Teams, roles and workspace access
Invite collaborators, assign a narrow role and switch between workspaces without sharing credentials.
Last reviewed 24 July 2026Teams should collaborate through individual accounts, not a shared password. OrbitPage permissions are attached to the workspace so one person can participate in more than one page.
An account identifies a person; a workspace owns a page.
A user may own a personal workspace, collaborate on other workspaces, or use an account only for collaboration. The account switcher changes the workspace being edited without changing the signed-in identity.
Public content, storage, billing and plan limits remain attached to the selected workspace.
Give each collaborator the access their job requires.
Owners control the workspace. Admins can manage the page and collaborators. Profile editors focus on page content. Analytics viewers can inspect reports without editing the public page.
Available seats and role capabilities vary by managed plan. Review the current plan before inviting a team.
Invite a verified address and let the recipient use their own sign-in.
Invitations bind the intended email to a workspace role. The recipient completes account access and then sees the workspace in the account selector.
Remove access when the working relationship ends. Do not recycle another person's account for a replacement collaborator.
Partner workspaces can retain a visible support administrator.
Selected partner onboarding can include the OrbitPage support account as an administrator so the owner can ask for hands-on help. That access is visible in the team list and should be explained during onboarding.
Regular customer workspaces remain controlled by their owner and invited team.
