Licenses
Client licenses, the servers using them and their agents.
| Client | License key | Server | Agents | Users | Status |
|---|
Sign in with your username, password and the 6-digit code from your authenticator app.
New colleague? I have an invitation code
Enter your username and the invitation code a colleague gave you. Next you choose your password and enroll your authenticator app.
Scan the QR code with your authenticator app, or type in the key below. Then choose your password and enter the code the app shows.
Signing in now takes a password plus a code from an authenticator app
(Microsoft Authenticator, Google Authenticator, 1Password, …).
Enter the old superadmin secret to continue. It has been removed
from .env, and you will choose a new password in the next step.
Scan the QR code with your authenticator app, or type in the key below. Then choose a new password and enter the code the app shows.
Operator sign-in has not been set up yet. For security, setup only works on the
SuperServer machine itself: open http://127.0.0.1:42792/ there.
Client licenses, the servers using them and their agents.
| Client | License key | Server | Agents | Users | Status |
|---|
A key for a client: their own server (on-premise) or a workspace hosted on your master server (cloud).
Your sign-in, the master server token and everyone's recent sign-in activity.
Lets your MASTER OmniTool server authenticate to this SuperServer when it runs on
another machine or connects through the HTTPS domain. Not needed when it runs on this machine and uses
http://127.0.0.1:42792.
config.yml under
orchestration: as master_token: <token> and restart it.
SuperAdmin accounts of the cloud dashboard (master server): they manage every cloud workspace.
You get a temporary password, shown once. At their first sign-in on the cloud dashboard they choose their own password and enroll their authenticator. The cloud server applies the change at its next sync (usually within 30 seconds). Confirm with your authenticator code.
OmniTool servers published for remote access. People open them from OmniSuite; they show on the edge address.
Our team: everyone who manages OmniSuite, each with their own password and authenticator app. They sign in at OmniSuite like everyone else.
You get a one-time invitation code (valid 72 hours). Give it to them with the username: on the OmniSuite sign-in page they choose “I have an invitation code”, set their password and enroll their own authenticator. Confirm with your authenticator code.
How fast this SuperServer hands out new builds. Agents update only when an admin pushes the update from their server's dashboard.
Downloaded once here and handed to every client server, which matches it against its own inventory (servers send only product names, never hosts or versions).
Sends recovery-email verification and password-reset codes to client administrators.
Providers, models and agent packages for every client: changes apply on the next request, no update needed.
Every AI call of every client: models, tokens, latency and cost.
| Client / Organization | License Key | Requests | Prompt | Completion | Total | Last Active |
|---|
| Timestamp | Client | Model | Prompt | Completion | Total | Latency | Status |
|---|
Enable or disable modules allowed for this client. Changes sync automatically in real-time to both Cloud Server and Client Servers.
Manage administrators and users for this tenant workspace. Changes sync to the client's server and cloud dashboard.
AI calls of this client: models, tokens, latency and cost.
| Timestamp | Model | Prompt | Completion | Total | Latency | Status |
|---|
If checked, the Cloud Server allows full interactive device and remote access. If unchecked, the workspace is treated as On-Premise (private device data stays on client server; cloud only sees counters).