Skip to content
Open the app

Roles and access

First Six keeps access deliberately simple: a small set of roles, plus a scope that limits which students a person sees. Together they make sure staff have exactly the reach their job needs — no more.

The three roles

RoleWhat it's forCan do
Institution adminRunning the showFull access: settings, the whole team, the audit trail, every cohort
Content editorBuilding the student experienceAuthors briefings, resources, and announcements for their scope
Support responderLooking after studentsWorks the inbox and the cohort pulse for their scope

Most people are a responder or an editor. Admins are few by design.

Scope: who sees which students

On top of the role, each staff member has a scope — the slice of students they work with, set by course, degree, campus, or cohort. A responder scoped to one campus sees that campus's requests and pulse, not the whole institution.

Admins see everything; everyone else sees their scope

Institution admins have full reach across cohorts. Editors and responders are bounded by their scope, so the inbox, the cohort browser, and insights each show only the students they're responsible for.

Managing the team

From the team area, an admin can:

  1. Add staff and set their role

    Bring a colleague in as an admin, editor, or responder.

  2. Set their scope

    Point them at the courses, degrees, campuses, or cohorts they cover.

  3. Reassign work when someone's away

    When a staff member goes on leave, their open help requests can be reassigned to others, with a handoff note that travels with each ticket so context isn't lost.

Common questions

Can I make a custom role?

Not currently — the three roles cover the real jobs (run it, build it, respond to it), and scope handles the "which students" question. This keeps access easy to reason about and audit.

Who can see the audit log?

Institution admins. Every consequential action is recorded there — see the activity log.

What happens to a leaver's open tickets?

Reassign them before (or as) they leave, with handoff notes, so nothing falls through. The reassignment itself is recorded in the audit trail.

Was this helpful?
Need more help?

The fastest answer is usually one question away.

Edit this page on GitHub