Workspaces and access
Keep each team’s projects, evidence and permissions in the right place.
A workspace is the collaboration and access boundary. A project is the website and business you are investigating inside that workspace.
For agency work, check the selected workspace and project before connecting a property, starting a run or opening an Agent chat. A familiar website name alone is not enough to identify the right project.
Choose the right project
Use the application’s workspace and project controls to select your working context. Dashboard measurements, Actions and Agent chats belong to that project.
An Agent chat stays with the project where it started. Start a separate chat when you need to work on another project; asking the Agent to switch projects does not change its access.
Understand missing controls
Your role determines which actions you can perform. Workspace entitlements, remaining allowances and configured providers also affect whether a run is available.
If you can view a result but cannot start work:
- Confirm that you are in the expected workspace.
- Check the reason shown by the disabled control or access notice.
- Ask a workspace administrator to review your role or configuration.
A direct link to an object does not grant access to it.
Share context carefully
Links help colleagues return to the same project record, but each person still needs permission to read it. External AI clients connected through MCP also recheck the account’s current workspace access.
If an invited colleague cannot open a record, verify membership rather than copying private evidence into an unrelated workspace.
Appearance and preferences
The application and onboarding headers include a one-click Light/Dark theme switch. The preference is stored on your device. Public documentation uses the light public-site design. Appearance changes do not change the scope or meaning of your measurements.