Finding your way
The console is one web application for everyone who uses Olympusx AI. What it shows depends on your role: a page your role cannot use is not in your rail, and a button your role cannot press is not on the page. This page describes the layout and who sees what.
The layout
Section titled “The layout”From the top of the screen:
- The header. The product mark, the search button that opens the command palette, Notifications, and your user menu with Profile, theme, language and sign-out.
- The rail, on the left. The pages you can open, grouped by job.
- The page. Its title, one line on what it is for, and its content.
On a narrow screen the rail folds behind a menu button.
The rail
Section titled “The rail”The rail has two sections. A person in a tenant sees only Workspace, with no section heading. A platform administrator sees both.
Workspace
Section titled “Workspace”| Group | Pages | What it is for |
|---|---|---|
| Overview | Your home page: what needs you, and where to start. See Overview. | |
| My conversations | The conversations you started with an assistant. See My conversations. | |
| Use cases | Code Assistant, Security | Finished jobs the tenant turns on and its people use. |
| Build | Models, Knowledge, Agents, Tools, Skills, Assistants, Playground | What an agent is made of, in the order it is made, then publishing it, then the Playground to try a model. |
| Operate | Runs, Approvals, Conversations, Traces, Overview | What is running, what it did, and what it is waiting for. |
| Evaluate | Review queue, Scores | Judging answers. |
| Govern | Guardrails, Users, Keys and budgets, Usage, Audit, Erasure | Who may do what, what it costs, and the record of it. |
Knowledge has three tabs: Collections, Vector databases and Pipelines.
Platform
Section titled “Platform”Platform administrators only.
| Group | Pages |
|---|---|
| Infrastructure | Clusters, System health |
| Model serving | Model registry, Runtimes |
| Customers | Tenants, Projects |
| Billing | |
| Settings |
What each role sees
Section titled “What each role sees”Each tenant member holds one of five roles. A group whose pages are all closed to a role disappears from that role’s rail.
| Role | What their rail holds |
|---|---|
| End user | Overview and My conversations. |
| Reviewer | Overview, My conversations, Operate (Approvals, Conversations), Evaluate. |
| Builder | Overview, My conversations, Use cases, Build, Operate (all but Approvals), Govern (Guardrails, Keys and budgets, Usage). |
| Auditor | Overview, Use cases, Build (all but Playground), Operate, Evaluate, Govern. Everything is read-only. |
| Admin | Every Workspace page. |
| Platform admin | Every page in both sections, for every tenant. |
The full matrix, page by page, is in Roles. Why the roles are shaped this way is in Roles and permissions.
A signed-in account with no role in a tenant sees one screen that says so, and nothing else. An admin of the tenant gives them a role.
The first time you sign in
Section titled “The first time you sign in”The first time you sign in, the console shows a welcome page for your role. A tenant member sees the things the product does that their role may open, each with a button to start there. A platform administrator sees the setup checklist for the installation. Either way, choosing a tile or Explore on my own takes you on; the page does not come back. Language and theme are set later in Profile. See Profile and preferences.
Get anywhere from the keyboard
Section titled “Get anywhere from the keyboard”Press ⌘ K on a Mac or Ctrl K elsewhere to open the command palette. Type part of a page’s name, or of an agent, run, model or collection in your tenant, and press Enter. It offers only what your role can open. See Command palette.