The admin console
Where a staff admin starts: cohorts, grading queues and the gatekeeping engine, in one landing.
- One landing for the three jobs a staff admin actually does each day
- Every tile is capability-gated, so you only see what your role can act on
- Tenant work lives under the organization portal; this console stays about the programme
The staff admin landing
Admin is where a staff admin starts. It covers three jobs:
- Cohorts — who is grouped with whom, and what they are working through.
- Grading — the review queues for submitted work.
- Gatekeeping — the engine that decides who advances, and when.
What it is not
Tenant administration — members, teams, invitations, domains, settings — lives in the organization portal. Cross-tenant work lives in the platform console and is reachable only by operators. Keeping the three apart is why each one stays readable.
Gated tiles
Sections are shown by role. If a colleague sees something you do not, that is the role difference rather than a fault.
Frequently asked
What is the difference between this and the organization portal?
The admin console runs the teaching programme — cohorts, grading, gatekeeping. The organization portal runs the tenant — people, teams, invitations, domains, settings.
Why can I not see a section a colleague can?
Sections are gated by role. The console shows what your role can act on rather than showing a tile that refuses you when you click it.
Where do platform-wide consoles live?
Under the platform console, and only for operators. Nothing cross-tenant is reachable from here.
Related guides
Add admin employees with granular roles and fine-tune permissions.
ReadCreate cohorts, review applicants and enroll learners — with seat quotas enforced automatically.
ReadWhat lands in each review queue, and what happens when you action it.
Read