Use the Atlan browser extension | Atlan Documentation

The Atlan browser extension provides metadata context directly in your supported data tools . You can use the extension in the following Chromium-based browsers: Google Chrome and Microsoft Edge. Install the extension To install Atlan's browser extension: You can either: Find the extension in the Chrome Web Store: https://chrome.google.com/webstore/detail/atlan/fipjfjlalpnbejlmmpfnmlkadjgaaheg From the upper right of any screen in Atlan, navigate to your name and then click Profile . Click the four dots icon in the resulting dialog to get to integrations. Under Apps , for Browser extension , click Install . Find the extension in the Chrome Web Store: https://chrome.google.com/webstore/detail/atlan/fipjfjlalpnbejlmmpfnmlkadjgaaheg From the upper right of any screen in Atlan, navigate to your name and then click Profile . Click the four dots icon in the resulting dialog to get to integrations. Under Apps , for Browser extension , click Install . Click the four dots icon in the resulting dialog to get to integrations. Under Apps , for Browser extension , click Install . To install the Atlan browser extension: For Google Chrome, in the upper right of your screen, click Add to Chrome . When prompted for confirmation, click the Add extension button. For Microsoft Edge, follow the steps in Add an extension to Microsoft Edge from the Chrome Web Store . For Google Chrome, in the upper right of your screen, click Add to Chrome . When prompted for confirmation, click the Add extension button. For Microsoft Edge, follow the steps in Add an extension to Microsoft Edge from the Chrome Web Store . Currently, you can't install the browser extension on mobile devices or tablets. You can also install Atlan's browser extension at the workspace level . To set this up, you need to be an administrator or have access to the admin console of your organization's Google account. If your organization uses managed browsers, you can configure the extension for managed browsers . Configure the extension Once installed, configure the Atlan browser extension to get started. Optionally, Atlan admins can preconfigure custom domains for data sources , if any. Configure the extension as a user To configure the browser extension, once installed: If you are logged into your Atlan instance, skip to the next step. If you haven't logged into Atlan, log in to your Atlan instance when prompted. In the Options page, to enter the URL of your Atlan instance: If your organization uses an Atlan domain (for example, _mycompany_.atlan.com ), the Atlan instance URL appears preselected. Click Get started . (Optional) Switch to a different Atlan domain, if required. If your organization uses a custom domain (for example, _atlan_.mycompany.com ), enter the URL of your Atlan instance and then click Get started . If your organization uses an Atlan domain (for example, _mycompany_.atlan.com ), the Atlan instance URL appears preselected. Click Get started . (Optional) Switch to a different Atlan domain, if required. If your organization uses a custom domain (for example, _atlan_.mycompany.com ), enter the URL of your Atlan instance and then click Get started . After a successful login, the message Updated successfully appears. (Optional) If your data tools are hosted on custom domains, rather than the standard SaaS domain of each tool: Click the Configure custom domain link at the bottom. In the dropdown on the left, select your data tool. In the text box on the right, enter the custom domain you use for that tool. Repeat these steps for each tool hosted on a custom domain. Click the Save button when finished. If your Atlan admin has preconfigured custom domains for data sources , you won't be able to update or remove these selections. Click + Add to configure custom domains for additional data sources as required. Click the Configure custom domain link at the bottom. In the dropdown on the left, select your data tool. In the text box on the right, enter the custom domain you use for that tool. Repeat these steps for each tool hosted on a custom domain. Click the Save button when finished. In the dropdown on the left, select your data tool. In the text box on the right, enter the custom domain you use for that tool. Repeat these steps for each tool hosted on a custom domain. Click the Save button when finished. If your Atlan admin has preconfigured custom domains for data sources , you won't be able to update or remove these selections. Click + Add to configure custom domains for additional data sources as required. You can now close the Options tab. The extension is now ready to use! ð (Optional) Configure custom domains as an admin You need to be an admin user in Atlan to configure custom domains for data sources from the admin center. To configure custom domains, from within Atlan: From the left menu of any screen, click Admin . Under Workspace , click Integrations . Under Apps , expand the Browser extension tile. In the Browser extension tile, for Set up your custom data source. , if your data tools are hosted on custom domains rather than the standard SaaS domain of each tool, click the Configure link to configure them for users in your organization. For Connector , select a supported tool for the browser extension. In the adjacent field, enter the URL of the custom domain for your data source. (Optional) Click + Add to add more. Click Save to save your configuration. info ð ª Did you know? For any supported tools that you have configured, your users won't be able to update or remove these selections. They can, however, add additional custom domains for data sources. For Connector , select a supported tool for the browser extension. In the adjacent field, enter the URL of the custom domain for your data source. (Optional) Click + Add to add more. Click Save to save your configuration. ð ª Did you know? For any supported tools that you have configured, your users won't be able to update or remove these selections. They can, however, add additional custom domains for data sources. (Optional) For Download Atlan extension or share with your team , you can either install the Atlan browser extension for your own use or share the link with your users. Anyone with access to Atlan any admin, member, or guest user and a supported tool can use the browser extension. First, log into Atlan. When using Atlan's browser extension in a supported tool , the extension only reads the URL of your browser tab no other data is accessed. If using Atlan's browser extension on any website , it only reads the favicon, page title, and URL of your browser tab. Learn more about Atlan browser extension security . Access and enrich context in-flow To access context for an asset, from within a supported tool: Log into the supported tool. Open any supported asset. In the lower-right corner of the page, click the small Atlan icon. danger The icon to activate Atlan is not the extension icon that appears at the top of your Chrome browser. This small Atlan icon in the lower right corner of the page is the only way to access the metadata for the asset you are viewing in another tool. The icon to activate Atlan is not the extension icon that appears at the top of your Chrome browser. This small Atlan icon in the lower right corner of the page is the only way to access the metadata for the asset you are viewing in another tool. In the sidebar that appears: Click the tabs and links to view all context about the asset. Make changes to any of the metadata you'd like. Click the tabs and links to view all context about the asset. Make changes to any of the metadata you'd like. Now you can understand and enrich assets without leaving your data tools themselves! ð The Atlan sidebar automatically reloads as you browse your assets in a supported tool to show details about the asset you're currently viewing. Your permissions in Atlan control what metadata you can see and change in the extension. The extension opens a new browser tab on Atlan's discovery page, with the results for that text! ð Add a resource You can link any web page as a resource to your assets in Atlan using the browser extension. To add a web page as a resource to an asset: In the top right of the web page you're viewing, click the Atlan Chrome extension . In the resource clipper menu, under Link this page to an asset , select the asset to which you'd like to add the web page as a resource. Click Save to confirm your selection. (Optional) Once the resource has been linked successfully, click the Open in Atlan button to view the linked asset directly in Atlan. You can now add resources to your assets in Atlan from any website! ð The Tableau extension offers native embeddings directly in your dashboards. See Enable embedded metadata in Tableau for more information. Supported tools Currently, the Atlan browser extension supports assets in the following tools: Amazon QuickSight : analyses, dashboards, and datasets Databricks : databases, schemas, views, and tables dbt Cloud : models and sources in the model editor and dbt docs Google BigQuery : datasets, schemas, views, and tables IBM Cognos Analytics : folders, dashboards, packages, explorations, reports, files, data sources, and modules Looker : dashboards, explores, and folders Microsoft Power BI : dashboards, reports, dataflows, and datasets Mode : collections, reports, queries, and charts Qlik Sense Cloud : apps, datasets, sheets, and spaces Redash : queries, dashboards, and visualizations Salesforce : objects Sigma : datasets, pages, and data elements Snowflake (via Snowsight schema explorer): databases, schemas, tables, views, dynamic tables, streams, and pipes Tableau : dashboards, data sources, workbooks, and metrics. Additionally, you can choose to switch the Tableau extension to offer native embeddings directly in your dashboards. See Enable embedded metadata in Tableau for more information. ThoughtSpot : liveboards, answers, visualizations, and tables MicroStrategy : dossiers, reports, documents Install the extension Configure the extension


Configure the extension for managed browsers | Atlan Documentation

