Admin#

Who this guide is for#

This guide is for users with the global Admin role. It covers everything you need from signing in to managing users, configuring models, knowledge settings, and operational visibility. Admins can also perform all Teacher tasks inside classes.

What you can do#

  • Everything a Teacher can do inside classes.

  • Change the global role of any user.

  • Send accounts to trash, restore them, and purge eligible ones.

  • Configure AI models and connections.

  • Configure global knowledge settings.

  • Review the audit log, general branding, and system status.

Getting started#

Task: sign in#

Goal#

Access the product with your account.

Before you start#

  • You need a registered email and password.

Steps#

  1. Open the access screen.

  2. Enter your email.

  3. Enter your password.

  4. Confirm access.

Expected result#

The system takes you to the dashboard with your Admin role options.

Limits and notes#

  • v1 does not require email verification.

  • v1 has no password reset flow inside the product.

access-sign-in — Access screen with email and password fields.

Task: confirm your role has changed#

Goal#

Verify that the Admin role is now active on your account.

Before you start#

  • An Admin has already told you your role was assigned or updated.

Steps#

  1. Sign out.

  2. Sign in again with the same account.

  3. Check whether you now see the dashboard and Admin options, including the entry to Admin settings.

Expected result#

Your Admin role is active and you can access the global platform configuration.

Limits and notes#

  • Role changes do not take effect in the current session.

  • You must always sign out and sign back in.

access-role-change — Visible difference between the previous state and the state after sign-in, with Admin options active.

Class management#

Admins can perform all Teacher tasks inside classes. This section covers the most common ones. See the Teacher guide for more detail on any specific flow.

Task: create a class#

Steps#

  1. Go to the dashboard.

  2. Use the action to create a new class.

  3. Fill in at least title and description.

  4. Confirm creation.

The class is immediately active. Configuration lives inside that class’s workspace.

teacher-create-class — New class form with and .

Task: manage members#

Steps#

  1. Open Class Settings from the class workspace.

  2. Open the members table.

  3. Approve, reject, or remove as appropriate.

Admins can remove any member, including Teachers, unlike Teachers who cannot remove Admins.

teacher-manage-members — Members table with pending and approved rows, and Admin actions visible.

Task: grade from the Grades tab#

Steps#

  1. Open the correct lesson.

  2. Go to Grades.

  3. Select a student.

  4. Edit the numeric grade, exempt, and feedback per row.

  5. Publish or unpublish the necessary rows.

The numeric scale is 0 to 10. Autosave stores the draft automatically.

teacher-grades-tab — tab with a student selected and publish/unpublish actions.

Admin settings#

Task: open Admin settings and get oriented in its tabs#

Goal#

Access the global configuration panel and learn what sections are available.

Before you start#

  • You have an active Admin role.

Steps#

  1. Open Admin settings from the dashboard or global navigation.

  2. Review the available sections: User, Courses, Course, System, and Operations.

  3. Navigate to the section you need.

Expected result#

You can access any global configuration from this panel without leaving to a class workspace.

Limits and notes#

  • This panel is exclusive to Admins.

  • Teachers and Students do not have access to Admin settings.

Admin settings with System and Operations sections

Users#

Task: manage global roles#

Goal#

Change the global role of a user when necessary.

Before you start#

  • You have opened Admin settings.

Steps#

  1. Go to the Users tab.

  2. Search for the user by name or email.

  3. Change their global role as appropriate.

Expected result#

The user has their new global role saved in the platform.

Limits and notes#

  • The role change takes effect after the affected user signs out and signs back in.

  • The system blocks any action that would leave zero active Admins.

admin-users-role-change — tab with an active search and role change available.

Task: remove, restore, or purge accounts#

Goal#

Manage the active or soft-deleted state of accounts.

Before you start#

  • You have opened the Users tab.

Steps#

  1. Find the active account you want to remove, or expand the trash section to see soft-deleted accounts.

  2. Use the remove action to send an account to trash.

  3. Use restore to bring an account back from trash.

  4. Use purge only when you truly need to permanently delete an eligible account.

