PROS supports a shared workspace model in which different users can have different levels of access. The default role keys are Owner, Admin, Editor, and Viewer.
| Permission | Owner | Admin | Editor | Viewer |
| Create QR Codes | Yes | Yes | Yes | No |
| Edit QR Codes | Yes | Yes | Yes | No |
| Delete QR Codes | Yes | Yes | No | No |
| Create Short Links | Yes | Yes | Yes | No |
| Edit Short Links | Yes | Yes | Yes | No |
| View Analytics | Yes | Yes | Yes | Yes |
| Export Analytics | Yes | Yes | No | No |
| Manage Team | Yes | Yes | No | No |
The Owner is the primary workspace role created during standard registration or first-time Google signup. The owner has the broad default permission set and cannot be removed or have the owner role changed through normal tenant Team settings.
Admin has the same default permission list shown for Owner in the current role mapping, including QR management, Short Link management, Analytics viewing/export, and team management.
Owner is still special: Even though Owner and Admin share the same mapped permissions, the application specifically protects the Owner record from normal role changes and removal.
Editor can create and edit QR Codes and Short Links and can view Analytics. Editors do not receive the default QR delete, Analytics export, or team-management permissions.
The Bio Page and Landing Page delete controllers also explicitly block a user whose role key is editor from deleting those pages.
Viewer receives Analytics viewing permission only in the current role mapping. This role is appropriate when someone needs performance visibility without asset-management authority.
A role does not bypass the workspace subscription. The Team invitation route checks both team-management authorization and the plan limit for team members.
| User need | Recommended starting role |
| Full workspace ownership | Owner |
| Day-to-day management and team administration | Admin |
| Create/edit campaign assets without administrative authority | Editor |
| Read-only performance review | Viewer |
Least privilege: Give each team member only the access required for their work. This reduces accidental deletion and unauthorized administrative changes.