If you're using managed browsers, you can install and configure the Atlan browser extension for all users in your organization. To do so, you will need to bulk install the extension and deploy a configuration script. Atlan supports managing the Atlan browser extension for the following: Operating systems: macOS and Microsoft Windows Browsers: Google Chrome and Microsoft Edge The deployment scripts - .mobileconfig file for macOS and PowerShell script for Microsoft Windows - are designed to make only the most necessary modifications required for the Atlan browser extension to function properly. Both deployment methods adhere to the principle of least privilege: The .mobileconfig file for macOS only includes the configuration settings required to install and operate the Atlan browser extension. The PowerShell script creates essential registry keys required for the Atlan browser extension to operate on Microsoft Windows systems. To configure the Atlan browser extension for a managed browser, you must complete these steps in the following order: Configure the browser extension Bulk install the browser extension Deploy the configuration script (Optional) Verify and monitor the installation Configure the browser extension You will need to be an admin in Atlan to configure the browser extension for users in your organization. You will also need inputs and approval from the IT administrator of your organization. You can configure the browser extension and then download a configuration script to bulk install and deploy it for everyone in your organization. To configure the browser extension, from within Atlan: From the left menu on any screen, click Admin . Under Workspace , click Integrations . Under Apps , expand the Browser extension tile. In the Browser extension tile, for Bulk install the browser extension , click the Set up now button. In the Set up browser extension form, enter the following details: For Choose browser , the browser and operating system values will be prefilled based on what you're currently using - you can modify the fields, if required. For Your Atlan domain , enter the URL of your Atlan instance - for example, https://(instance_name).atlan.com . info ð ª Did you know? If you enable multiple Atlan domains, your users will be able to select the most relevant Atlan domain from a dropdown menu while using the browser extension. The default value in the dropdown will be the Atlan instance entered as Your Atlan domain . If your organization does not have multiple Atlan domains, only the default selection will be displayed. (Optional) For Advanced settings , you can configure the following: If you have multiple Atlan instances, toggle on Multiple Atlan domains and then enter the URLs of your additional Atlan instances. Click + Add to add more Atlan domains. If your data tools are hosted on custom domains rather than the standard SaaS domain of each tool, toggle on Custom data source domain . Click + Add to add more custom domains for data sources. For Connector , select a supported tool for the browser extension. In the adjacent field, enter the URL of your custom data source domain. info ð ª Did you know? For any supported tools configured while setting up the managed browser extension, your users will not be able to update or remove these selections. They can, however, add additional custom domains for data sources. Click the Download Script button to download the corresponding configuration script. The IT administrator(s) in your organization will need to install this configuration file in your organization's devices using a mobile device management (MDM) software. Administrative permissions to the MDM platform are required to complete the setup. Based on your operating system, the downloaded file can be one of the following two types: .mobileconfig - use this file to configure profiles with specific settings in macOS devices . .ps1 - use this PowerShell script to create registry keys in Microsoft Windows devices . For Choose browser , the browser and operating system values will be prefilled based on what you're currently using - you can modify the fields, if required. For Choose browser , the browser and operating system values will be prefilled based on what you're currently using - you can modify the fields, if required. For Your Atlan domain , enter the URL of your Atlan instance - for example, https://(instance_name).atlan.com . info ð ª Did you know? If you enable multiple Atlan domains, your users will be able to select the most relevant Atlan domain from a dropdown menu while using the browser extension. The default value in the dropdown will be the Atlan instance entered as Your Atlan domain . If your organization does not have multiple Atlan domains, only the default selection will be displayed. For Your Atlan domain , enter the URL of your Atlan instance - for example, https://(instance_name).atlan.com . ð ª Did you know? If you enable multiple Atlan domains, your users will be able to select the most relevant Atlan domain from a dropdown menu while using the browser extension. The default value in the dropdown will be the Atlan instance entered as Your Atlan domain . If your organization does not have multiple Atlan domains, only the default selection will be displayed. (Optional) For Advanced settings , you can configure the following: If you have multiple Atlan instances, toggle on Multiple Atlan domains and then enter the URLs of your additional Atlan instances. Click + Add to add more Atlan domains. If your data tools are hosted on custom domains rather than the standard SaaS domain of each tool, toggle on Custom data source domain . Click + Add to add more custom domains for data sources. For Connector , select a supported tool for the browser extension. In the adjacent field, enter the URL of your custom data source domain. info ð ª Did you know? For any supported tools configured while setting up the managed browser extension, your users will not be able to update or remove these selections. They can, however, add additional custom domains for data sources. (Optional) For Advanced settings , you can configure the following: If you have multiple Atlan instances, toggle on Multiple Atlan domains and then enter the URLs of your additional Atlan instances. Click + Add to add more Atlan domains. If you have multiple Atlan instances, toggle on Multiple Atlan domains and then enter the URLs of your additional Atlan instances. Click + Add to add more Atlan domains. If your data tools are hosted on custom domains rather than the standard SaaS domain of each tool, toggle on Custom data source domain . Click + Add to add more custom domains for data sources. For Connector , select a supported tool for the browser extension. In the adjacent field, enter the URL of your custom data source domain. info ð ª Did you know? For any supported tools configured while setting up the managed browser extension, your users will not be able to update or remove these selections. They can, however, add additional custom domains for data sources. If your data tools are hosted on custom domains rather than the standard SaaS domain of each tool, toggle on Custom data source domain . Click + Add to add more custom domains for data sources. For Connector , select a supported tool for the browser extension. In the adjacent field, enter the URL of your custom data source domain. ð ª Did you know? For any supported tools configured while setting up the managed browser extension, your users will not be able to update or remove these selections. They can, however, add additional custom domains for data sources. Click the Download Script button to download the corresponding configuration script. The IT administrator(s) in your organization will need to install this configuration file in your organization's devices using a mobile device management (MDM) software. Administrative permissions to the MDM platform are required to complete the setup. Based on your operating system, the downloaded file can be one of the following two types: .mobileconfig - use this file to configure profiles with specific settings in macOS devices . .ps1 - use this PowerShell script to create registry keys in Microsoft Windows devices . Click the Download Script button to download the corresponding configuration script. The IT administrator(s) in your organization will need to install this configuration file in your organization's devices using a mobile device management (MDM) software. Administrative permissions to the MDM platform are required to complete the setup. Based on your operating system, the downloaded file can be one of the following two types: .mobileconfig - use this file to configure profiles with specific settings in macOS devices . .ps1 - use this PowerShell script to create registry keys in Microsoft Windows devices . Bulk install the browser extension You will need to have administrator access to your organization's mobile device management (MDM) software with the permission to add and deploy new policies to all users. You will also need inputs and approval from your Atlan admin. You will need to configure the ExtensionInstallForcelist browser policy for either Google Chrome or Microsoft Edge to force-install the extension for everyone in your organization. The ExtensionInstallForcelist browser policy: Governs extensions that can be silently installed and automatically enabled for all users. Provides extension IDs that the browser will automatically install and enable when a user logs in. Google Chrome To bulk install the Atlan browser extension in Google Chrome, follow the steps in Google documentation: Force install apps and extensions . Microsoft Edge To bulk install the Atlan browser extension in Microsoft Edge, follow the steps in Microsoft documentation: Force-install an extension . For the Extension/App IDs and update URLs to be silently installed (Device) field, copy and paste the following value: fipjfjlalpnbejlmmpfnmlkadjgaaheg is the extension-id for the Atlan browser extension. Deploy the configuration script You will need to have administrator access to your organization's mobile device management (MDM) software with the permission to add and deploy new policies to all users. You will also need inputs and approval from your Atlan admin. The browser extension relies on managed storage for configuring domains in the Atlan extension. The values for managed storage can be configured through: A configuration profile in macOS Registry keys in Microsoft Windows Although Atlan's solution is platform-agnostic, the following example pertains to Microsoft Intune . You will need to create a custom managed profile to configure the domains for the Atlan browser extension. To deploy the .mobileconfig file for your organization, you can use any MDM platform. Microsoft Intune - follow the steps in Custom configuration profile settings . Microsoft Windows You will need to create registry keys to deploy the extension. You can create the required registry keys with a PowerShell script, which can then be deployed to your users devices using an MDM software. To deploy the PowerShell configuration script for your organization, you can use any MDM platform. Microsoft Intune - follow the steps in Create a script policy and assign it . For Script settings , enter the following details: Script location - upload the .ps1 configuration script downloaded from Atlan. Run this script using the logged on credentials - change to No . Enforce script signature check - change to No . Run script in 64 bit PowerShell Host - change to Yes . Script location - upload the .ps1 configuration script downloaded from Atlan. Run this script using the logged on credentials - change to No . Enforce script signature check - change to No . Run script in 64 bit PowerShell Host - change to Yes . Verify and monitor the installation To ensure that the Atlan browser extension has been successfully deployed across all selected devices in your organization, you can: Verify the installation - after you have deployed the policies, check a few target devices to ensure that the extension was installed and configured correctly. Monitor compliance - monitor the compliance status of the policy and troubleshoot any issues. Your users will now be able to use the Atlan browser extension in a managed browser! ð Once the managed browser has synced with the latest configuration changes for your organization, the Atlan browser extension will be automatically installed and a new tab will open to indicate that the Atlan browser extension is now active. Configure the browser extension Bulk install the browser extension Deploy the configuration script Verify and monitor the installation


Atlan browser extension security | Atlan Documentation

Atlan adheres to strict security standards for the browser extension . Atlan mandates security throughout the extension coding lifecycle: Hardening configurations through content security policies, Validating all inputs, Requiring least privileges, Employing defense-in-depth techniques like code obfuscation to frustrate reverse engineering, Accessing customer resources over secure HTTPS channels after SSL certificate verification to prevent tampering. Atlan follows proven CI/CD methodologies used for our SaaS application, enabling rapid and frequent updates to Atlan's Chrome extension. This allows: Patching identified vulnerabilities faster through new releases while simultaneously upholding stability. Mandatory code reviews specifically focused on analyzing security to help with identifying issues before these can impact customers. Once ready, both static and dynamic scanning tools rigorously test the extension codebase for any weaknesses before distribution. Atlan is committed to transparency. If any post-deployment points of concern arise, Atlan will notify impacted customers promptly and address their concerns responsibly. By incorporating security into each phase - secure architecture, peer reviews, robust testing, and responsible disclosure - Atlan strives to build browser extensions with both user needs and enterprise risks top of mind. Reach out to Atlan support for any questions. When using Atlan's browser extension in a supported tool , Atlan will read: the URL of your browser tab Document Object Model (DOM) elements such as asset title, hierarchy information, text, data-test-id attributes, and more to locate an asset in a supported source tool . This list may vary depending on the source tool. If you're using Atlan's browser extension on any website , it will only read the favicon, page title, and URL of your browser tab. Atlan uses the following permissions for the browser extension to work in a supported tool: activeTab - the activeTab permission allows the browser extension to temporarily access the content of the active tab as you interact with the extension. This enables Atlan to display the Atlan badge and read the URL and DOM elements to locate the asset for displaying asset metadata in the sidebar. storage - the storage permission allows Atlan to store information about the locally domains configured. This enables the browser extension to remember the sites that you want to use it on, even when you close and reopen your browser. host_permissions - the host permissions allow the browser extension to work specifically with Atlan tenants, which is the host in this case. For example, https://atlan.com/* , https://atlan.dev/* . "content_scripts": [ { "matches": ["http://*/*", "https://*/*"] - the content_scripts key allows Atlan to inject Atlan's content script to any website you visit. Although this content script will be injected into all webpages, it will neither be executed nor any DOM elements captured if the webpage is not a supported tool.


