Skip to content

Assign personas to your members

As an organization administrator you decide which persona each member starts in and which personas they may switch between. You do this from the member grid in Settings, then Users & Teams, the same grid where members and their roles are managed.

Each member has two persona settings, shown as columns in the member grid:

  • Home persona is the persona the member starts in when they sign in. If you set nothing else, this is the only persona they have.
  • Allowed personas is the set the member may switch between using the Persona option in their account menu (their avatar in the top-right corner). The home persona is always included. A member with a single allowed persona never sees the Persona option.

Set a member’s home persona to match the work they do: a governance owner to Data Steward, a data engineer to Data Engineer. Add allowed personas when someone genuinely works across roles, for example a lead who both reviews model drafts and works on the full catalog surface.

There is no persona screen in the product to open. The personas are fixed by the platform, so there is nothing to configure and nothing to browse. Personas reference is the list: both personas, and the sections each one sees. Check it when you are deciding which home persona fits a member.

Assigning a persona does not change a member’s access

Section titled “Assigning a persona does not change a member’s access”

Persona and role are separate. Setting a member’s persona changes the view they get, never their permissions. To change what a member can edit, change their role, not their persona.