Back to Spinrun

Security and compliance

Find the published policies and discuss specific requirements.

What to check first

For this issue, start with the active workspace and the relevant settings screen. Find the published policies and discuss specific requirements. Read the current confirmation or provider error rather than repeating the action immediately. Keep a record of what you tried and its approximate time so an administrator or the support team can identify the request.

Keep data within its intended scope

Workspace and resource access checks apply to chat, files, and connected systems. Give a task only the material it needs. A person being in a team channel does not make every private source available to them.

Review publication separately

A generated file, artifact, or hosted application can have a different audience from the source conversation. Inspect its sharing controls and actual content before making a link public.

If the issue remains

Open the data and privacy guide for the current product steps. If that does not resolve the issue, contact support. Include your workspace name, the screen, and the approximate time. Do not send passwords, API keys, card numbers, or an unrestricted data export.

Related articles

Before anything loads

We would like to switch on analytics, so we can see which pages are worth keeping. Nothing has loaded yet and nothing will until you choose. The cookies that keep you signed in and remember your language are not part of this.

Read the Cookie Policy