Add a resource | Atlan Documentation

Need to redirect users to important information that's outside Atlan? You can add links to internal or external URLs wit hin an asset profile. These can help your team better understand the contextual information for your asset. To add resources to your assets, follow these steps: On the Atlan homepage, click Assets in the left menu. Click on an asset to open the asset profile. In the navigation bar to the right of the asset profile, click Resources . Click +Add Resource and paste your URL. For Title , type a title for your resource. Your resource is now ready to use! ð Once you've added a resource, click +Add in the Resource menu to add more resources for your asset. You can also edit or delete them to curate your list of resources. You can also add any web page as a resource to your assets using Atlan's Chrome extension .


Enable embedded metadata in Tableau | Atlan Documentation

Atlan metadata layers Atlan context directly onto the source application, rather than in a sidebar. This embedded experience provides users with immediate access to data lineage, quality metrics, and governance information without leaving their Tableau workflow. Before enabling embedded metadata in Tableau: You must have the Atlan browser extension installed. If not, see the How to use the Atlan browser extension guide for instructions. Tableau dashboards must be available through the browser Permissions required To enable this feature, you need: Admin role in Atlan Access to the Labs settings Enable embedded metadata in Tableau To enable the embedded Atlan experience in Tableau for your users: From the left menu in Atlan, click Admin . From the left menu in Atlan, click Admin . Under Workspace , click Labs . Under Workspace , click Labs . Under the Access Control heading of the Labs page, turn on View embedded metadata in Tableau Under the Access Control heading of the Labs page, turn on View embedded metadata in Tableau Once enabled, users with the extension installed can view Atlan metadata in Tableau dashboards. Once enabled, users with the extension installed can view Atlan metadata in Tableau dashboards. See also Troubleshoot the Atlan browser extension Use the Atlan browser extension Tableau connector documentation Enable embedded metadata in Tableau


What does Atlan crawl from Amazon QuickSight? | Atlan Documentation

Atlan currently supports lineage for the Amazon QuickSight connector to the following data sources: Microsoft SQL Server Atlan crawls and maps the following assets and properties from Amazon QuickSight. Atlan maps analyses from Amazon QuickSight to its QuickSightAnalysis asset type. Atlan maps dashboards from Amazon QuickSight to its QuickSightDashboard asset type. Atlan maps datasets from Amazon QuickSight to its QuickSightDataset asset type. Atlan maps folders from Amazon QuickSight to its QuickSightFolder asset type. Dataset fields Atlan maps dataset fields from Amazon QuickSight to its QuickSightDatasetField asset type. Analysis visuals Atlan maps analysis visuals from Amazon QuickSight to its QuickSightAnalysisVisual asset type. Dashboard visuals Atlan maps dashboard visuals from Amazon QuickSight to its QuickSightDashboardVisual asset type.


What does Atlan crawl from Databricks? | Atlan Documentation

Atlan crawls and maps the following assets and properties from Databricks. The following properties aren't crawled by the System tables extraction method: Table properties : partitionList , partitionCount Column properties : maxLength , precision Atlan maps databases from Databricks to its Database asset type. Atlan maps schemas from Databricks to its Schema asset type. Atlan maps tables from Databricks to its Table asset type. Atlan maps views from Databricks to its View asset type. Materialized views Atlan maps materialized views from Databricks to its MaterialisedView asset type. To help you work seamlessly with STRUCT data types, Atlan supports nested columns up to level 30 in Databricks. You can view these columns in the Tree view or the asset sidebar of your table assets, and also explore child columns of STRUCTs nested within MAPs or ARRAYs. However, lineage for nested columns isn't supported. Atlan maps columns from Databricks to its Column asset type.


What does Atlan crawl from dbt Cloud? | Atlan Documentation

Atlan crawls and maps the following assets and properties from dbt Cloud. Atlan also supports lineage between the following: SQL tables and views materialized by dbt models, dbt seeds, dbt sources Column-level lineage for these entities Atlan only crawls dbt assets that are in the applied (built) state in dbt Cloud. Models must be part of a successful run to be picked up during crawling; models that are only defined in your project files but haven t been executed won t be included. For more information about project state, see Project states in dbt Cloud. Once you've crawled dbt , you can use dbt-specific filters for quick asset discovery: Test status - filter dbt tests that passed, failed, or have a warning or error Alias - filter by the name of a dbt model's identifier in the dbt project Unique id - filter by the unique node identifier of a dbt model Project name - filter by dbt project name, only supported for dbt Core version 1.6+ Environment name - filter by dbt environment name Job status - filter by dbt job status Last job run - filter by the last run of the dbt job Atlan's dbt connectivity also populates custom metadata to further enrich the assets in Atlan. The Atlan dbt-specific property column in the tables below gives the name of the mapped custom metadata property in Atlan. Atlan enables you to sync your dbt tags and update your dbt assets with the synced tags. It's also possible to map other metadata on Atlan's assets through your dbt models . Atlan maps tables from dbt Cloud to its Table asset type. Atlan maps columns from dbt Cloud to its Column asset type. Atlan maps models from dbt Cloud to its Model asset type. Atlan maps sources from dbt Cloud to its DbtSource asset type. Atlan maps tests from dbt Cloud to its Test asset type. Atlan maps models from dbt Core to its Seed asset type.


What does Atlan crawl from Google BigQuery? | Atlan Documentation

Once you have crawled Google BigQuery , you can use connector-specific filters for quick asset discovery. The following filters are currently supported for these assets: Tables - BigQuery labels and Is sharded filters Atlan doesn't run any table scans. Atlan leverages the table preview options from Google BigQuery that enable you to view data for free and without affecting any quotas using the tabledata.list API. Hence, table asset previews in Atlan are already cost-optimized. However, this doesn't apply to views and materialized views . For Google BigQuery views and materialized views , Atlan sends you a cost nudge before viewing a sample data preview. This informs you about the precise bytes that are spent during the execution of the query, helping you decide if you still want to run the preview. You also receive a cost nudge before querying your Google BigQuery assets . Atlan crawls and maps the following assets and properties from Google BigQuery. Atlan maps projects from Google BigQuery to its Database asset type. Atlan maps datasets from Google BigQuery to its Schema asset type. Table asset previews are already cost-optimized. Google BigQuery enables you to use the table preview options to view data for free and without affecting any quotas. Note that this isn't currently supported for Google BigQuery views and materialized views in Atlan. Atlan maps tables from Google BigQuery to its Table asset type. Atlan maps views from Google BigQuery to its View asset type. Materialized views Atlan maps materialized views from Google BigQuery to its MaterialisedView asset type. Atlan supports nested columns up to level 1 for Google BigQuery to help you enrich your semi-structured data types. You can view nested columns in the asset sidebar for your table assets. Atlan maps columns from Google BigQuery to its Column asset type. Atlan doesn't crawl primary key (PK) and foreign key (FK) information from Google BigQuery. Stored procedures Atlan maps stored procedures from Google BigQuery to its Procedure asset type.


What does Atlan crawl from IBM Cognos Analytics? | Atlan Documentation

Atlan crawls and maps the following assets and properties from IBM Cognos Analytics. Atlan also supports lineage: For packages, files, reports, and modules. To upstream sources - Microsoft SQL Server and Snowflake. Field-level lineage is currently not supported. Atlan generates the sourceURL property for IBM Cognos Analytics assets using a combination of the host, port, and id of the asset. This allows Atlan to help you view your assets directly in IBM Cognos Analytics from the asset profile. Direct extraction - in addition to id , Atlan obtains the host and port values from the credentials you provided while setting up a crawler workflow. Offline extraction - in addition to id , Atlan obtains the host and port values from the parameters with which the offline extractor is executed. Assets marked with ð includes lineage and column-level lineage. Assets marked with ð display column information. Atlan maps folders from IBM Cognos Analytics to its CognosFolder asset type. Dashboards ð Atlan maps dashboards from IBM Cognos Analytics to its CognosDashboard asset type. Packages ð Atlan maps packages from IBM Cognos Analytics to its CognosPackage asset type. Explorations ð Atlan maps explorations from IBM Cognos Analytics to its CognosExploration asset type. Reports ð Atlan maps reports from IBM Cognos Analytics to its CognosReport asset type. Files ð Atlan maps files from IBM Cognos Analytics to its CognosFile asset type. Data sources Atlan maps data sources from IBM Cognos Analytics to its CognosDatasource asset type. Modules ð Atlan maps modules from IBM Cognos Analytics to its CognosModule asset type. Atlan maps fields from IBM Cognos Analytics to its CognosColumns asset type. Based on the asset type, some attributes may not be extracted: cognosColumnRegularAggregate appears only for reports and datasets. cognosColumnDatatype appears only for modules.


What does Atlan crawl from Looker? | Atlan Documentation

