Personas reference
DeltaVault has two content personas. Every member of your organization is assigned one of these personas by an administrator. The personas are fixed by the platform: every organization has the same two, and an administrator cannot relabel one, reorder them, remove one, create a new one, or change what each one shows. Assigning a persona to a member is the whole of the control you have.
These personas control the navigation and view a member sees. They are separate from access roles (editor and viewer), which control what a member can change.
The two personas
Section titled “The two personas”Data Steward
Section titled “Data Steward”Keeps the business vocabulary healthy: what each term means, how it is classified, and how source metadata maps onto it. This is the persona a member starts with when an administrator has not chosen one for them.
Sections visible: Business, Catalog, Models, Entities, Glossary, Map & Match, Knowledge
Data Engineer
Section titled “Data Engineer”Works the full platform surface: modeling, catalog, templates, and pipelines.
Sections visible: Projects, Catalog, Builds, Operations, Toolkit, Business, Branches, Knowledge, Models, Entities, Glossary, Map & Match
Assigning personas
Section titled “Assigning personas”Administrators assign a home persona and allowed personas to each member from the organization member grid. For instructions, see Assign personas to your members.
Switching between personas
Section titled “Switching between personas”If an administrator allows a member more than one persona, a Persona option appears in their account menu (their avatar in the top-right corner). Switching reskins the navigation but does not change permissions. For more, see Working in DeltaVault as your persona.
Related guides
Section titled “Related guides”- Assign personas to your members for administrator instructions
- Working in DeltaVault as your persona for the member experience
- Preview the app as a persona for platform administrators