Platform

Roles & Access

There are three roles inside an organization — Member, Instructor, and Admin — plus a narrower super admin flag layered on top of Admin, and a separate master admin who works across every organization.

The three roles

Role	Can	Cannot
Member	Join courses published to them, work through modules, answer questions, download results and certificates, bookmark courses.	See any authoring, invite, reporting, or people screen.
Instructor	Create and manage their own courses, upload content, write questions, invite people into their courses, grade written answers.	See other instructors' courses, invite admins or instructors, or open Reporting.
Admin	Everything, organization-wide: every course regardless of who authored it, invites for any role, People, Reporting, and Settings.	See other organizations, or (without the super admin flag) Backup, Roles, Audit Log, and Removal.

An instructor's view is deliberately narrow

On the Courses page an instructor sees only the courses they own or collaborate on. An admin sees the whole organization’s courses, grouped by instructor.

How each role gets created

The path into an organization differs by role, and this is enforced on the server, not just hidden in the interface:

The first admin is created together with the organization itself, by whoever registers it. See Organizations.
Instructors and further admins can only be created by an existing admin sending an invite. There is no other route.
Members have three routes: self-registration from the login page, an admin invite, or accepting an instructor’s invite to a specific course (which creates a member account if they don’t have one).

Super admin

Super admin is not a fourth role — it’s a switch on an existing admin. Every admin has full access to people, content, and reporting; only admins with this flag additionally see four tabs under Settings:

Backup — whether this organization is included in the regular backup runs.
Roles — the switch itself, listing every admin.
Audit Log — this organization’s recorded actions.
Removal — requesting that the organization be closed.

Only a super admin can grant or revoke the flag, on Settings › Roles. See Settings.

Master admin

Master admin is the Intermediate Data Systems team, and it lives outside the ordinary role system: it requires both that the workspace itself is the master workspace and that the account is a super admin. A master admin manages every organization’s plan and status and authors the shared platform courses.

No customer organization can ever have a master admin, and the master workspace has no ordinary Courses page of its own. See Master Workspace.

Changing someone's role

An admin opens Invite Team Members, finds the person in the list below the pending invites, and clicks View. Role, phone number, and activation all live in that profile panel.

Two guardrails

An admin cannot change their own role, and cannot deactivate their own account — both are blocked in the interface and refused by the server. This is what stops an organization from accidentally locking out its last admin. Full detail on People & Roles.