Atlan crawls and maps the following assets and properties from Looker. Atlan also supports the following lineage: Asset-level lineage for views, models, looks, dashboards, tiles, and explores. Field-level lineage for views, explores, looks, tiles, and dashboards. Lineage between explore fields and dashboards. This allows you to view all the fields used in a given dashboard and trace their upstream lineage to SQL columns. Cross-project lineage for Looker assets. For example, if an explore includes a view from an imported project, Atlan will parse project manifest files to generate lineage. Looker refinements for views and explores. Atlan will parse project manifest files to generate lineage. Refined fields for views and explores are displayed with a Refinement label in Atlan. Currently Atlan only represents the assets marked with ð in lineage. Atlan maps connections from Looker to its Connection asset type. Atlan maps projects from Looker to its LookerProject asset type. Views ð Atlan maps views from Looker to its LookerView asset type. To trace the upstream lineage of these views, Atlan currently supports SQL-based derived tables . Persistent derived tables (PDTs) and Liquid parameterized tables are currently not supported. However, Atlan will always catalog the associated views. Atlan also supports view refinements . Atlan includes the fields from refinements in the parent view asset, and marks the fields with a Refinement label. You can hover over the label to view the file path and line number where the refinement is defined. Models ð Atlan maps models from Looker to its LookerModel asset type. Atlan maps folders from Looker to its LookerFolder asset type. Fields ð For explores Atlan maps fields for explores from Looker to its LookerField asset type. For views Atlan maps fields for views from Looker to its LookerField asset type. For looks Atlan maps fields for looks from Looker to its LookerField asset type. For tiles Atlan maps fields for tiles from Looker to its LookerField asset type. For dashboards Atlan maps fields for dashboards from Looker to its LookerField asset type. Looks ð Atlan maps looks from Looker to its LookerLook asset type. Dashboards ð Atlan maps dashboards from Looker to its LookerDashboard asset type. Tiles ð Atlan maps tiles from Looker to its LookerTile asset type. Explores ð Atlan maps explores from Looker to its LookerExplore asset type. Atlan also supports explore refinements : For explores defined in the same model, Atlan includes the fields from refinements in the parent explore asset. For explores with the same name that are defined in a different model, Atlan will create a new explore asset. In both cases, Atlan marks the fields with a Refinement label. You can hover over the label to view the file path and line number where the refinement is defined.


What does Atlan crawl from Microsoft Power BI? | Atlan Documentation

Atlan crawls and maps the following assets and properties from Microsoft Power BI. Once you've crawled Microsoft Power BI , you can use connector-specific filters for quick asset discovery. The following filters are currently supported for these assets: Measures - External measure filter Currently Atlan only represents the assets marked with ð in lineage. For your Microsoft Power BI reports , Atlan also provides asset previews to help with quick discovery and give you the context you need. Atlan maps Apps from Microsoft Power BI to its PowerBIApp asset type. Atlan maps workspaces from Microsoft Power BI to its PowerBIWorkspace asset type. Dashboards ð Atlan maps dashboards from Microsoft Power BI to its PowerBIDashboard asset type. Data sources Atlan maps data sources from Microsoft Power BI to its PowerBIDatasource asset type. Datasets ð Atlan maps datasets from Microsoft Power BI to its PowerBIDataset asset type. Dataflows ð Atlan maps dataflows from Microsoft Power BI to its PowerBIDataflow asset type. Atlan currently only supports dataflow lineage for the following SQL sources: Microsoft SQL Server Dataflow entity columns ð Atlan maps attributes of dataflow entities from Microsoft Power BI to its PowerBIDataflowEntityColumn asset type. Reports ð Atlan maps reports from Microsoft Power BI to its PowerBIReport asset type. Pages ð Atlan maps pages from Microsoft Power BI to its PowerBIPage asset type. Tiles ð Atlan maps tiles from Microsoft Power BI to its PowerBITile asset type. Tables ð Atlan maps tables from Microsoft Power BI to its PowerBITable asset type. Columns ð Atlan maps columns from Microsoft Power BI to its PowerBIColumn asset type. Measures ð Atlan maps measures from Microsoft Power BI to its PowerBIMeasure asset type. Atlan supports PowerBI Measures for downstream lineage to a PowerBI Page. Dataflow entity columns ð


What does Atlan crawl from Mode? | Atlan Documentation

Atlan crawls and maps the following assets and properties from Mode. Atlan maps workspaces from Mode to its ModeWorkspace asset type. Atlan maps collections from Mode to its ModeCollection asset type. Atlan maps reports from Mode to its ModeReport asset type. Atlan maps queries from Mode to its ModeQuery asset type. Atlan maps charts from Mode to its ModeChart asset type.


What does Atlan crawl from Qlik Sense Cloud? | Atlan Documentation

Atlan crawls and maps the following assets and properties from Qlik Sense Cloud. Once you've crawled Qlik Sense Cloud , you can use connector-specific filters for quick asset discovery. The following filters are currently supported for these assets: Atlan only supports asset-level lineage for the following asset types: Datasets --> Charts --> Sheets --> Apps Atlan maps spaces from Qlik Sense Cloud to its QlikSpace asset type. Atlan maps apps from Qlik Sense Cloud to its QlikApp asset type. Only the app resource type is retrieved. Other types, such as qvapp or qlikview , are not crawled. Atlan maps sheets from Qlik Sense Cloud to its QlikSheet asset type. Atlan maps charts from Qlik Sense Cloud to the QlikChart asset type and catalogs only those linked to dataset fields. For example, table charts are crawled because their columns represent dataset dimensions or measures. UI elements that do not reference dataset fields - such as filters, buttons, and text elements - are ignored. These elements are not considered charts and are not crawled: filterpane , qlik-button-for-navigation , VizlibAdvancedTextObject , listbox , action-button , VizlibFilter , variable , text-image , VizlibLineObject . Atlan maps datasets from Qlik Sense Cloud to the QlikDataset asset type. Datasets loaded through the Data Load Editor are called implicit datasets in Atlan and appear under this type.


What does Atlan crawl from Redash? | Atlan Documentation

Atlan crawls and maps the following assets and properties from Redash. Once you've crawled Redash , you can use connector-specific filters for quick asset discovery. The following filters are currently supported for these assets: Queries - Schedule, Is Published, and Redash tags filters Visualizations - Type filter Dashboards - Redash tags filter Currently, Atlan only represents the assets marked with ð in lineage. Queries ð Atlan maps queries from Redash to its RedashQuery asset type. Dashboards ð Atlan maps dashboards from Redash to its RedashDashboard asset type. Visualizations ð Atlan maps visualization elements from Redash to its RedashVisualization asset type.


What does Atlan crawl from Salesforce? | Atlan Documentation

Atlan only performs GET requests on these five endpoints: sObject Basic Information Each endpoint will be set in its own OAuth client session. For every API request, it will hit the Salesforce login endpoint, which means there will be at least five (same as the number of endpoints above) login entries in your Salesforce account's login history within the duration of the scheduled workflow run. Atlan crawls and maps the following assets and properties from Salesforce. Once you've crawled Salesforce , you can use connector-specific filters for quick asset discovery. The following filters are currently supported for these assets: Fields - Is encrypted and Is required filters Atlan maps organizations from Salesforce to its SalesforceOrganization asset type. Atlan maps objects from Salesforce to its SalesforceObject asset type. Atlan maps fields from Salesforce to its SalesforceField asset type. Atlan maps reports from Salesforce to its SalesforceReport asset type. Atlan maps dashboards from Salesforce to its SalesforceDashboard asset type.


What does Atlan crawl from Sigma? | Atlan Documentation

Atlan crawls and maps the following assets and properties from Sigma. Currently, Atlan only represents the assets marked with ð in lineage. For your Sigma workbooks , Atlan also provides asset previews to help with quick discovery and give you the context you need. Workbooks ð Atlan maps workbooks from Sigma to its SigmaWorkbook asset type. Pages ð Atlan maps pages from Sigma to its SigmaPage asset type. Data elements ð Atlan maps table, pivot table, and visualization elements from Sigma to its SigmaDataElement asset type. Data element fields ð Atlan maps table, pivot table, and visualization element fields from Sigma to its SigmaDataElementField asset type. Atlan maps datasets from Sigma to its SigmaDataset asset type. Data elements ð Data element fields ð


What does Atlan crawl from Snowflake? | Atlan Documentation

Atlan crawls and maps the following assets and properties from Snowflake. Once you've crawled Snowflake , you can use connector-specific filters for quick asset discovery. The following filters are currently supported for Snowflake assets: Streams - Source type and Stale filters Functions - Language, Function type, Is secure, and Is external filters Snowflake tags and tag values Atlan supports lineage for the following asset types: External Named Stages Pipe Table Internal Named Stages Pipe Table (auto-ingest not recommended) Not supported for External or Iceberg Tables Atlan maps databases from Snowflake to its Database asset type. Atlan maps schemas from Snowflake to its Schema asset type. Atlan maps tables from Snowflake to its Table asset type. For Iceberg tables In addition to the table metadata above, Atlan supports additional metadata for Iceberg tables crawled from Snowflake. Atlan currently supports fetching metadata for Iceberg tables only for the information schema extraction method. Atlan maps views from Snowflake to its View asset type. Materialized views Atlan maps materialized views from Snowflake to its MaterialisedView asset type. External tables Atlan maps external tables from Snowflake to its Table asset type. Atlan maps columns from Snowflake to its Column asset type. Atlan maps stages from Snowflake to its Stage asset type. Atlan maps streams from Snowflake to its Stream asset type. Atlan maps pipes from Snowflake to its Pipe asset type. User-defined functions Atlan maps user-defined functions (UDFs) from Snowflake to its Function asset type. Atlan currently does not support lineage for user-defined functions from Snowflake. Dynamic tables Atlan maps dynamic tables from Snowflake to its DynamicTable asset type.


What does Atlan crawl from Tableau? | Atlan Documentation

