> ## 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 AI Registry, Atlan's hosted product. The AI registry specification and aireg CLI are maintained separately. /open-source lists publicly reachable signed installers and explains that the source repository and hosted CLI reference currently require GitHub access. Do not claim the repository or its reference docs are publicly accessible. Use these docs for Atlan-specific setup such as the adapter, sign-in and workspaces.

# Set up your organization

> A checklist for administrators: sign-in, members, workspaces, desktop rollout, models, and apps, in the order that saves rework.

Use this checklist when you first set up AI Registry for your organization. Each step links to its full guide. The order matters: sign-in rules decide who can join, and workspaces should exist before you invite people into them.

## Before you begin

* **Organization Admin role.** Most steps need it. See [Organization roles](/administer/users/references/roles).
* **A second administrator.** Plan for one, so access never depends on one person.

## Checklist

<Steps>
  <Step title="Decide how people sign in">
    Verify your company email domains, choose how people with those addresses join, and connect your identity provider.

    * [Manage company domains](/admin/security/how-tos/manage-domains)
    * [Configure company SSO](/admin/security/how-tos/configure-sso)
  </Step>

  <Step title="Create team workspaces">
    A workspace decides where skills and agents live and who can see or change them. Create one for each team that shares skills, then choose whether its changes release automatically or wait for approval.

    * [Create and edit workspaces](/administer/workspaces/how-tos/create-and-edit)
    * [Set workspace release policy](/administer/workspaces/how-tos/set-release-policy)
  </Step>

  <Step title="Invite members">
    Invite people to the organization, or straight into the workspaces they need, with the right roles. Give a second person the organization **Admin** role.

    * [Invite members](/administer/users/how-tos/invite-members)
    * [Manage workspace members](/administer/workspaces/how-tos/manage-members)
  </Step>

  <Step title="Roll out Atlan Desktop and the trace plugin">
    Atlan Desktop brings each person's Claude Code and Codex skills and sessions into AI Registry. On managed computers, deploy it with your MDM. To capture Claude Code sessions across a fleet, deploy the trace plugin with managed settings.

    * [Deploy desktop app with MDM](/administer/desktop/how-tos/deploy-with-mdm)
    * [Managed installation](/plugins/how-tos/managed-installation)
  </Step>

  <Step title="Choose what is stored from sessions">
    Decide whether Atlan stores session content, or only the run's metadata. Settle this before people start sending traces.

    * [Manage trace privacy](/admin/security/how-tos/manage-trace-privacy)
  </Step>

  <Step title="Connect models and set rates">
    Connect the model providers your agents should reach through Model Gateway. Then set the rates your organization pays, so run cost matches your bill.

    * [Supported model providers](/gateway/model/references/providers)
    * [Set model rates](/admin/finops/models-and-rates)
  </Step>

  <Step title="Install optional apps">
    Metrics Studio and Ontology are installed by an administrator. Install them only if your teams will use them.

    * [Install and manage apps](/registry/apps/how-tos/install-apps)
  </Step>

  <Step title="Create credentials for automation">
    Scripts, CI jobs, and services use API keys instead of a person's sign-in. Scope each key to what it needs.

    * [Manage API keys](/admin/security/how-tos/manage-api-keys)
  </Step>
</Steps>

## Verify

* A colleague you invited can sign in, sees the team workspaces they joined, and finds a shared skill. If they can't, see [Workspace access errors](/administer/workspaces/troubleshooting/workspace-access-errors).
* **Settings** shows your verified domains and your second administrator.

## Next steps

* [Admin & security](/admin/index): every administration task in one place.
* [Availability and limits](/concepts/availability-and-limits): what is on by default and what needs turning on.


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