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

# Astro

Connect your Astronomer Astro organization to add its workspaces, Airflow deployments, and users to your [Asset Map](/docs/asset-map).

## What it maps

| Resource | Configuration and relationships |
| - | - |
| Organization | Organization details and members. |
| Workspaces | Workspaces and their deployments. |
| Deployments | Airflow and Astro Runtime versions, executor type, cloud provider, region, and status. |
| Users | Organization roles and account status. |

These relationships help agents identify where your data pipelines run and who has access to the organization.

## Access required

Use an **organization API token** with permission to view the organization, its workspaces, deployments, and users. Choose a role that covers these resources. A token restricted to one workspace will not provide organization-wide visibility.

Antigen uses the token to read configuration. The token’s full permissions depend on the roles you assign in Astro.

## Connect Astro

### 1. Create an organization API token

In Astro, open **Settings → Access Management → API Tokens** and select **New Organization API Token**.

Name the token `Antigen`, select its organization role, and choose an expiration. Create the token and copy its value.

See [Astro organization API tokens](https://www.astronomer.io/docs/astro/organization-api-tokens) for token roles and setup instructions.

### 2. Complete the connection

Open **Settings → Integrations → Astro** in Antigen.

Paste the token and select **Connect**. Antigen discovers the organization associated with the token and adds its resources to your Asset Map.

## Troubleshooting

### The token is rejected

Check that you created an organization API token and that it has not expired or been revoked.

### Workspaces or deployments are missing

Check the token’s organization and workspace roles. Its permissions must cover the resources you want to map, including deployments in each workspace.