Platform console & support access

Find and manage an organisation

Company SSO credentials, integration secrets and membership changes remain in Company settings using an authorised membership. The platform detail page does not reveal secrets or silently grant a company role.

1. Open Platform console → Organisations. Search across all company names and slugs; results are paginated with up to 25 companies per page.
2. The default directory includes Companies and Showcases. Use Test workspaces or All workspaces to inspect technical fixtures. Showcase names and records are fictional; classification never deletes data or changes permissions.
3. Select a company name or Manage. Overview shows people, course, enrolment and completion counts. Company profile edits its name, timezone, logo, accent, support contacts and directory classification.
4. Workspace policies controls slug and custom-domain self-service. AI governance controls allowed providers and limits. People & support provides member profiles, contact editing, learning history and bounded support sessions; Activity shows the latest 100 company administration events.
5. Save changes with a recent administrator sign-in. A revision conflict prevents overwriting another change; reload and review before resubmitting. Your active workspace and identity do not change.

Platform operators and company administrators

Platform console is the operator area for organisations, address policies and AI governance. An active owner membership must also be explicitly allowlisted by the installation operator. Company administrator access alone does not grant cross-company access.

Use the workspace switcher to enter companies where you have an owner or administrator membership. Manage people and learning there with your own identity.

Member profiles and acting sessions

Acting allows only native course saving/publishing, assignments, progress and resource/course bookmarks or resource management, subject to the target's permissions. Committed changes and administrator attribution are atomic. Messaging, uploads, SCORM writes, company settings, credentials, roles and all other writes remain blocked.

Suspended memberships remain editable but cannot be support-session targets. Other platform operators cannot be targets. Expired or revoked support access shows a recovery screen. No password, MFA secret or identity-provider account is exposed.

1. Open a member profile to inspect contact details, roles, teams, identity-provider issuers and paginated learning history. Audit history shows the latest 30 profile changes and committed support actions.
2. Choose Edit profile, provide a reason and save with recent authentication. A revision conflict preserves your edits; reload current details before retrying. Contact email does not change identity-provider sign-in email or credentials.
3. If the installation enables SUPPORT_ACT_AS_ENABLED, choose Act as user, enter a reason and confirm that changes affect real learning records. The banner identifies the person and provides Return to administrator. Access expires after 15 minutes.

View as user

Starting and ending a support view records the original operator and target in the operator company audit history; the start also records the reason. The target’s password and sessions are never changed or exposed.

All state-changing browser requests are blocked during support view, including uploads and progress writes. Suspension or permission changes invalidate the view; the write restriction stays until it is explicitly ended. Expired or revoked views must be exited before continuing. This is support inspection, not unrestricted writable impersonation.

1. Open Platform console, open a company, then choose People & support → Browse people & profiles. Search the paginated membership list and select Open profile.
2. Choose a person and enter a meaningful support reason. A recent sign-in is required. Other platform operators cannot be viewed as.
3. Start the read-only view. The banner identifies the person and company and provides Return to administrator. The view lasts up to 15 minutes.
4. Return to administrator before changing settings or assignments. An explicitly enabled Act as user session can perform reviewed native learning actions with confirmation; these affect real records.

Testing data

An installation operator can provision additive fictional QA accounts and learning data through the guarded testing utility. This is optional and never runs during customer installation. Account passwords belong in the private operator registry, never in this public guide. Existing identities, passwords and learning history are preserved.