Access Control in Atlan covers identity and access management (SSO, SCIM, users, groups, roles), permissions (personas, purposes, connection access, visibility), and audit logs. Configure who can sign in, what they can see, and how their activity is tracked.
Understand the Atlan architecture: platform components, management components, and central services across AWS, Azure, and GCP deployments.
Learn about compliance standards and assessments.
Reference for data quality permission scopes and configuration in Atlan.
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.
Learn about encryption and key management.
Grant the Unity Catalog and workspace permissions Context Engineering Studio needs to deploy a context repository to Databricks Genie. Required at deploy time. On Databricks, Simulate also runs on a live Genie Space, so simulating requires a first deploy.
Grant the Snowflake permissions Context Engineering Studio needs to deploy a certified context repository to Snowflake Cortex Analyst. Required only at deploy time. You can connect, build, and simulate without them.
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.
Control what users can see and do in Atlan once they have signed in. Scope access by team with personas, by data sensitivity with purposes, by connection, or hide assets entirely. Learn which control to use and how role, persona, and purpose combine.
Full reference of the privileges required to crawl AI models and extract lineage from Databricks Unity Catalog, including what each privilege enables and how to grant it.
Full reference of the privileges required to crawl AI models and extract lineage from the Snowflake Model Registry, including what each privilege enables and why it's needed.
Full reference of the additional privileges the Atlan service account needs to discover Snowflake listings and shares, including what each privilege enables, why standard connector permissions aren't enough, and how to grant them.
Explanation of Snowflake's security model and role requirements for data quality operations.
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 permissions for the Atlan browser extension.
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.
Set up user accounts and permissions required for SAP BW/4HANA metadata extraction in Atlan.
Set up user accounts and permissions required for SAP ECC metadata extraction in Atlan.
Set up user accounts and permissions required for SAP S/4HANA metadata extraction in Atlan.
Learn about troubleshooting salesforce connectivity.
Why is the security\_admin role required to complete the ServiceNow integration?