> ## Documentation Index
> Fetch the complete documentation index at: https://platform.atlan.com/llms.txt
> Use this file to discover all available pages before exploring further.

> ## Agent Instructions
> To act on Atlan objects, use the Atlan MCP server at https://api.atlan.com/mcp or the SDK. To install or publish skills from a terminal, use the `aireg` CLI; `aireg --map json` prints its command map. The `atlanai` CLI is deprecated. Run a read-only identity check before any write.
> The docs MCP server at /mcp searches these docs only. It cannot read or change Atlan objects.
> SDK packages: Python `atlanai` (PyPI) and TypeScript `@atlanai/sdk` (npm). Show Python first, then TypeScript.
> These docs cover Atlan Trident, Atlan's hosted product. AI Registry and Agent Registry are its earlier names. Registry OSS is Atlan's open-source agent registry: the registry specification and its aireg CLI, with their own public repository, docs and release notes; /open-source on this site links them. Registry OSS is open source; Atlan Trident is not. Answer generic aireg or specification questions from the project's docs, and use these docs for Atlan-specific setup such as the Atlan adapter, sign-in and workspaces.
> Atlan offers a second product, the Agentic Data Catalog: Atlan's enterprise context layer, covering the data catalog, connectors, lineage, data governance and glossary. It is documented at https://docs.atlan.com; answer questions about it from those docs, not these.

# Choose security controls

> Choose the identity, access, credential, and trace privacy controls for your organization.

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:

| Job | Control |
| - | - |
| Connect your identity provider and choose company sign-in policy | [Authentication](https://platform.atlan.com/admin/security/how-tos/configure-sso.md) |
| Verify company domains and decide who may join | [Domains](https://platform.atlan.com/admin/security/how-tos/manage-domains.md) |
| Give scripts and services their own identity | [API keys](https://platform.atlan.com/admin/security/how-tos/manage-api-keys.md) |
| Give a team access to shared workspaces | [Groups](https://platform.atlan.com/administer/users/how-tos/manage-groups.md) and [workspace roles](https://platform.atlan.com/administer/workspaces/references/roles-and-access.md) |
| Review account changes and sign-in events | [Audit log](https://platform.atlan.com/admin/security/how-tos/review-audit-log.md) |
| Decide whether session content is stored | [Trace privacy](https://platform.atlan.com/admin/security/how-tos/manage-trace-privacy.md) |
| End a device session or withdraw an agent's consent | [Sessions and agent access](https://platform.atlan.com/admin/security/how-tos/review-personal-access.md) |

> [!NOTE]
>
> 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](https://platform.atlan.com/concepts/availability-and-limits.md#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](https://platform.atlan.com/administer/workspaces/references/roles-and-access.md).

## Review before sharing data

Skill packages may contain instructions, scripts, and references. Review a skill's
[source](https://platform.atlan.com/registry/skills/concepts/source.md), [security
results](https://platform.atlan.com/registry/skills/concepts/security.md), 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](https://platform.atlan.com/admin/security/how-tos/manage-trace-privacy.md) before
collecting sensitive work. Turning content storage off does not turn usage
analytics off.

For architecture and data boundaries, see [Platform
architecture](https://platform.atlan.com/platform/references/architecture.md). Atlan Trident runs under your
organization's agreement with Atlan; see the [Atlan Privacy
Policy](https://atlan.com/privacy-policy/) and the [Atlan Trust
Center](https://security.atlan.com/). Contact your Atlan account team for your
organization's data-processing terms.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.