Placio Personas
Understanding user personas is essential for understanding feature access and scope.
Admin
Scope: System-level
Context: Outside all workspaces
Access: Global control only
Use Cases: System management, platform administration
Admin exists at the system level, never inside a workspace. Admin has global control over the entire platform. Admin is separate from Workspace Owner.
Workspace Owner
Scope: Workspace-level
Context: Inside workspace (exactly ONE per workspace)
Access: Root authority inside workspace
Use Cases: Workspace configuration, staff management, full feature access
There is exactly ONE Workspace Owner per workspace. Workspace Owner has root authority within their workspace. Workspace Owner can create and manage Staff members. Workspace Owner is NOT the same as Admin.
Staff
Scope: Workspace-level (role-based)
Context: Inside workspace
Access: Created by Workspace Owner, permissions granted via roles
Use Cases: Limited feature access based on assigned roles
Staff members are created by the Workspace Owner. Staff have NO implicit permissions - all access is role-based. Staff access is always documented as role-based. Staff cannot access Admin-level features.
Customer
Scope: Public/external
Context: Outside workspace (customer-facing)
Access: Public URLs, storefront, booking links
Use Cases: Placing orders, booking sessions, accessing public services
Customers are external users, never internal. Customers access public-facing features only. Customers do NOT have access to any dashboards. Customer flows are always public-facing.