Backstage users can be members of one or more organizations.
A member of an organization always has a role within that organization. This organization role determines what rights (accesses or actions) they can perform within the organization.
As a member of an organization, the Backstage user will also be a member of one or several workspaces, and/or one or several content hubs.
In each of those workspaces or content hubs, that same Backstage user will also have a determined role within the workspace and/or content hub.
Please see the tables below that explain the different possible organization, workspace, and content hub roles.
More information is available on how to manage roles in an organization or in a workspace.
Organization roles
As a Backstage user, you are part of one or several organizations. Your role can be either Admin, Member, Organizer or Guest of the organization.
A special role, Entitlement manager, also allows users to allocate seats and advanced modules to your organization's workspaces and to download seat usage reports.
To note, Developer API access (enabled at the organization level) is needed for organization members to access, connect, and configure the integrations modules on an organization’s workspace(s). Organization admins by default have Developer API access enabled for that organization. Organization admins can also enable Developer API access for people who have an “Organizer” role within the organization. More information on managing roles within an orgnanization. Workspace roles are not taken into consideration when it comes to having Developer API access.
Organizational roles within workspaces
The following table summarizes the rights of each organization role, within the organization:
Admin | Organizer | Member | Guest | Entitlement manager | |
---|---|---|---|---|---|
View organization details | ✓ | ✓ | ✓ | ✘ | - |
Edit organization details | ✓ | ✘ | ✘ | ✘ | - |
View organization members | ✓ | ✓ | ✓ | ✘ | - |
Add and promote organization members | ✓ | ✘ | ✘ | ✘ | - |
View workspace list (in "Manage organization" tab) | ✓ | ✓ | ✘ | ✘ | - |
Create a new workspace | ✓ | ✓ | ✓(only test workspaces) | ✘ | - |
Add a member to a workspace (themselves or someone else) | See the section below called Organization and workspace roles needed to add a user to a workspace for all details on doing this. | ||||
Promote test/pre-production workspaces to production | ✓ | ✓ | ✘ | ✘ | - |
Create a template from a workspace | ✓ | ✓ | ✘ | ✘ | - |
View legal documents | ✓ | ✓ | ✓ |
✘ Can see them in a workspace or content hub |
- |
Edit legal documents | ✓ | ✓ | ✘ | ✘ | - |
View entitlements | ✘ | ✘ | ✘ | ✘ | ✓ |
Manage entitlements | ✘ | ✘ | ✘ | ✘ | ✓ |
Developer API access | ✓ |
✘ (unless enabled by org admin) |
✘ | ✘ | - |
Organization and workspace/content hub roles needed to add a user to a workspace/content hub
Note: When reading this table, please note that where we say “workspace”, the same rules apply to content hubs. Remember that users can be added to a workspace/content hub via the organization settings, or via the workspace/content hub settings.
Your role in the organization | Your role in the workspace that is connected to the organization | Can you add this person to the workspace, IF the person you are trying to add… | ||
Exists in the organization connected to the workspace? | Does not exist in any organization at all? | Does not exist in the organization connected to the workspace, but does exist in another organization. | ||
Admin | Manager |
Via the workspace settings: ✓ Via the organization settings: ✓ |
Via the workspace settings: ✓ Via the organization settings: ✓* |
Via the workspace settings: ✘ Via the organization settings: ✓* |
Admin | Editor / Viewer |
Via the workspace settings: ✘ Via the organization settings: ✓ |
Via the workspace settings: ✘ Via the organization settings: ✓* |
Via the workspace settings: ✘ Via the organization settings: ✓* |
Organizer | Manager |
Via the workspace settings: ✓ Via the organization settings: ✓ |
Via the workspace settings: ✘ Via the organization settings: ✘ |
Via the workspace settings: ✘ Via the organization settings: ✘ |
Member / Guest / Entitlement manager | Manager |
Via the workspace settings: ✓ Via the organization settings: ✘ |
Via the workspace settings: ✘ Via the organization settings: ✘ |
Via the workspace settings: ✘ Via the organization settings: ✘ |
Organizer / Member / Guest / Entitlement manager |
Editor / Viewer |
Via the workspace settings: ✘ Via the organization settings: ✓ |
Via the workspace settings: ✘ Via the organization settings: ✘ |
Via the workspace settings: ✘ Via the organization settings: ✘ |
* This is done by first adding the person to the organization, and then adding them to the workspace.
Organizational roles within content hubs
The following table summarizes the rights of each organizational role, in content hubs
Admin | Organizer | Member | Guest | Entitlement manager | |
---|---|---|---|---|---|
View the content hub tab and access content hub functionality on Backstage |
✓ | ✓ | ✓ | ✓ | - |
View the list of content hubs (only those that they are added to as a team member of) |
✓ | ✓ | ✓ | ✓ | - |
Access a content hub via the list (only those that they are added to as a team member of) |
✓ | ✓ | ✓ | ✓ | - |
Create a new content hub |
✓ | ✓ | ✘ | ✘ | - |
View content hub list (in "Manage organization" tab) |
✓ | ✓ | ✘ | ✘ | - |
Workspace roles
As a Backstage user, you can be a member of one or several workspaces, each with a different role: Manager, Editor, or Viewer.
The following table summarizes the rights of each role within the workspace:
Manager | Editor | Viewer | |
---|---|---|---|
Add/edit/remove a team member/role | See the section below called Organization and workspace roles needed to add a user to a workspace for all details on this. | ||
Install/Uninstall modules | ✓ | ✘ | ✘ |
Edit workspace settings | ✓ | ✘ | ✘ |
Update workspace production status | ✓ | ✘ | ✘ |
Send emails | ✓ | ✘ | ✘ |
Edit emails | ✓ | ✓ | ✘* |
Send notifications | ✓ | ✓ | ✘* |
Add/Import content | ✓ | ✓ | ✘* |
Start live streams | ✓ | ✓ | ✘* |
Delete "PAST" live sessions | ✓ | ✓ | ✘ |
View and export content | ✓ | ✓ | ✓ |
View analytics | ✓ | ✓ | ✓ |
Generate session check-in/out PIN codes | ✓ | ✓ | ✘ |
Developer API access | Managed at the organization role level (see above) |
*(unless they are members of the organization that the workspace belongs to)
Content hub roles
As a Backstage user, you can be a member of one or several content hubs, each with a different role: Manager, Editor, or Viewer.
The following table summarizes the rights of each role within the content hub:
Manager | Editor | Viewer | |
---|---|---|---|
View team members |
✓ | ✓ | ✘ |
Add/edit/remove a team member/role |
See the section below called Organization and workspace roles needed to add a user to a workspace for all details on this. | ||
View content hub general settings (content hub name, privacy policies, container app, production status) |
✓ | ✓ | ✓ |
Edit content hub general settings (content hub name, privacy policies, container app, production status) |
✓ | ✘ | ✘ |
View content hub connected event settings |
✓ | ✓ | ✓ |
Edit content hub connected event settings |
✓ | ✓ | ✘ |
Update content hub production status |
✓ | ✘ | ✘ |
View content in the hub |
✓ | ✓ | ✓ |
Add/edit/delete content |
✓ | ✓ | ✘ |
Download content |
✓ | ✓ | ✘ |
Download analytics |
✓ | ✘ | ✘ |
Manage users (view users, add users, cancel users) |
✓ | ✓ | ✘ |
Send emails to users |
✓ | ✓ | ✘ |
View/edit design |
✓ | ✓ | ✘ |
Notes: When the Backstage user, with an admin or organizer role within their organization, creates a new content hub, they are automatically set as a manager in the content hub. As manager they can add other team members to the content hub.
Comments
0 comments
Please sign in to leave a comment.