Atlan crawls and maps the following assets and properties from Tableau. Once you've crawled Tableau , you can use connector-specific filters for quick asset discovery. The following filters are currently supported for these assets: Projects - filter Tableau assets by projects, including nested projects Data sources - Is published filter For your Tableau worksheets and dashboards , Atlan also provides asset previews to help with quick discovery and give you the context you need. You may need to disable clickjack protection for Tableau asset previews to load. Did you know? Lineage to dashboards may appear incomplete or missing if worksheets are not crawled. Additionally, Tableau assets that haven't been refreshed since May 27, 2025, won't display the new column-level lineage (CLL) or updated lineage paths. Atlan supports lineage for the following: Asset Lineage - Datasource to Dashboard, Datasource to Worksheet, Datasource to Workbook Column Level Lineage - Supported for Datasource to Worksheet and Worksheet to Dashboard Atlan maps sites from Tableau to its TableauSite asset type. Atlan maps projects from Tableau to its TableauProject asset type. Due to limitations at source, Atlan won't be able to crawl Tableau flows if you use the JWT bearer authentication method. Atlan maps flows from Tableau to its TableauFlow asset type. Tableau has retired metrics methods in API 3.22 for Tableau Cloud and Tableau Server version 2024.2. If you're using Tableau API version 3.22 or higher, metadata for metrics is unavailable in Atlan. Atlan maps metrics from Tableau to its TableauMetric asset type. Atlan maps workbooks from Tableau to its TableauWorkbook asset type. Atlan maps worksheets from Tableau to its TableauWorksheet asset type. Atlan maps dashboards from Tableau to its TableauDashboard asset type. Data sources Atlan maps data sources (embedded and published) from Tableau to its TableauDatasource asset type. Data source fields Atlan maps data source fields and column fields from Tableau to its TableauDatasourceField asset type. Custom SQL Atlan parses custom SQL queries used in Tableau data sources to extract lineage information. This process identifies the relationships between data assets based on the SQL logic defined within Tableau. Calculated fields Atlan maps calculated fields from Tableau to its TableauCalculatedField asset type. Atlan calculates lineage for Tableau as follows: Lineage is currently not supported for Tableau flows and metrics . Data source fields


What does Atlan crawl from ThoughtSpot? | Atlan Documentation

Once you've crawled ThoughtSpot , you can use connector-specific filters for quick asset discovery. The following filters are currently supported for all ThoughtSpot assets: Tags and chart type filters Atlan supports lineage for the following ThoughtSpot assets: Answers - upstream lineage to tables, views, or worksheets from multiple sources (if applicable), no downstream lineage Visualizations - upstream lineage to tables, views, or worksheets from multiple sources (if applicable) Liveboards - upstream lineage to visualizations Tables - upstream lineage to source tables, and column-level lineage between ThoughtSpot tables and worksheets Views - upstream lineage to ThoughtSpot tables or worksheets, and column-level lineage between ThoughtSpot views and worksheets Worksheets - upstream lineage to ThoughtSpot tables or views from multiple sources (if applicable) Atlan crawls and maps the following assets and properties from ThoughtSpot. Currently, Atlan only represents the assets marked with ð in lineage. Answers ð Atlan maps answers from ThoughtSpot to its ThoughtSpotAnswer asset type. Visualizations ð Atlan maps visualizations from ThoughtSpot to its ThoughtspotDashlet asset type. Liveboards ð Atlan maps Liveboards from ThoughtSpot to its ThoughtspotLiveboard asset type. Tables ð Atlan maps tables from ThoughtSpot to its ThoughtspotTable asset type. Views ð Atlan maps views from ThoughtSpot to its ThoughtspotView asset type. Worksheets ð Atlan maps worksheets from ThoughtSpot to its ThoughtspotWorksheet asset type. Columns ð Atlan maps columns from ThoughtSpot to its ThoughtspotColumn asset type.


What does Atlan crawl from MicroStrategy? | Atlan Documentation

Atlan crawls and maps the following assets and properties from MicroStrategy. Currently Atlan only represents the assets marked with ð in lineage. Once you've crawled MicroStrategy , you can use connector-specific filters for quick asset discovery. The following filters are currently supported for these assets: Projects , attributes , facts , metrics , cubes , reports , documents , dossiers , and visualizations - Is Certified filter Cubes , reports , and visualizations - Type filter Atlan maps projects from MicroStrategy to its MicroStrategyProject asset type. Atlan maps attributes from MicroStrategy to its MicroStrategyAttribute asset type. Atlan maps facts from MicroStrategy to its MicroStrategyFact asset type. Atlan maps metrics from MicroStrategy to its MicroStrategyMetric asset type. Cubes ð Atlan maps cubes from MicroStrategy to its MicroStrategyCube asset type. Reports ð Atlan maps reports from MicroStrategy to its MicroStrategyReport asset type. Documents ð Atlan maps documents from MicroStrategy to its MicroStrategyDocument asset type. Dossiers ð Atlan maps dossiers from MicroStrategy to its MicroStrategyDossier asset type. Atlan maps dossier visualizations from MicroStrategy to its MicroStrategyVisualization asset type.


Administrators | Atlan Documentation

User management User management is a critical part of data governance. Atlan's user management capabilities should be a mainstay of how you organize and control access for people in your organization. Add and manage users from the admin center It's super simple to invite and remove users from Atlan from the Admin center . You can also manage existing users by adding them to groups, changing their roles, or set up SSO , SCIM , and SMTP configurations. Manage access control from the governance center The Governance center is where you can build access control mechanisms to manage user access . Personas allow you to group users into teams, such as Financial Analysts or Cloud Engineers , and set policies based on the access those personas should have. Purposes are where you can build policies based on the actions or access that a user might need. For example, you can use Atlan's policy-based access controls to manage access to PII and other sensitive data. This is a best practice for data governance. Once you set these policies, Atlan will enforce them throughout your users' experience. This means that users who don't have access to a particular type of data will not be able to see it. Governance workflows help you set up robust controls on data access management, metadata enrichment, new entity creation, and more, with out-of-the-box workflow templates and automated execution. Asset profile The asset profile in Atlan gives you a quick and clear understanding of what a data asset contains. You can think of the asset profile as the TL;DR about your data. The glossary provides key intel on your data assets so you can quickly understand important attributes of your data, such as: Owners of your data, so you know who to ask for clarification. Certificate status, to easily understand if metadata enrichment is still in progress or the asset is ready to be used. Linked assets that are relevant to the term, so you can explore other helpful material. Here are a few of the things that make Atlan's discovery awesome: Intelligent keyword recognition sees through your typos to show exactly what you wanted, no matter what you actually typed. Sort by popularity to quickly discover what assets your teammates are using every day.


Administrators | Atlan Documentation


Invite new users | Atlan Documentation

You will need to be an admin user in Atlan to invite users. Usernames in Atlan are of a permanent nature. Atlan uses usernames as a unique identifier across the platform and does not support making any changes to them. When logging into Atlan for the first time, ensure that you configure your username as per your preference. Without SSO To invite new users to Atlan, without SSO: From the left menu of any screen, click Admin . From the left menu of any screen, click Admin . Under Workspace click Users . Under Workspace click Users . Click the Invite Users button. Click the Invite Users button. Under Invite users to Default enter one or more email addresses of the users to invite. danger Atlan does not allow the use of disposable email addresses. You will receive an error indicating this if you attempt to send an invitation to one. Under Invite users to Default enter one or more email addresses of the users to invite. Atlan does not allow the use of disposable email addresses. You will receive an error indicating this if you attempt to send an invitation to one. (Optional) To the right of each email, click Member to change the role of the user . (Optional) To the right of each email, click Member to change the role of the user . Click the Send Invite button. Click the Send Invite button. Your user(s) will now receive an email with a link to sign up on Atlan! ð Note that the invitation link will remain valid for 7 days. If the link expires, you can resend the invitation to your new users. With SSO When SSO is enforced , you will not be able to invite users in Atlan - they can only be invited through the SSO provider. Any users mapped to the SAML app can log into Atlan via SSO. A user profile will be generated for them automatically, if one does not already exist. Admins can also assign default user roles for SSO to give appropriate permissions to users as soon as they log into Atlan.


Manage users | Atlan Documentation

