Web console overview
How the console is laid out, what each group in the sidebar is for, and who can see what.
The console is the browser app. It is where an organization is set up and where the whole picture is read: every agent, every session, every signal, and the analytics across them.
Everything is scoped to one organization. The switcher at the top of the sidebar changes which one you are in, and the rest of the console follows.
The sidebar
Three groups, and they map onto three different jobs.
Work
Day-to-day use. Everyone in the organization gets these.
| Item | What it is for |
|---|---|
| Home | Your starting point, with a debrief launcher and the recent activity list |
| Feed | The organization's shared stream of posts, updates and approvals |
| Analytics | Usage and signal dashboards across the organization |
| Ask Auron | A chat about your organization's data as a whole |
| Reports | Long-form research reports about a record over a period |
| Knowledge Graph | A network view of records, the sessions they were discussed in, and the signals found |
Configure
Setting up what the agents are and what they can do. This is the half of the product the mobile app does not have.
| Item | What it is for |
|---|---|
| Agents | The AI personas that join meetings and chats |
| Skills | Packaged behaviours you attach to agents |
| Entities | The kinds of thing you track, their fields, and their records |
| Toolkits | Connections that let agents call your other systems |
| Knowledge Stores | The documents and text agents ground their answers in |
| Automations | Triggers and actions that run around your sessions |
| Signal Categories | How detected signals are grouped |
Organization
Administration: general settings, users and teams, access, labels, custom fields, secrets, usage, webhooks, integrations and the AI constitution.
Members with the user role see only Integrations in this group, since that is the one thing here that is about their own account rather than the organization's setup.
Read-only for users
Several configuration screens open in a read-only state for anyone with the user role. The agent configuration and canvas are the clearest examples: a user can see exactly how an agent is set up and cannot change it. See Roles and access.
Where to start
Signing in and organizations
Accounts, single sign-on, invitations, and creating an organization.
Set up your first agent
Name it, write its instructions, give it skills, entities, knowledge and tools, then publish it.
Activities
Every meeting and chat in the organization, searchable and filterable, with the signals beside them.
The mobile app
What the same organization looks like on a phone, and which parts only exist there.