The Team & Permissions area lets authorized workspace users invite members, assign roles, update member access, and remove eligible team members. Team access is governed by both permissions and the subscription plan.
The number of team members a workspace can have is controlled by the plan resource limit named team_members. A workspace can also have a specific limit override.
If the team limit is reached, review the live Plan & Billing information before attempting to add another user.
The invite workflow accepts a name, email address, role, and password. Source validation includes:
After creation, PROS reports: Team member invited. They can now sign in with their password.
| Role | Default Operational Scope |
| Owner | Full owner-level workspace access represented by the default permission map. |
| Admin | QR create/edit/delete, Short Link create/edit, Analytics view/export, team management. |
| Editor | QR create/edit, Short Link create/edit, Analytics view. |
| Viewer | Analytics view. |
Important: Actual visible actions are also affected by route-level permissions, plan limits, and specific controller restrictions.
The Owner is the protected workspace owner role. The Settings controller does not allow the Owner role to be changed through normal team-member editing and does not allow the Owner to be removed through the team removal workflow.
The default Admin permission map includes QR creation/editing/deletion, Short Link creation/editing, Analytics viewing/export, and team management. Use Admin only for trusted users who need broad operational control.
The default Editor permission map includes QR create/edit, Short Link create/edit, and Analytics view. Certain destructive operations are further restricted; for example, Bio Page and Landing Page deletion explicitly block editor-role users in the current controllers.
The default Viewer role is designed for read-oriented Analytics access. A Viewer should not be expected to create or manage campaign assets.
Authorized users can update an eligible member role to Admin, Editor, or Viewer and can optionally set a new password. The optional replacement password must be between 8 and 100 characters.
Use the remove action only when a member should no longer have workspace access. The Owner cannot be removed using this workflow.
Caution: Removing access can affect a person who is actively working in the workspace. Confirm the correct member before performing a destructive team action.
The Sidebar is permission-aware. A team member may see fewer navigation items than the Owner or Admin.
| Navigation Area | Relevant Permission |
| QR Codes | qr.create or qr.edit |
| Short Links | link.create or link.edit |
| Bio Pages | bio.manage |
| Landing Pages | landing.manage |
| Analytics | analytics.view |
| Settings | team.manage or billing.manage in Sidebar visibility logic |
A member can have permission to perform an action while the workspace is still blocked by a plan limit. For example, an Editor might be allowed to create a QR Code, but creation can still be blocked if the workspace has reached its QR allowance.