Roles and Permissions

Role matrix

Instructor roles

"Instructor" covers three granted roles: course manager (every session of that course), session instructor, and session teaching assistant. Teaching assistants see the aggregates and progress of their assigned sessions but not speaker notes.

Session course binding and permissions

A session can be bound to one course or not bound (an event code). Course managers are authorized per course, so the bound course decides which course managers can manage the session: once bound, every manager of that course can manage it, and rebinding or unbinding removes that from the previous course's managers. A session that is not bound gives no course manager automatic access; only the teachers assigned to it and admins can manage it. Only admins can change this setting, a change shows its impact first, and it is written to the audit log.

Credential administrator

Credential administrator is a separate granted role, not automatically included with the instructor or admin roles. A credential administrator can review a learner's submitted work and issue applied-skill certificates and other certification levels, manage certification definitions, rubrics and issuance policies in the credential console, and see certification-related evidence. An instructor who also holds this role can do the same review work. Admins grant and revoke the Platform Admin, Credential Admin, Course Manager and Teacher or teaching-assistant roles in the admin people page; Credential Admin can only be granted to an existing user. Changing a credential's issuance policy needs a second person: whoever proposes the change cannot approve it with admin or credential-administrator authority (see Certification Architecture).

HR viewer

"HR viewer (feedback only)" is a read-only role granted in the organization workspace. It sees only that organization's course-feedback statistics, the platform baseline, the response rate and de-identified comments, and can download a CSV. It gives no access to the organization's other data (for example Use Cases) or to other organizations. The role is checked per organization on the server, and every read and export is audited.

Server-side authorization

Every access to protected data is checked on the server; hiding a button in the interface is never an authorization mechanism. The Teacher and Admin apps check permission before the page is even served.

Sign-in and roles

Roles are usually granted by an admin. A learner who joins a course session with a code never gains instructor or admin access by doing so. In a narrow case, a course with no manager assigned yet can be self-claimed by an eligible user (one who already holds an instructor or teaching-assistant role on one of that course’s sessions, or whose account is on the approved instructor allowlist) without an admin granting it manually.

• Account and sign-in
• Access and roles (admins)