You will need to be an admin user in Atlan to manage other users. As an admin user in Atlan, you can: Change a user's role Temporarily disable or permanently remove a user Reactivate a disabled user Change a user's role To change a user's role: From the left menu of any screen, click Admin . Under Workspace , click Users . Under the Role column, on a given user's row, click the role name. Under Change Role , select the new role to give the user, and then click Change . That's it, the user's role has now been changed! ð Deactivate a user To deactivate a user, you can either disable or remove them from Atlan. For example, you can disable a user to temporarily suspend their access to Atlan and reactivate it at a future date. If a user leaves the organization, you can remove their access. Atlan recommends that you proceed with caution if you want remove a user. While a disabled user can be reactivated , removing a user is a permanent and irreversible action. If a removed user needs to be restored to Atlan later on, you will need to add them as a new user. You can remove users irrespective of whether you're using basic authentication, SSO, or SCIM provisioning. Note that if you're using SCIM provisioning, disabling or reactivating users in Atlan is not allowed . If a SCIM-provisioned user is unassigned from the Atlan app in the identity provider, that user will be disabled in Atlan as well. Only then will you have the option to remove that user permanently. To deactivate a user: From the left menu of any screen, click Admin . Under Workspace , click Users . Scroll the table all the way to the right, if necessary. On an active user's row, click the 3-dot menu button and then from the dropdown: To temporarily remove a user, click Disable user and then click Disable . To permanently remove a user, click Remove user . In the Remove user dialog, for Transfer ownership , select an existing user to transfer any and all assets and workflows owned by the user you want to remove. Depending on the volume of assets to be transferred, the user removal process may take 15 minutes to a few hours to complete. You will be notified via email upon completion. Check the I understand this action can't be reversed and want to permanently remove this user box. Click Remove user . To temporarily remove a user, click Disable user and then click Disable . To permanently remove a user, click Remove user . In the Remove user dialog, for Transfer ownership , select an existing user to transfer any and all assets and workflows owned by the user you want to remove. Depending on the volume of assets to be transferred, the user removal process may take 15 minutes to a few hours to complete. You will be notified via email upon completion. Check the I understand this action can't be reversed and want to permanently remove this user box. Click Remove user . In the Remove user dialog, for Transfer ownership , select an existing user to transfer any and all assets and workflows owned by the user you want to remove. Depending on the volume of assets to be transferred, the user removal process may take 15 minutes to a few hours to complete. You will be notified via email upon completion. Check the I understand this action can't be reversed and want to permanently remove this user box. Click Remove user . That's it, the user is now deactivated and will no longer be able to access Atlan. ð ¢ Deactivated user accounts do not count towards the total number of Atlan licenses procured by your organization. If the user you want to disable is a connection admin , you will need to ensure that other users can manage the connection before disabling the account. You can modify a connection to add more connection admins. Reactivate a user You can only reactivate a disabled user's account. To reactivate a user: From the left menu of any screen, click Admin . Under Workspace , click Users . Scroll the table all the way to the right, if necessary. On a deactivated user's row, click the 3-dot menu button. Click Enable user , and then Enable . That's it, the user can once again access Atlan! ð Atlan has a retention policy of 60 days for user login events. If a user has not logged into Atlan for more than 60 days, the Last Active column will display - for the user. Change a user's role Deactivate a user Reactivate a user


SSO Integration | Atlan Documentation

Get started How to enable Azure AD for SSO How to enable Google for SSO How to enable JumpCloud for SSO How to enable Okta for SSO How to enable OneLogin for SSO How to enable SAML 2.0 for SSO Authenticate SSO credentials to query data Authenticate SSO credentials to view sample data How to limit SSO automatically creating users when they log in How to set default user roles for SSO SSO integration with PingFederate using SAML Troubleshooting connector-specific SSO authentication Why do I get a 404 error when using PingFederate SSO? Why do I get an authentication error when logging in via Okta for the first time? Why do I get an error while logging in via Google dashboard? Unable to log into Atlan via SSO due to an internal error from Microsoft Defender Can Atlan integrate with multiple Azure AD tenants within a single instance? Can we use a Microsoft SSO login? What type of user provisioning does Atlan support for SSO integrations? When does Atlan become a personal data processor or subprocessor? Why did my users not receive an invite email from Atlan?


Configure SCIM provisioning | Atlan Documentation

You can automate the process of provisioning and deprovisioning your users and groups in Atlan with System for Cross-domain Identity Management (SCIM). Atlan supports SCIM 2.0 for SCIM provisioning. SCIM provisioning works in combination with your single sign-on (SSO) setup. Setting up SCIM enables you to manage all your users from one central location. Atlan currently supports SCIM provisioning for the following SSO providers: For more questions about SCIM provisioning, head over to Troubleshooting SCIM provisioning .


Configure SMTP | Atlan Documentation

You will need to be an admin user in Atlan to configure SMTP. The default SMTP setup is preconfigured by Atlan. You should only update this configuration if you want to set up custom SMTP. Atlan uses SMTP to send emails, primarily for things like inviting users, login failure alerts, and scheduled queries . We provide an embedded SMTP server to do this, out-of-the-box. If desired, you can override this embedded SMTP se rver with your own. To override the embedded SMTP server: From the left menu of any screen, click Admin . Under Workspace , click SMTP . Fill in the configuration of your SMTP server, at least: For Host the fully-qualified hostname of the SMTP server. For From Email the email address that should be used to send emails from the server. For Username the username required by your SMTP server. For Host the fully-qualified hostname of the SMTP server. For From Email the email address that should be used to send emails from the server. For Username the username required by your SMTP server. At the bottom of the page, click the Test SMTP Config button to test your configuration. This will attempt to send an email to your profile's email address. Once you successfully receive the test email, at the bottom of the page click Save .


Control access to metadata and data? | Atlan Documentation

You can customize access for users through several mechanisms. User roles The most general mechanism is a user role . These define the very broad permissions a user has in Atlan - for example, whether they can administer other users, or only discover metadata. When it comes to what metadata and data a user can access, though, we need to use the additional mechanisms below. Connection admins Connection admins are users who manage connectivity to a data source. By default, these users can: Read and write all metadata on assets from that connection. Preview and query the data in all data assets from that connection. Manage access policies to grant others access to the assets from that connection. You define the connection admin when crawling a new data source for the first time. A connection admin can also extend the list of connection admins on their connection at any time. Access policies A user must be both an admin user and a connection admin to define access policies for the connection's assets. Access policies either allow or restrict access to certain assets. These allow you to be much more creative (and granular) about access than the all-or-nothing privileges of connection admins. You start by defining which assets to control with each policy. There are two complementary mechanisms to do this in Atlan - personas and purposes . Once you have defined the subset of assets, you can then define granular access to both metadata and data: Metadata policies Metadata policies control what users can do with the assets' metadata. Through them, you can control who can: Read : view an asset's activity log, custom metadata, and SQL queries Update : change asset metadata, including description, certification, owners, README, and resources Update Custom Metadata Values for the assets Add Tags to the assets Remove Tags from the assets Create : create new assets within the selected connection (via API) Delete : delete assets within the selected connection (via API) Data policies Data policies control what users can do with the assets' data. Through them, you can control who can: Query and preview the data within the assets Whether to hide any data, through various masking techniques: Show first 4 : replaces all the data with X except the first 4 characters of data. For example 1234 5678 9012 3456 would become 1234XXXX . Show last 4 : replaces all the data with X except the last 4 characters of data. For example 1234 5678 9012 3456 would become XXXX3456 . Hash : replaces the data with a consistent hashed value. Because the hash is consistent you can still join on it across assets. For example 1234 5678 9012 3456 would become f43jknscakc12nk21ak . Nullify : replaces the data with the null value. For example 1234 5678 9012 3456 would become null . Redact : replaces all alphabetic data with x and all numeric data with 0. For example 1234 Street Name would become 0000 Xxxxxx Xxxx . Show first 4 : replaces all the data with X except the first 4 characters of data. For example 1234 5678 9012 3456 would become 1234XXXX . Show last 4 : replaces all the data with X except the last 4 characters of data. For example 1234 5678 9012 3456 would become XXXX3456 . Hash : replaces the data with a consistent hashed value. Because the hash is consistent you can still join on it across assets. For example 1234 5678 9012 3456 would become f43jknscakc12nk21ak . Nullify : replaces the data with the null value. For example 1234 5678 9012 3456 would become null . Redact : replaces all alphabetic data with x and all numeric data with 0. For example 1234 Street Name would become 0000 Xxxxxx Xxxx . Glossary policies Glossary policies can only be defined through personas. All the mechanisms above can coexist. This is powerful, but can also be a bit overwhelming to think about. What takes priority when a user is under the control of all these mechanisms? ð µ ð « It's actually not as bad as you might think - only these three rules: Access is denied by default (implicitly) By default, users will not have the permissions listed above. This remains true until you explicitly grant a user a permission. For example, imagine you have not set up any access policies and a new user joins. They will not have any of the permissions above against any assets in Atlan. Explicit grants (allows) are combined When you grant a user a permission, this is combined with all other permissions you have granted the user. Continuing our example, imagine you add the new user to a group defined as the connection admins for Snowflake. The user will now have full read/write access to all metadata for Snowflake assets, and be able to query and preview the data in those assets. Then you add the user to a persona that gives read/write access to a Looker project. The user will now have access to all Snowflake assets and a Looker project's assets. Explicit restrictions (denies) take priority When you explicitly deny a user a permission, this takes priority over all other permissions you have granted the user. Continuing our example, imagine you define a purpose with a data policy that masks PII data. The user will still have full read/write access to all metadata for Snowflake assets and a Looker project's assets. In general, they will still be able to query and preview the data in the Snowflake assets. However, any PII data in Snowflake will now be masked. Then you add a metadata policy to the purpose that denies permission to remove the PII tag. The user will no longer have full read/write access to all metadata for Snowflake assets and a Looker project's assets. The user can no longer remove the PII tag from any of these assets. The combination of mechanisms in the example above shows their power. Through a small number of controls we can define wide-ranging but granular access permissions.


What are personas? | Atlan Documentation

Personas define policies to control which users can (or cannot) take certain actions on specific assets. They address a combination of two main objectives: Curating the assets that are relevant to a team of users Controlling the actions users can take on those assets (querying data, updating metadata, etc) Think of personas as a way of curating assets for a group of users. Team-based personalization Personas curate the assets that are discoverable by users, and the detailed metadata shown. In this way, users can focus on only those assets (and metadata) relevant to their role in the organization. This reduces distractions and "noise" for users. For example, a team of marketers may only work with a few data sets and dashboards. Rather than flooding the marketers with details about every asset in your company, you want to focus their attention. Broad-brush access control Combined with the personalization are broad-brush access control policies. When defining the policies in a persona, you not only select the assets but also what actions users can take on those assets. For example, your team of marketers should be able to describe their dashboards. But perhaps they should only be able to see the shared data sets that feed those dashboards, not change their descriptions or tags. You can define the persona so that they can read and write the dashboards, but only read the data sets. Broad-brush access control


