Skip to main content
Atlan Trident checks the signed-in identity and workspace access when people, API keys, and agents read or change Registry content. Organization roles govern settings; workspace roles govern the content in each workspace. Start with the control that matches the job:
Some controls depend on your plan. Company SSO and viewing the audit log are included in Team and Enterprise, not in Startup. Network access controls are included in Enterprise only. See What depends on your plan.

Organization and workspace access

Use Member for day-to-day work and Admin for people who manage organization settings. A workspace has its own Admin, Builder, and Viewer roles. Check both scopes when someone cannot reach a resource. API keys and agents also need workspace access. Knowing a workspace ID or holding a valid credential does not grant access to its content. See Roles and access.

Review before sharing data

Skill packages may contain instructions, scripts, and references. Review a skill’s source, security results, and release before using it with a client that can run code or call external tools. Session content can contain prompts, responses, and files used by an agent. Configure trace privacy before collecting sensitive work. Turning content storage off does not turn usage analytics off. For architecture and data boundaries, see Platform architecture. Atlan Trident runs under your organization’s agreement with Atlan; see the Atlan Privacy Policy and the Atlan Trust Center. Contact your Atlan account team for your organization’s data-processing terms.