Reference

Persona cells: scope × intent

The cells that decide your menu: which intent is populated in each scope, which key gets you in, and how many keys its package holds.

For: Platform administrator, Builder, Account administrator, Tenant administrator, Operator, Auditor, Member

What a cell is

A persona is the intersection of a scope and an intent. Of 3 scopes and 5 intents, 12 cells are populated. A person's menu is made of the cells they hold in the scope they are in: a cell appears in the menu when you hold its entry key and (for cells with actions) at least one action key.

Populated cells

ScopeIntentWhat forEntry keyPackage
Platformbuild (Studios in the menu)Building capabilities and solutionscapability.read14 keys
Platformgovern (Governance in the menu)Policy floors, roles, platform configurationrole.read13 keys
Platformoperate (Operations in the menu)Runtime, health and incidentsoperations.read8 keys
Platformaudit (Assurance in the menu)Platform auditaudit.read18 keys
Accountbuild (Studios in the menu)Publishing to the account's own tenantscapability.read14 keys
Accountgovern (Governance in the menu)Tenant lifecycle, people, rolesrole.read11 keys
Accountaudit (Assurance in the menu)Account audit—not defined yet
Tenantbuild (Studios in the menu)Installing applications from the catalog—not defined yet
Tenantgovern (Governance in the menu)Tenant configuration, members, teamscapability.read11 keys
Tenantoperate (Operations in the menu)Workspace operations and data—not defined yet
Tenantuse (Work in the menu)Business userrecord.read4 keys
Tenantaudit (Assurance in the menu)Tenant auditaudit.read18 keys

Tip A cell whose package is “not defined yet” exists in the product but does not declare any permission package yet; so it doesn't appear in anyone's menu.

Empty cells

ScopeIntentWhy it is empty
PlatformuseNobody uses an application in the platform scope.
AccountoperateAn account governs; it doesn't run workloads.
AccountuseThe same reason as in the platform scope.