What are purposes? | Atlan Documentation

Purposes provide ways to interact with tagged assets. They address two main objectives: Grouping assets together in ways they may be used by many teams - for example, by project or domain Controlling access to very granular, typically sensitive data When defining a purpose , you choose its tags. Atlan then considers all assets with at least one of those tags as part of the purpose. Think of purposes as a way of further protecting particularly sensitive data. Even if a user can see data in a table, you may not want them to see one or two sensitive columns within that table. Asset curation by domain One way you can use purposes is to curate assets. In this approach, the purpose's tag tends to be a domain. For example, this could be a project or an area of your organization's business. Through the purpose, you can grant permissions to assets with that tag. With purposes, any future assets given a tag will gain the same permissions - no policy changes needed. Granular data protection The other way you can use purposes is to enforce granular data protection. In this approach, the purpose's tag tends to be some level of information sensitivity. For example, this could be personally-identifiable information (PII) or confidential internal financial metrics. These sensitivity tags will tend to be against granular data assets - often columns. Personas tend to control permissions at a broader level, for example entire data sources, databases or schemas. Through these more granular tags, purposes give you more fine-grained control. And you can layer this on top of the permissions granted by personas . For example, you might grant permission to preview and query a database to a group of users through a persona . But you don't want those users to be able to see any PII data - specific columns - wherever they appear in the database. There could be hundreds of these columns, scattered across thousands of tables. By tagging the columns, you can restrict access to them through a single policy in a purpose. This way you don't need to maintain many separate per-column policies through a persona . Asset curation by domain Granular data protection


Automate data governance | Atlan Documentation

You must be an admin user in Atlan to enable , create , and manage governance workflows. Anyone with access to Atlan - admin, member, or guest user - can use the inbox . You can streamline your data governance requirements in Atlan with governance workflows and manage alerts, approvals, and tasks using the inbox . Governance workflows enable you to set up robust controls on data access management, metadata enrichment, new entity creation, and more, with out-of-the-box workflow templates and automated execution. For example, instead of allowing your users to directly query data or update the certification status of an asset, you can specify assets that require advanced controls and create governance workflows to govern them. These workflows will run in the background, ensure that all required approvals are in place, and only then approve users with appropriate permissions to perform any action. You can use governance workflows to ensure: Risk mitigation - determine how data is used and shared in your organization with automated access policies. Data security - manage requests for data access and processing to only allow access to authorized individuals or teams. Metadata change management - monitor and audit metadata changes to align with established organizational standards. New entity creation - manage and audit documentation of business context such as glossaries and tags to align with established organizational standards. Policy compliance - set up repeatable processes and approval flows for your data assets in Atlan to adhere to regulatory requirements - currently only applicable if you have also enabled the policy center module . Workflow properties A common set of properties are applicable to all governance workflows in Atlan: Only an admin user can create, update, or delete governance workflows. Out-of-the-box workflow templates. Predefined steps based on workflow selection. Must be associated with an asset type or action. Set up auto-approval rules for users, groups, or owners based on metadata attributes and policies. Activity logs for all workflows available by default. Visibility into the transition states of a workflow. Overlapping workflows - governance workflows provide you with the flexibility of creating workflows per team or business domain on the same set of assets instead of creating one complex workflow to cover all your use cases. Atlan will handle all the complexities, only allowing approvals to go through once all approval conditions have been met. Workflow templates You can choose from the following workflow templates to govern your assets and manage access: Change management This template allows you to control changes to metadata within your organization's data management and governance framework. Use cases include requests to: Add, update, and remove descriptions manually and using Atlan AI Add, update, and remove certificates Add, update, and remove an alias Add, update, and remove owners Attach, update, and remove tags Add, update, and remove custom metadata Add, update, and remove domains Add, update, and remove READMEs Add, update, and remove announcements Change management workflows will override any permissions assigned through user roles or access policies . For example, even for users with edit access , metadata update requests will go through change management workflows. If there are no change management workflows in place, then users with edit access will be able to update metadata while users without edit access will only be able to suggest changes to metadata . New entity creation This template allows you to control the creation and publication of new entities in Atlan. The new entity creation workflow will override existing glossary policies and user role permissions to create new entities. Creation of the following entities is currently supported for the new entity creation workflow: Data products : Creation of a new data product Change of a data product's status from Sunset , Archived , or Draft to Published Creation of a new data product Change of a data product's status from Sunset , Archived , or Draft to Published Access management This template allows you to automate the process of requesting, approving, and revoking access to data assets in Atlan. It includes the combination of a self-service approach as well as mandating human intervention for approval. You can also revoke data access in Atlan or other data sources. For data sources other than Atlan, you can configure additional actions to revoke data access in the data source. Use cases include requests to query data or view sample data for the following supported asset types - tables, views, and materialized views. Grant access in Atlan - allow requesters to request data access for querying data in Insights and previewing sample data within Atlan only. Raise Jira ticket to grant or revoke data access on source - allow requesters to request or revoke data access for any tool. Atlan will create a support ticket in Jira Cloud for your team to grant or revoke data access and display the status of your request in Atlan. You will need to: Integrate Jira Cloud and Atlan . Link your individual Jira Cloud account to Atlan . Install or register a webhook . Create an access management workflow to enable or revoke access everywhere using Jira. Add a Jira project and issue type and specify an issue status while creating the data access workflow. Your users will be granted access or their access will be revoked once the request is approved in Jira. Integrate Jira Cloud and Atlan . Link your individual Jira Cloud account to Atlan . Install or register a webhook . Create an access management workflow to enable or revoke access everywhere using Jira. Add a Jira project and issue type and specify an issue status while creating the data access workflow. Your users will be granted access or their access will be revoked once the request is approved in Jira. Add a Jira project and issue type and specify an issue status while creating the data access workflow. Your users will be granted access or their access will be revoked once the request is approved in Jira. Raise ServiceNow request to grant or revoke data access on source - allow requesters to request or revoke data access for any tool. Atlan will create a request in the Atlan Data Access catalog for your team in ServiceNow to grant or revoke data access and display the status of your request in Atlan. You will need to: Integrate ServiceNow and Atlan . Link your individual ServiceNow account to Atlan . Create a data access approval workflow to enable or revoke access everywhere using ServiceNow. Specify the request state(s) for approval while creating the data access workflow. Your users will be granted access or their access will be revoked once the request is approved in ServiceNow. Integrate ServiceNow and Atlan . Link your individual ServiceNow account to Atlan . Create a data access approval workflow to enable or revoke access everywhere using ServiceNow. Specify the request state(s) for approval while creating the data access workflow. Your users will be granted access or their access will be revoked once the request is approved in ServiceNow. Specify the request state(s) for approval while creating the data access workflow. Your users will be granted access or their access will be revoked once the request is approved in ServiceNow. Trigger a webhook - allow requesters to request or revoke data access for any tool. Atlan will trigger a webhook to a URL of your choice for your team to grant or revoke data access. For URL , enter the URL for where you want to receive events, including details on requester, approver, and asset, and then validate the URL. danger Atlan will send a sample payload to test if the webhook URL is correct. You must respond with a 2xx status for the validation to succeed. Atlan will also run this validation before you save your webhook as a precautionary measure. Copy the Secret Key and store it in a secure location to verify data access approval or revocation requests from Atlan. For URL , enter the URL for where you want to receive events, including details on requester, approver, and asset, and then validate the URL. danger Atlan will send a sample payload to test if the webhook URL is correct. You must respond with a 2xx status for the validation to succeed. Atlan will also run this validation before you save your webhook as a precautionary measure. For URL , enter the URL for where you want to receive events, including details on requester, approver, and asset, and then validate the URL. Atlan will send a sample payload to test if the webhook URL is correct. You must respond with a 2xx status for the validation to succeed. Atlan will also run this validation before you save your webhook as a precautionary measure. Copy the Secret Key and store it in a secure location to verify data access approval or revocation requests from Atlan. Copy the Secret Key and store it in a secure location to verify data access approval or revocation requests from Atlan. Policy approval You must enable the policy center module to use the policy approval workflow template. This template allows you to automate approvals for your data governance policies in Atlan. Automated policy approval workflows can help you streamline the approval process, facilitate compliance with regulatory standards, and simplify data governance for your organization. Use cases include requests to: Create new policies Revise existing policies Enable governance workflows and inbox You must be an admin user in Atlan to enable the governance workflows and inbox module for your organization. To enable governance workflows and inbox for your Atlan users: From the left menu of any screen in Atlan, click Admin . Under the Workspace heading, click Labs . On the Labs page, under Governance center , turn on Governance Workflows and Inbox to govern your assets and manage alerts, approvals, and tasks in Atlan more effectively. If you'd like to disable the Governance Workflows and Inbox module from your organization's Atlan workspace, follow the steps above to turn it off. Once enabled, you can also temporarily disable the module and turn it on again as needed. For any governance workflows you may have created or existing requests , this will not result in any data loss. Interactions with existing access control mechanisms Once you have turned on governance workflows and inbox, the module will interact with existing access control mechanisms in Atlan as follows: Requests : Atlan will channel requests and approvals through governance workflows and land them in the inbox. New requests - once you have enabled governance workflows and inbox, the requests widget will be replaced by an inbox and your member and guest users will not be able to raise any new requests until an admin user has created at least one governance workflow. To enable your member and guest users to raise new requests in Atlan: Create a change management governance workflow . Select all connections present in your Atlan workspace . Skip auto-approval . Select Anyone approves and list the users or groups designated as your Atlan admins . Publish your first governance workflow! Once published, this comprehensive workflow will allow your member and guest users to raise requests. Now you can focus on creating more use-case-driven workflows and consequently removing governed assets from the first workflow until you no longer need it. Existing requests - only admin users can take action on existing requests from the requests center . Your member and guest users will only be able to raise new requests on governed assets. New requests - once you have enabled governance workflows and inbox, the requests widget will be replaced by an inbox and your member and guest users will not be able to raise any new requests until an admin user has created at least one governance workflow. To enable your member and guest users to raise new requests in Atlan: Create a change management governance workflow . Select all connections present in your Atlan workspace . Skip auto-approval . Select Anyone approves and list the users or groups designated as your Atlan admins . Publish your first governance workflow! Once published, this comprehensive workflow will allow your member and guest users to raise requests. Now you can focus on creating more use-case-driven workflows and consequently removing governed assets from the first workflow until you no longer need it. Create a change management governance workflow . Select all connections present in your Atlan workspace . Skip auto-approval . Select Anyone approves and list the users or groups designated as your Atlan admins . Publish your first governance workflow! Once published, this comprehensive workflow will allow your member and guest users to raise requests. Now you can focus on creating more use-case-driven workflows and consequently removing governed assets from the first workflow until you no longer need it. Existing requests - only admin users can take action on existing requests from the requests center . Your member and guest users will only be able to raise new requests on governed assets. Metadata policies - your users must have read access to an asset for triggering governance workflows. If an asset is governed by a governance workflow, your users will be able to raise a request on that asset regardless of all allow/deny permissions in metadata policies. Data policies : No data policy exists - if the workflow connection allows querying and previewing sample data but a data policy has not been configured, your users will be able to raise a data access request on governed assets in the connection. Data policy with explicit restrictions - if an existing data policy denies querying and previewing sample data and assets are governed by a governance workflow, your users will not be able to raise a data access request on governed assets in the connection. Data policy with explicit grants - if an existing data policy allows querying and previewing sample data and assets are governed by a governance workflow, your users will be able to raise a data access request on governed assets in the connection. No data policy exists - if the workflow connection allows querying and previewing sample data but a data policy has not been configured, your users will be able to raise a data access request on governed assets in the connection. Data policy with explicit restrictions - if an existing data policy denies querying and previewing sample data and assets are governed by a governance workflow, your users will not be able to raise a data access request on governed assets in the connection. Data policy with explicit grants - if an existing data policy allows querying and previewing sample data and assets are governed by a governance workflow, your users will be able to raise a data access request on governed assets in the connection. Domain policies - governance workflows are currently not applicable to domain policies. User roles - if an asset is governed by a governance workflow, your users will be able to raise a request on that asset regardless of their role or permissions. For any asset not governed by a governance workflow, default role permissions will apply. Connection admins - if an asset is governed by a governance workflow, connection admins will have to go through the approval process for governed assets in the connection. Add, update, and remove resources Add a README to a term using Atlan AI Bulk updates through spreadsheet tools Bulk updates using playbooks Bulk updates using Atlan AI Bulk updates through API, SDK, and CLI operations Metadata updates in supported tools using Atlan browser extension Enable governance workflows and inbox


