Roles
Your workspace has two roles:| Role | What they can do |
|---|---|
| Admin | Everything a member can, plus curate Mappings (approve, reject, remap, create, and bulk-approve) and manage members’ roles. |
| Member | View everything — Sources, the Catalogue, concepts and canonical entities, and the mapping queue — but not change it. Members have view-only access. |
Roles govern what someone can change in the context layer — the shape of the
governed data your AI tools read. They don’t change what data your connected tools can
query over MCP; that’s gated by your integrations.
Manage members
Open Governance in the sidebar to see your members, their email, and their role.Find the member
Each row shows a person’s name, email, and current role. Your own row is marked
You.
A workspace always needs at least one admin. If you’re the only admin, make someone
else an admin before stepping down from the role.