Administer

Administration in emergent is about the Organization: the administrative context that scopes who can do what. You do this work in the admin console — a single, scope-aware dashboard. When you sign in, the console shows the scope your account carries (one Organization, several, or the whole platform) and lays out the tools you are entitled to as a stack of panels on that one page.

As an administrator you set the stage: you decide who takes part, under what role, and how the Organization presents itself when it signs credentials. You rarely author learning content yourself — that is teaching work — but nothing runs until the people are in place.

What the admin console lets you do

The console is task-focused rather than sprawling. These guides cover the core loop, in the order you would usually work through it:

1. Sign in and choose your scope — reach the console, confirm your admin role, and pick the Organization you are operating in.
2. Set up an Organization’s issuer identity — the image and descriptive details embedded in the credentials the Organization signs.
3. Invite people — provision the teachers, assistants, and other staff and administrators who run the Organization’s Offerings.
4. Resolve held identities — settle imported or self-signed-up people the platform could not match with certainty (platform administrators).

Two things worth knowing first

• Identity is durable. Provisioning a person creates a Person — a durable identity whose learning history follows them, not the account they happen to sign in with. Roles are granted to a Person; the Person is not the account.
• Scope decides what you see. An organization administrator sees the tools for the Organization they administer. A platform administrator sees those plus platform-wide tools such as identity review. If a panel described in these guides is not on your dashboard, your account does not carry the scope for it.