What are asset profiles? | Atlan Documentation

Every asset in Atlan has its own asset profile, which consists of all the information available for that particular asset. After you've discovered an asset, click to open the asset profile. This view gives you all the context you need about the asset. Components of an asset profile This section displays important details about the asset: Technical name and alias , if added Number of rows and columns Description of the asset Certification status (verified, draft, or deprecated) Owner of the asset For table profiles, you can also view the Columns tab. This tab allows you to update the metadata for your columns directly from the asset profile. Lineage offers a visual representation of the sources and transformations of your asset. You can also download lineage in a CSV file or as an image from here. Related assets Related assets displays all the assets that have associations with each other beyond a parent-child relationship. For example, a Microsoft Power BI workspace will generally have reports, datasets, dashboards, and dataflows, all of which are related to each other. Related assets are additionally listed in the Relations tab of the asset sidebar. Column preview Column preview offers a snapshot of all the columns in a data table, including the column name, data type, and description. This will change to Field preview in the asset profile and Fields tab in the asset sidebar for certain asset types - including but not limited to data source fields and calculated fields for Tableau data sources, columns for Microsoft Power BI tables, fields for Looker explores and views, and more. You can also export child assets such as columns or fields from the parent asset profile. Sample data Sample data shows the sample data for an asset. This helps users understand what kind of data is included in the asset and allows them to copy or export this data. Connection admins can also enforce users to validate their credentials before viewing sample data, helping you enforce better governance across your organization. Linked queries Linked queries displays any saved queries auto-linked to the asset when queried or referenced in the SQL query. This helps users quickly find the saved queries for additional context or launch the query in Insights directly from the asset profile. From the Linked queries tab: View all saved queries linked to the asset, along with a total count of such queries. Hover over a linked query to: View the total number of query runs in the last 30 days in a popover. Click the play icon to run the query in Insights. Click the open asset sidebar icon to view details about the query in the sidebar. View the total number of query runs in the last 30 days in a popover. Click the play icon to run the query in Insights. Click the open asset sidebar icon to view details about the query in the sidebar. Click the 3-dot icon to view any additional linked queries. If you do not have access to query data in Atlan, the linked queries will be displayed with a lock icon . Readme provides contextual information about the asset. It's a great place to crowdsource all the tribal knowledge and context that different users might have about the data asset. Asset profile header This section helps you perform quick actions. From the top right of the asset profile: Click the user avatars to view a list of recently visited users, total views on your asset, total number of unique visitors, and total views by user. Use the days filter to filter asset views and user activity in the last 7, 30, and 90 days. This feature is turned on by default - admins can turn off user activity . Use the days filter to filter asset views and user activity in the last 7, 30, and 90 days. This feature is turned on by default - admins can turn off user activity . Click the star button to star your asset and bookmark it for easy access. Expand the Query dropdown to view sample data or query the asset in Insights. Click the clipboard icon to copy the link for your asset. Click the Slack or Teams icon to post on a Slack or Microsoft Teams channel. Click the 3-dot icon to add an announcement or a resource to your asset. Asset sidebar The sidebar to the right of the asset profile provides high-level information about the asset. Here's what you can view: Relations shows a list of all the related assets. Usage displays usage metadata for your Snowflake and Google BigQuery assets. Lineage shows the upstream sources and downstream transformations for the asset. Fact-Dim Relations displays foreign-key relationships between fact and dimension tables. Fact-dimension relationships between assets can currently only be defined and published via API. Activity serves as a changelog for the asset . Resources are links to internal or external URLs that help your team understand the asset. Queries shows all the saved queries for the asset. Requests for an asset can be filtered by their status, such as Pending , Approved , and Rejected . Properties shows the unique identification number of the asset and other essential properties. Integrations show Slack messages and Jira tickets pertaining to the asset. Custom metadata tabs display custom metadata properties of the asset, if enabled. Components of an asset profile


A Glossary | Atlan Documentation

Using familiar terminology helps people quickly understand the data and its context. This is a crucial element of data governance since it adds business context to the data initiatives of an organization. Why do I need a glossary? In today's diverse data teams, which include people from different backgrounds and use cases, not all of them think about their data in the same way. For teams made up of data analysts, data engineers, data scientists, and decision makers, having a shared language is an important step towards ensuring better collaboration. Building a glossary allows your team to define the metrics, columns, and assets with the same meaning for everyone. Highlights of the Atlan glossary Here's how the Atlan glossary can help your organization: Supports automated metadata management through auto-glossary suggestions from the Atlan bot Anatomy of the Atlan glossary This structure allows for glossaries from multiple domains. A term is the lowest unit that is unique to each glossary. It describes the content of the data assets in a useful and precise way. It can exist independently, without belonging to any particular category or subcategory. Subcategories can be added within categories to provide more context in a glossary. Related term Similar in definition - serves the purpose of a "see also" section in a dictionary. Client is a related term for Customer . Recommended term Preferred form of usage for the current term applied. User may be preferred over Customer in the context of your organization. Interchangeable in meaning as another term. Glossary and Dictionary , or Client and Customer . Opposite in meaning to a particular term. Minimum is an antonym for the term Maximum , or Loss and Profit are antonyms. Translated term Translated version of the same term in additional languages. Cliente is the Spanish term for Customer . Valid values for Defines values that are considered appropriate for a related term. Red , Green , Blue , and Yellow are valid values for the term Color . Classifies and Classified by Country classifies United States , while United States is classified by Country . Why do I need a glossary? Highlights of the Atlan glossary Anatomy of the Atlan glossary


Add owners | Atlan Documentation

Atlan allows you to add owners for each data asset. This enriches the asset profile and helps build trust among users. Users can then quickly reach out to the owner of the asset for any questions about the data. The owner is responsible for maintaining the data asset. They are the right person to contact for questions about the data's frequency of update, progress, status, and more. Add owners to your assets To add or update owners for a data asset, follow these steps: On the Atlan homepage, click Assets in the left menu. Click on an asset to view its asset profile. To assign owners, you can either: Click the checkbox next to an individual user's name. Toggle to groups in the top right and select an entire group of users. Click the checkbox next to an individual user's name. Toggle to groups in the top right and select an entire group of users. Click Save . Your asset profile will now display the asset owners! ð You can also filter your assets by asset owners. Here are the steps: In the Filters menu on the Assets page, click Owners . Click the checkbox next to an owner name to view their owned assets. You can select No Owners in the Owners filter to view assets that currently do not have assigned owners and assign accordingly if needed. Add owners to your assets