Administration

Running an Open Model Gateway installation from the Admin portal, as a Platform Admin or Auditor.

These pages are for Platform Admins, who run the installation, and Platform Auditors, who read everything in Admin without changing it. Open Admin with the Portal switch at the top of the sidebar.

Screenshot to comeAdmin Overview: the setup checklist with most steps done and one route still unpriced, and "Platform at a glance" with users, Teams, Projects, ready models, requests and spend this month.admin-overview

First run

From an empty installation to the first request, following the setup checklist.

People and roles

Platform roles, suspension, the 30-day lifecycle and the last-admin safeguard.

Teams and Projects

Creating shared workspaces, their owners, overrides and cost centers.

SSO groups and SCIM

Mapping identity-provider groups to roles and memberships, and pushing changes with SCIM.

Connections, models and prices

Providers, models, routes, routing and failover, and price versions.

Catalogs

Which models each kind of workspace can use.

Limits and budgets

Stacked layers of rate limits, jobs at once, storage and budgets.

Records

The audit log, key safety, logs, usage and cost centers.

What admins can and can't see

Platform roles give authority over the installation, not over people's private work:

Personal workspaces stay private. Admins and Auditors see their cost and usage totals in reports, never their keys or requests.
Teams and Projects: admins and Auditors see their configuration, members and cost totals. Admin › Logs shows their requests' metadata. Their keys and request details inside the workspace's own pages need a membership, like anyone else.
Making a key in a Team or Project needs a real membership, even for a Platform Admin.

Auditors see every Admin page read-only: no buttons that change anything, and the API refuses changes.