Access Control
Learn how to manage user permissions and access to data assets in Atlan for security and compliance.
Learn how to manage user permissions and access to data assets in Atlan for security and compliance.
Configure AI asset access in personas — control who can view, edit, or manage AI models, model versions, applications, and governance properties.
Understand the Atlan architecture: platform components, management components, and central services across AWS, Azure, and GCP deployments.
Learn how to automatically provision Atlan groups based on user designations at first login using the designation-based group provisioning app.
Learn how to automatically assign roles and sub-roles to users in Atlan based on their group memberships using the group-role sync app.
Learn about compliance standards and assessments.
Use the Metadata Policy Helper app to create metadata policies in personas using advanced asset selection patterns. Setup requires the app access and connection admin rights.
The Atlan Secure Agent is a Kubernetes-based application that runs within a customer's environment. It acts as a gateway between the single-tenant Atlan SaaS and external systems like Snowflake, Tableau, and other data sources. This document explains the Secure Agent's deployment architecture, key components, communication flows, and security considerations.
Automatically provision Atlan groups based on user designations — maps user roles to groups at first login.
Learn about encryption and key management.
Configure Immuta access request links on Atlan assets and request data access directly from asset profiles.
Learn about incident response plan.
Learn about infrastructure security.
This guide provides step-by-step instructions to install the Secure Agent on an Amazon Elastic Kubernetes Service (AWS EKS) cluster.
Configure the Immuta workflow in Atlan to enrich data assets with Immuta access request links.
When users log into Atlan, a user session begins. You can change the default timeouts for user sessions for all users in your organization, helping you establish secure authentication protocols in Atlan. Once you have configured the settings, these would be applicable to users logging in via both basic and SSO authentication.
Configure metadata access in personas — control who can view, edit, or restrict metadata, tags, terms, and governance properties.
Configure metadata policies at scale using policy templates — automate permission assignment across assets, taxonomies, and custom metadata.
Learn about unable to log into atlan via sso due to an "internal error" from microsoft defender.
Request and manage changes to assets that you don't have direct edit access to.
The Atlan Secure Agent is a lightweight, Kubernetes-based application that enables secure metadata extraction. It connects internal systems with Atlan SaaS while keeping sensitive data protected and doesn’t require inbound connectivity. Running within an organization’s controlled environment, the Secure Agent ensures compliance with security policies and automates metadata processing.
Frequently asked questions about security controls and access protections for Lakehouse.
Learn about security monitoring.
The Docker-based databricks-extractor offline tool has been sunset. For on-premises or network-restricted Databricks lineage extraction, use Self-Deployed Runtime, Secure Agent, or direct connectivity via private link.
Learn about troubleshooting salesforce connectivity.
Why is the security\_admin role required to complete the ServiceNow integration?
Automatically downgrade offboarded users to Guest role — configure workflows for secure access revocation when users leave.
Import user roles from external sources into Atlan — automate role assignment based on user attributes and systems of record.
Complete configuration reference for the User Role Sync app properties and settings.
Learn what Atlan enriches from Immuta and how it surfaces on asset profiles.