17 docs tagged with "personas"

Add or remove users and groups from a persona in Atlan to control who inherits its access policies and view.

Configure AI asset access in personas: control who can view, edit, or manage AI models, model versions, applications, and governance properties.

Block users from querying or previewing data in Atlan at different levels: workspace-wide, by connection, by specific asset, or by tag.

Configure glossary access in personas: control who can create, update, and delete terms and categories, link terms to assets, and manage tags and custom metadata within a glossary.

Copy a policy from one persona to another in Atlan to reuse access configurations without rebuilding them from scratch.

Create a dynamic metadata policy in Atlan to grant a persona access across every connection with a single metadata rule, instead of one policy per connection.

Customize the catalog view a team gets in Atlan: set the default landing page, which asset types, sidebar tabs, and discovery filters appear, and what custom metadata is visible, per persona.

Configure data access in personas and purposes: control who can query and preview data, deny selected permissions with rules that override other grants, and apply column-level masking such as hashing, redaction, or showing only the last four characters.

How to pick the simplest access-control mechanism, sequence a persona rollout, map SSO groups, and govern sensitive data without over-engineering.

Configure domain access in personas: control who can read, update, and manage data domains, subdomains, and products, including their custom metadata.

Configure metadata access in personas: control who can view, edit, or restrict metadata, tags, terms, and governance properties, including deny rules that override grants from other policies.

Control what users can see and do in Atlan once they have signed in. Scope access by team with personas, by data sensitivity with purposes, by connection, or hide assets entirely. Learn which control to use and how role, persona, and purpose combine.

Personas in Atlan scope what a team sees and can do by bundling users and groups with access policies and a custom catalog view.

Monitor governance metrics in the reporting center dashboard. Track query access for personas and purposes, view tag propagation across assets, and manage governance requests from a centralized view.

Create a persona in Atlan to scope what a team sees and can do: define access policies, add members, and set the UI experience for a team or function.

The lock icon in Atlan indicates when users have limited access to an asset. This page explains what the icon means and how roles, connection admins, and access policies affect it.

Impersonate any non-admin user in Atlan to validate personas, Labs toggles, and access controls from their point of view, and to troubleshoot access issues they report.