Expected result#

The account is in the expected state inside the users table.

Limits and notes#

  • Active and Soft-deleted are the states visible in this tab.

  • Restore is immediate.

  • Purge requires confirmation.

  • The system blocks deletion of the last Admin.

admin-users-trash — Trash section with restore and purge actions visible.

Models#

Task: configure models#

Goal#

Select the active global model and adjust minimal inference settings.

Before you start#

  • You have opened Admin settings.

Steps#

  1. Go to Operations → AI & Models.

  2. Review available backends and models.

  3. Configure necessary connections.

  4. Select the active global model.

  5. Adjust temperature and max tokens if needed.

Expected result#

The platform is pointed at the global model you want to use for new messages.

Limits and notes#

  • Existing chats are preserved after a model change.

  • New messages use the new active model.

  • Configure one provider to get started; Ollama is local, while OpenAI requires a valid API key.

  • Teachers and Students cannot see the identity of the active model.

AI and Models provider configuration

Knowledge#

Task: configure knowledge settings#

Goal#

Define global retrieval and citation rules for the entire platform.

Before you start#

  • You have opened Admin settings.

Steps#

  1. Go to Operations → RAG.

  2. Adjust chunking.

  3. Select the embedding model or backend.

  4. Adjust retrieval limits.

  5. Enable or disable citation behavior.

Expected result#

The platform updates its global knowledge and retrieval configuration.

Limits and notes#

  • Retrieval limits control the maximum number of source chunks sent to the model and the maximum number of visible citations.

  • These rules are global and affect all lessons and classes.

RAG and knowledge settings

Audit#

Task: review the audit log#

Goal#

Check relevant administrative events without leaving the Admin panel.

Before you start#

  • You have opened Admin settings.

Steps#

  1. Go to Audit.

  2. Filter by info, warning, or error.

  3. Review the events you need to investigate.

Expected result#

You see only the events covered by the v1 minimal audit.

Limits and notes#

  • The v1 Audit Log covers account removals, model changes, support-ticket lifecycle events, user and administrator password changes, and material processing failures.

  • This view does not replace external technical monitoring.

admin-audit-tab — tab with severity filters and event list.

System#

Task: review system status and general settings#

Goal#

Check basic operational visibility and adjust branding or global theme.

Before you start#

  • You have opened Admin settings.

Steps#

  1. Go to Operations → Overview to review available runtime health.

  2. Go to System → General to review application name, logo, and theme.

Expected result#

You can review the basic operational state of the platform and adjust the general configuration available in v1.

Limits and notes#

  • Runtime status is read-only.

  • If GPU information is missing, the interface should degrade gracefully.

  • General does not make the platform multi-tenant; it only adjusts basic app configuration.

General system settings

Support and passwords#

Task: manage support requests#

Open Support queue to search and filter requests, open the original message, resolve a ticket, or reopen it when more work is required.

Administrator support queue

Task: set a user’s password#

Open Users & roles, choose an active user, and use the password action. The interface does not reveal the previous password and blocks invalid or unauthorized changes.

Administrator password action

Operations#

The Admin-only Operations section separates configuration from runtime visibility:

  • Overview summarizes provider, worker, database, and usage health.

  • AI & Models manages generation and embedding providers.

  • RAG shows retrieval configuration and indexing state.

  • Database shows database readiness and storage information.

  • Workers & Indexing shows job queues, durations, and reindex batches.

  • Usage & Costs summarizes AI operations and configured pricing.

  • Diagnostics runs the available local diagnostic checks.

Operations overview

AI and Models operations

RAG operations

Database operations

Workers and indexing operations

Usage and costs operations

Diagnostics operations

Use the shared Account and Settings guide for personal profile, password, appearance, motion, support, and account controls.

When to ask for help#

  • If an action is blocked, check whether it protects a minimum rule such as keeping at least one active Admin.

  • When reporting a problem, share your role, the blocked action or affected class, and a screenshot of the state you see.