Skip to main content

Onboarding and security

This guide distinguishes the current open Administration preview from the separate central identity-service implementation. It prevents browser-local sample account controls from being mistaken for production authentication, secure invitations or access enforcement.

Open Administration in the CEDA preview.

1. Understand the current Onboarding centre​

The Onboarding centre includes three counts:

CountWhat it represents
PendingInvitation records with Prepared status
CompletedInvitation records with Completed status
Delegated onboardersUser profiles whose May onboard other people flag is selected

The Invitations prepared card near the top of Administration is calculated differently: it counts user profiles marked with Invitation prepared status. It does not count the invitation records in the centre. The numbers can therefore differ.

In the current open preview, adding a preview account does not create an invitation record. An empty invitation list is expected, and the centre explains that the local preview account action does not generate a link.

The open preview does not create a secure invitation, verify the recipient's identity or send email. The user profile created by Add preview account has no sign-in credential or central identity record.

The presence of Generate link, Revoke invitation or Password update link controls in a separate identity-service flow does not make the current open directory a secure invitation system. Do not copy, share or rely on prototype links for real CEDA users.

Opening an email-app action only prepares a message in the user's email application. It does not send the message automatically.

3. Understand the separate central identity-service mode​

The repository contains a gated identity implementation. It is separate from the current open preview and is used only when the deployment explicitly enables access enforcement and provides the required identity infrastructure.

The central mode includes:

  • a one-time initial platform-administrator bootstrap using a deployment secret;
  • administrator sign-in and sign-out;
  • a D1-backed central user directory and invitation register;
  • server-validated administrator actions for invitation, role/workspace updates, account status, invitation revocation and password-update links;
  • invitation onboarding with progress, password setup and completion;
  • an identity session using a secure, HTTP-only cookie; and
  • identity audit records written to the central database.

The initial bootstrap is intended to create the first platform administrator only once. Subsequent account management requires an authenticated platform administrator.

The central API stores invitation-token hashes rather than the raw token. Its invitation records have an expiry and are checked for pending status before the token can be used. The onboarding screen verifies the invitation before displaying the invitee details.

This is an implementation path in the repository. Its presence does not mean the currently open CEDA preview has been switched to that mode or that CEDA has approved production use.

4. Understand the gated sign-in and bootstrap screens​

When the central identity mode is enabled:

  1. Administration checks whether an initial platform administrator needs to be created.
  2. If no platform administrator exists, the one-time bootstrap screen requests the administrator name, email, password and deployment bootstrap secret.
  3. Otherwise, the page presents Administrator sign in.
  4. After sign-in, the authenticated administrator can view the central directory.
  5. Sign out ends the administrator session.

The identity API requires the D1 database binding. If the database is unavailable or not configured, the central sign-in path reports that the identity service is not connected. Do not treat a client-side flag or the presence of a sign-in form as proof that the full production identity environment is configured.

5. Understand the central onboarding sequence​

When a central invitation is created by an authorised administrator, the flow is:

  1. The administrator enters the user's name, email, role and workspace scope.
  2. The identity service creates the account in an invited state and creates a single-use invitation record.
  3. The administrator copies the generated onboarding link and shares it with the invitee. The portal does not send the email automatically.
  4. The invitee opens the link and the onboarding page verifies it with the identity service.
  5. The invitee confirms their details and reviews the assigned role and workspaces.
  6. The invitee reads the workspace orientation and prototype-safety instructions.
  7. The invitee creates a password that meets the minimum length and character requirements shown by the form.
  8. The invitee confirms readiness and completes onboarding.
  9. The central directory records the completed onboarding state and activates the assigned role.

A delegated applicant onboarder, where separately authorised, may prepare invitations for applicant team members only. Staff, evaluators, adjudicators and privileged roles remain the responsibility of a platform administrator.

6. Understand password and session controls​

The central identity implementation requires passwords of at least 12 characters, including uppercase, lowercase and a number. The API hashes passwords using PBKDF2 with SHA-256 and a per-password salt. It does not store the submitted password in plain text.

The sign-in session is represented by a secure, HTTP-only cookie and an expiry-controlled central session record. Password-update links use a separate invitation purpose and are checked for validity and expiry by the identity service.

These details describe the current implementation. CEDA must still approve password policy, MFA, session lifetime, recovery controls, identity hosting and incident-response procedures for production.

7. Production access requires multiple layers​

LayerRequired control
AuthenticationVerify the person through the approved identity service
Workspace accessConfirm the person may open the requested workspace
Record-level accessCheck the relationship to the applicant, case, assignment or panel record
Action permissionsAuthorise sensitive actions such as eligibility decisions, assignment, rubric publication and decision release
Document accessAuthorise every file view and download against the record and role
AuditRecord sensitive access and changes in a durable, protected audit register

Client-side navigation, role dropdowns and hidden buttons are not sufficient security. Protected APIs and document operations must independently validate the session, role, assignment and record scope on the server.

8. Approval checklist before enabling central identity​

Before enabling central identity and access enforcement for CEDA, obtain approval for:

  • official role titles, role approvers and delegated authority;
  • workspace, record-level and document-level permissions;
  • segregation of duties and conflict-of-interest restrictions;
  • applicant-team delegation boundaries;
  • identity hosting, data residency and database administration;
  • MFA, password and session policies;
  • invitation, revocation, password recovery and account suspension procedures;
  • audit ownership, retention and monitoring; and
  • incident response and account support responsibilities.

The preview D1 database must not hold real applicant, staff or operational identity records until CEDA has approved the hosting location and data-protection arrangements.

This guide documents the implementation boundary; it does not enable authentication or permissions. Keep the open-preview access behaviour while the prototype remains under review.