Administer a facility

Manage people, courses, communication, and operational visibility while preserving facility and role boundaries.

For
Administrator
Reading time
9 min
Updated
August 16, 2026

Before you start

  • A Facility Administrator account for the intended installation.
  • Verified identity details, account role, initial-password handoff plan, and required course memberships.

You are done when

  • User management shows the saved person, fixed account role, contact details, and current security state.
  • Course management shows the saved course code, title, active or archived state, and intended instructor and student counts.

If something goes wrong

  • Use Try again or Refresh on a failed list before repeating a create action.
  • Correct field-level validation in the open panel; do not close it until the save confirmation appears.
  • Archive rather than delete when a course must be removed from active operation; Restore reverses that state.

Keep access intentional

  1. Open User management and choose Add user

    Enter first name, last name, username, email, optional birth date, Account role, initial password, and confirmation. Choose Create user only after verifying the identity and role.

  2. Use Edit user for profile changes

    The role is fixed after creation. Save changes for profile fields; use Set new password only after its separate confirmation because outstanding sign-in codes are invalidated.

  3. Open Course management and choose Add course

    Enter the course code and title, then use the instructor and student member pickers to add only the intended people. Choose Create course and verify the resulting counts.

  4. Use archive and restore deliberately

    Archive removes the course from active editing without deleting membership history. Confirm the status badge; use Restore when the course should return to operation.

Use operational insight responsibly

  • Treat analytics as facility-scoped operational evidence, not as a substitute for academic judgment.
  • Use factual counts, events, and status timelines to investigate an issue.
  • Limit exported or shared information to the people who need it for the stated task.

Continue with