Get started A tour of the console
A tour of the console
The console has a navigation rail on the left and a top bar. This page walks through both, then the controls that every list shares.
The navigation rail
The rail has seven parts. What you see depends on your role: an item you have no permission to read is not shown. An item marked SOON is not available yet.
| Part | Pages | What it answers |
|---|---|---|
| Overview | Overview | What is connected, which AI services are used most, which AI tools were found, who uses them most, and which MCP servers and local models exist. |
| Inventory | Machines, Accounts, AI Artifacts, AI Tools, Connections | What do we have? |
| Activity | Interactions, File Events | What happened? |
| Detections | Alerts, Issues | What fired, and what is wrong? See Alerts and issues. |
| Governance | Policies, Engines, Runs, Posture | What decides, and what did it decide? |
| Collection | Connectors, Coverage Matrix | What is collecting, and what does it cover? |
| Settings | Settings | Your workspace: members, roles, logging, plan. |
A section's page opens with its own tabs. The tab you are on is kept in the
address as ?tab=, so a copied address opens the same tab.
Overview
Overview is the first page. It shows a map of What is connected, the most used AI services, the AI tools found, the most active people, MCP servers and local models. A toggle at the top sets the time window.
Inventory
- Machines lists every machine that runs the agent, and is where you enroll more. See Deployment.
- Accounts lists people, merged from machines and platforms.
- AI Artifacts is every AI artifact found. AI Tools is the same inventory narrowed to AI tools.
- Connections lists the platforms you have connected.
Activity and detections
Interactions and File Events are what happened. Alerts and Issues are what a policy made of it. An alert has no triage, and an issue does.
Governance
Policies are your rules. Engines are what they ask about content. Runs lists decisions, one row for each decision a policy made, blocks included. Posture reads every shipped posture check by AI risk.
Collection
Connectors is the catalogue of platforms you can connect. Coverage Matrix shows what the agent's capture covers.
The top bar
Search or jump to
Choose Search or jump to, or press Ctrl K (Cmd K on a Mac). It opens a box that says Go to, or do…. Type part of a page's name to go there. It also offers a few actions: My tickets, New ticket, Notification settings, What's new, Copy diagnostics, and a choice of appearance.
The workspace switcher
The switcher at the top of the rail shows the workspace you are in. Choose it to see Workspaces and switch to another. A platform admin also sees Platform admin.
The workspace is kept on your session, not in the address. Two tabs in the same browser share one active workspace, and a tab that comes back into focus on another workspace reloads.
The Help menu
The Help button in the top bar opens:
- What's new, the changelog: what Oxelone shipped, newest first. A dot on the button means there is an entry you have not seen.
- Docs for this page, or Docs where the page has none. It opens these docs.
- Take the tour, which starts the console's first-run tour again.
- Copy diagnostics, which puts on the clipboard what a ticket would carry about the page you are on: its route, breadcrumbs and the panel that is open. It does not say who you are.
- Console build, at the foot of the menu, when the deployment states one.
Inbox and tickets
The bell opens your Inbox: your notifications. Announcements from Oxelone, such as News, Maintenance, Incident and Action required, arrive there. Maintenance and Incident also show as a strip under the top bar.
Your account menu has New ticket and My tickets. A ticket tells Oxelone something: a Bug, an Idea or a Question. A ticket has a status, replies and followers. See Tickets.
Lists, search and filters
Most pages are a list with the same controls.
Search matches free text. It is separate from filters.
Add filter opens a picker, Find a filter, of the fields the list can be narrowed by. Each filter you add becomes a chip. A chip is one condition:
| Field type | Operators | Example |
|---|---|---|
| A choice from a set | is, is not | Category is Agent skill, Prompt |
| A date | before, after | Last seen before 1 Aug 2026 |
Choosing several values in an is condition means any of them.
When you have two or more conditions, a Match control sets how they combine: All (every condition must hold) or Any (at least one must hold). There are no nested groups: one flat list of conditions with one joiner. Clear all removes them.
Each condition appears once. A field already in the list is not offered again.
The filter in the address
A list keeps its filter in the address as ?filter=, so a filtered view can
be copied and shared. The form is the join, then one segment for each
condition, separated by semicolons:
- The first segment is
allorany. - Each later segment is
field~operator~values. The operators arein,nin,beforeandafter. Values are separated by commas, and a date is a UTC time in RFC 3339 form. - A value cannot contain
;,~or,. A condition that does is dropped. - A filter holds at most 20 conditions and 64 values for each condition.
- A field name the list does not know is refused, and a hand-edited or truncated filter loses the segments it cannot read rather than failing.
Policies have their own filter rows, with a different grammar. See Policies.
Opening a row
Opening a row docks an inspector beside the list. The row is kept in the
address as ?open=.