Skip to main content

Designation-based group provisioning
App

The designation-based group provisioning app enables automated group assignment in Atlan by mapping user designations to target groups at first login. It reads a CSV mapping file of standard Atlan designation values to group names, creates any missing groups if configured to do so, and updates group memberships accordingly.

This reference provides complete configuration details for the designation-based group provisioning app. Use this page to look up required CSV structure, property definitions, valid values, and configuration formats when you set up automated group assignments based on user designations so that new users land in the right groups from day one, with optional cleanup of default group memberships.

Access​

The designation-based group provisioning app isn't enabled by default. To use this app, contact Atlan support and request that it be added to your tenant.

Upload local mapping file​

Upload the designation-to-group mapping as a CSV (.csv) file. The app uses this file to determine which Atlan groups to add a user to based on their designation at first login.

Use exact designation values as configured in your tenant to avoid mismatches.

Supported file format:

  • Accepted format: CSV (.csv) only.
  • Maximum size: up to 1 MB.
  • Not supported: Excel files such as .xlsx or .xls.

Required structure​

Your CSV must:

  • Include a header row in the first line with these column names:

    • DESIGNATION
    • GROUP_NAME

  • Contain the following columns (case-sensitive):

    • DESIGNATION: The designation value stored for the user in Atlan that the app uses for matching.

      Example values: Data Analyst, Data Engineer, Data Scientist, Other

    • GROUP_NAME: The name of the Atlan group that the app provisions the user into when the designation matches.

      Example values: Data Analysts, Data Engineering, Data Governance, Business Users

Each row represents one designation → one group mapping.

To make sure every user is provisioned into a group, include a fallback row where:

  • DESIGNATION = Other

Users whose designation doesn't match any other row are provisioned into the group mapped to Other.

Example CSV​

DESIGNATION,GROUP_NAME
Data Analyst,Data Analysts
Data Engineer,Data Engineering
Data Scientist,Data Engineering
Other,Business Users

Sample CSV file​

Download a sample CSV file to understand the required structure:

📥 Download designation-to-group mapping CSV

Sample file disclaimer

This sample file shows the expected structure and example mappings only. Update the designations and group names to match your organization before running the workflow.

Handling for missing groups​

Controls how the app handles groups that appear in the mapping file but don't yet exist in Atlan.

  • Create: Automatically creates any missing GROUP_NAME values from the mapping file, then provisions matching users into those newly created groups. (Example: if DESIGNATION=Data Engineer maps to GROUP_NAME=Data Engineering and Data Engineering doesn’t exist, the app creates Data Engineering and adds Data Engineers to it.)

  • Skip: Skips provisioning for any mapping row where the target group doesn't exist. No groups are created, and affected users remain only in their existing groups (including default groups, unless removed by another setting). (Example: if DESIGNATION=Data Analyst maps to GROUP_NAME=Data Analysts but Data Analysts doesn’t exist, Data Analysts aren't provisioned into a new group.)

Remove mapped users from DEFAULT groups​

Controls whether users who are successfully provisioned into one or more mapped (non-default) groups are also removed from DEFAULT groups.

  • Yes: If a user is provisioned into at least one group via the mapping file, the app removes the user from the configured DEFAULT groups. (Example: a user is added to Data Engineering based on DESIGNATION=Data Engineer, and is then removed from All Users.)

  • No: Users remain in their existing DEFAULT groups even after being provisioned into mapped groups. (Example: a user is added to Data Engineering but also continues to belong to All Users.)

See also​