Account and team
Manage OrbitPage collaboration: invite team members, assign roles and permissions, switch workspaces and create or revoke personal automation tokens.
Team manages access to the selected workspace. Each collaborator signs in with their own account. Your plan determines whether collaborators are available and how many seats the workspace can use.
Account identity and workspace access
Each person signs in with their own account, then works within the selected workspace's membership. Account → Security manages that person's sign-in; Team manages access to the page. Use the workspace selector before inviting a collaborator or changing permissions.
Invite a collaborator
Open Team, enter the person's email and select a role. They accept the invitation with their own signed-in account. An invitation is not an active seat until accepted. Review pending invitations and revoke those you no longer need.
Choose a role
The owner controls the subscription, custom domains and workspace deletion. Roles limit which dashboard sections and actions a collaborator can use. Select Custom access to choose profile, content, theme, menu, privacy, media uploads, publication, analytics, backup export/history, backup restore, newsletter, shop, AI and member visibility separately. Restore includes backup read access; newsletter and shop include read and write access. AI edits still require the corresponding section permission. Permissions are checked again for every dashboard, REST and MCP request.
| Role | Access |
|---|---|
| Owner | All workspace actions, including billing, domains and deletion |
| Admin | Page and content editing, analytics, publication, backups and non-admin team management |
| Editor | Page/content editing and publication; no analytics, backups or team management |
| Analytics viewer | Read-only page context and analytics |
| Custom access | Only the selected sections; no billing, domains, member management or workspace deletion |
Check which page you are editing
Use the workspace selector to move between your page and workspaces shared with you. Check the page name and public address before saving, sending a campaign or changing access.
An external integration remains connected to its approved workspace. Switching the active browser workspace does not retarget an existing ChatGPT connection or personal API token.
Give an automation its own credential
Create a named, scoped token under Team → Personal API tokens. Choose only the permissions the automation needs and save the token in its secret store: the complete value is shown once.
Revoke unused or exposed credentials immediately. Tokens use your current workspace permissions; removing a member also removes their effective access.
