Admin Export App
The Admin Export app exports administrative information from Atlan into a single Excel workbook. You can include users, groups, personas, purposes, and policies to create a complete snapshot of your access model for backup, audits, or offline analysis.
This reference describes all configuration properties for the app and what each worksheet in the exported workbook contains.
Access
The Admin Export app isn't available in all tenants by default. To enable it, contact Atlan support or your Atlan customer team and request access to the Admin export app.
Once enabled, only admins or users with workflow permissions configure and run this app, because it operates on users, groups, personas, purposes, and policies.
Workflow name
Specifies the display name for this workflow configuration in Atlan. Use a descriptive name that makes it clear this job exports administrative configuration for audit or backup.
Example:
atlan-admin-export
Objects to include
Specifies which administrative objects the app exports into the output file. Select one or more object types. Each selected object type is exported to its own worksheet (Excel) or file (CSV).
- Users: exports user accounts in your Atlan tenant.
- Groups: exports groups used for access control and administration.
- Personas: exports personas and a summary of the policies attached to them.
- Purposes: exports purposes, their associated tags, and a summary of the policies attached to them.
- Policies: exports the detailed policies associated with personas and purposes.
Include out-of-the-box policies
Controls whether the export includes system policies provided by Atlan by default (out-of-the-box policies). These policies support core product functionality and typically can't be edited or removed.
- Yes: includes system policies that ship with Atlan. Use this when you need a complete view of all effective policies, including defaults, for troubleshooting complex permissions or for full audits.
- No: excludes default policies. Recommended for most reporting scenarios to avoid noise from policies that can't be modified.
File format
The File format setting controls how the exported data is structured on disk.
- Single Excel file
- Multiple CSV files
When selected, the app exports all chosen object types into one Excel workbook (.xlsx).
- Output: A single
.xlsxfile - Structure: One worksheet per object type (for example:
Users,Groups,Personas,Purposes,Policies) - Best for: Manual review, audits, one-file backups, and spreadsheet-based analysis
When selected, the app exports each chosen object type as a separate CSV file.
- Output: One .csv per selected object type (for example:
users.csv,groups.csv, etc.) - Structure: Flat files with header rows; each file contains only one object type
- Best for: Automated pipelines, importing into databases, version control diffs, and script-based analysis
Export via
Defines the primary delivery mechanism. Regardless of the option you choose, the file is always available to download from the workflow run in Atlan.
- Direct download
- Object storage
When selected, the app makes the exported file available directly in Atlan. After the workflow run completes, you can download the file from the workflow run details page (Workflow runs → select the run → Download).
Sends the exported workbook as an email attachment when the workflow completes.
Email addresses
Specifies one or more recipient email addresses, separated by commas. All recipients receive the same file as an attachment when the workflow completes successfully. Attachments sent by email are limited to 25 MB. If the exported file exceeds this size, the email isn't delivered, but the file remains available for direct download from the workflow run in Atlan.
Example:
Uploads the exported workbook to a cloud object store such as Amazon S3, Google Cloud Storage (GCS), or Azure Data Lake Storage (ADLS). Object storage is recommended when you need to keep exports for longer retention, integrate them into automated pipelines, or deliver them to downstream systems that read from S3, GCS, or ADLS.
For details on configuring storage credentials, access methods, and common fields such as Prefix (path), Object key (filename), and Cloud object store, see Object storage for apps.
Workbook structure
The exported Excel file contains one worksheet for each selected object type. Column names are fixed and designed for analysis in spreadsheet tools.
Users worksheet
Each row represents a single user account in Atlan.
| Column | Description | Notes |
|---|---|---|
| Username | Username of the user. | Matches the sign-in identifier used for the account. |
| First name | First name of the user. | Populated from the user's profile. |
| Last name | Last name of the user. | Populated from the user's profile. |
| Email address | Email address of the user. | Used for notifications and invitations. |
| Groups | Groups assigned to the user. | Multiple groups may be listed in a single cell, separated by delimiters. |
| Created | Date and time when the user was invited to Atlan. | Timestamp is converted into a human-readable format. |
| Enabled | Whether the user can log in (true) or is deactivated (false). | false indicates the account is disabled and can't access Atlan. |
| Last login | Date and time when the user last logged in. | Useful for identifying inactive or rarely used accounts. |
| Personas | Personas assigned to the user. | Includes personas assigned directly or via groups, with values separated by newlines. |
| Licence type | Type of license assigned to the user. | For example, admin vs member. |
| Designation | Designation of the user. | |
| Group names | Non-technical names of groups the user is assigned to. | Multiple groups may be listed in a single cell, separated by delimiters. |
| Extracted on | Date and time when the user was extracted. |
Sample users worksheet file
Download a sample CSV file that shows the structure of the Users worksheet:
📥 Download sample users CSV
This sample file shows the structure and format only. It may not match your environment and is intended as a template for understanding the export.
Groups worksheet
Each row represents a group used for access control or administration.
| Column | Description | Notes |
|---|---|---|
| Group name | Name of the group as it appears in the Atlan UI. | Display name used in governance and access control workflows. |
| Internal name | Programmatic name for the group. | Used when referencing the group in APIs, workflows, or automation. |
| Number of users | Number of users who belong to the group. | Helps you understand adoption and impact of changes to this group. |
| Default | Whether new users are added to this group by default. | true indicates the group is automatically assigned to new users. |
| Created at | Date and time when the group was created. | Useful for auditing when a group was introduced. |
| Created by | User who created the group. | Indicates who originally defined the group. |
| Updated at | Date and time when the group was last updated. | Helps track recent configuration changes. |
| Updated by | User who last updated the group. | Identifies the last owner to modify group membership or properties. |
| Extracted on | Date and time when the group was extracted. |
Personas worksheet
Each row represents a persona that groups policies and access behavior.
| Column | Description | Notes |
|---|---|---|
| Persona name | Name of the persona. | Used throughout Atlan to apply a consistent access profile. |
| Description | Description of the persona. | Optional text that explains the persona's purpose or scope. |
| Users | Users assigned to the persona. | Multiple users appear as newline-separated values in a single cell. |
| Groups | Groups assigned to the persona. | Multiple groups appear as newline-separated values in a single cell. |
| Metadata policies | Number of metadata policies associated with the persona. | Indicates how much metadata-level control the persona exerts. |
| Data policies | Number of data policies associated with the persona. | Indicates how much data-level control the persona exerts. |
| Glossary policies | Number of glossary policies associated with the persona. | Shows how glossary access is governed for this persona. |
| Domain policies | Number of domain policies associated with the persona. | Shows how domain-level access is governed for this persona. |
| Connections | Connections governed by the persona's metadata or data policies. | Values are newline-separated within the cell to support multi-connection personas. |
| Glossaries | Glossaries governed by the persona's glossary policies. | Values are newline-separated within the cell. |
| Domains | Domains governed by the persona's domain policies. | Values are newline-separated within the cell. |
| Navigation | Default landing page for the persona. | |
| Hide asset types | Asset types hidden from this persona. | |
| Hide sidebar tabs | Sidebar tabs hidden from this persona. | |
| Hide asset filters | Asset search filters hidden from this persona. | |
| Hide asset metadata | Asset metadata hidden from this persona. | |
| Display preferences | Specific preferences for displaying assets for this persona. | |
| Custom metadata to hide | Custom metadata tabs hidden from this persona. | |
| Extracted on | Date and time when the persona was extracted. |
Purposes worksheet
Each row represents a purpose that groups policies and Atlan tags.
| Column | Description | Notes |
|---|---|---|
| Purpose name | Name of the purpose. | Describes the access purpose (for example, regulatory or business usage). |
| Description | Description of the purpose. | Optional text that documents why the purpose exists. |
| Tags | Atlan tags controlled by the purpose. | Tags appear as newline-separated values within the cell. |
| Metadata policies | Number of metadata policies associated with the purpose. | Indicates the level of metadata control enforced by this purpose. |
| Data policies | Number of data policies associated with the purpose. | Indicates the level of data control enforced by this purpose. |
| Groups | Groups to which the purpose's policies apply. | Used to understand which group-based identities are governed. |
| Users | Users to which the purpose's policies apply. | Used to understand which individual identities are governed. |
| Navigation | Default landing page for the purpose. | |
| Hide asset types | Asset types hidden from this purpose. | |
| Hide sidebar tabs | Sidebar tabs hidden from this purpose. | |
| Hide asset filters | Asset search filters hidden from this purpose. | |
| Custom metadata to hide | Custom metadata tabs hidden from this purpose. | |
| Extracted on | Date and time when the purpose was extracted. |
Policies worksheet
Each row represents a policy associated with a persona or purpose.
| Column | Description | Notes |
|---|---|---|
| Policy active | Whether the policy is active (true) or deactivated (false). | |
| Policy name | Name of the policy. | Appears in governance views and policy management interfaces. |
| Description | Description of the policy. | Optional clarification of what the policy is intended to enforce. |
| Parent type | Type of access mechanism that owns the policy. | Typically Persona or Purpose, used to understand where the policy lives. |
| Parent name | Name of the parent persona or purpose. | Helps trace the policy back to the higher-level access construct. |
| Kind | Policy kind, such as metadata, data, glossary, or domain. | Indicates which layer of access the policy affects. |
| Type | Whether the policy grants or denies access. | Commonly allow or deny, depending on configuration. |
| Actions | Actions covered by the policy. | For example, which actions are allowed in an allow policy. |
| Resources | Resources that the policy controls. | Includes connections, glossaries, domains, or tags, listed as newline-separated values. |
| Extracted on | Date and time when the policy was extracted. |