Skip to main content

Members and roles

Every member of a workspace holds one or more of six roles. A member with several roles can do everything any of them allows. Roles are checked on every request, so a change takes effect immediately - nothing waits for a token to expire.

The six roles​

CapabilityOwnerAdminCreatorPresenterAnalystViewer
See activitiesYesYesYesYesYesYes
Read resultsYesYesYesYesYesYes
Build and edit activitiesYesYesYes---
Publish activitiesYesYesYes---
Run and present sessionsYesYesYesYes--
Moderate Q&A and brainstormsYesYesYesYes--
Download responsesYesYesYes-Yes-
Delete a session or erase a participantYesYesYes---
Connected systems (integrations)YesYes----
Data retention and workspace exportYesYes----
Single sign-on, SAML, SCIMYes-----
Audit logYes-----
API keys and webhooksYes-----
Delete the workspaceYes-----

In short:

  • Owner - everything.
  • Admin - everything except the workspace-level controls in the last five rows.
  • Creator - builds, publishes and runs activities, and reads and exports their results.
  • Presenter - runs sessions and moderates them, and reads results; cannot edit activities. In an activity they see the Run and Results tabs, not Build and Settings. The default for instructors launched from an integrated platform.
  • Analyst - reads and exports results.
  • Viewer - reads activities and results.

"Read results" and "download responses" are separate on purpose: reading results in the console and taking a copy out of the building are different acts.

How roles are assigned​

  • The person who creates a workspace is its owner.
  • Single sign-on gives new members one configured role: creator, presenter, analyst or viewer. It never changes the role of someone who is already a member.
  • SCIM gives a default role, or a role mapped from the person's directory groups, and moves it when their groups change. It cannot grant owner or admin, and it never demotes an existing owner or admin.
  • Integration launches give instructors the role the integration is configured with (presenter by default), and never change an existing member's role.

No identity provider or directory can create an owner or admin. An integration's instructor role is whatever its configuration names, so treat that setting with the same care.

Suspension​

A member suspended by SCIM loses every capability in the workspace at once and no longer sees it, but their account, their other workspaces, and the activities, sessions and audit records they created all remain. Suspension is how a departure is recorded without destroying the history that makes it auditable.

Leaving​

Members leave a workspace when their account is deleted, or when the workspace is deleted. See Data retention, deletion and export. An account cannot be deleted while it is the only active owner of a workspace that has other members; the workspace has to be deleted first, or have another owner.