Skip to main content
The Olira Console is the authenticated app your team uses to configure the platform, manage patients, and inspect what agents see. Use it to wire up data sources, choose which event types you collect, build view templates, and debug ingestion end to end. The section is organized by task:

Patients

Directory, enrollment, and the per-patient state explorer.

Settings

Team and roles, API keys, MCP access, and security policies.

Observability

Logs, state-affecting events, and generated views.

Playground

Try agent behavior against real resolved patient state.
The sidebar has two workspace sections plus global items:
The Data and Outputs sections require observability access on your account. If you don’t see them, ask your organization admin.
The sidebar also exposes the patient state ontology, a full-page reference of the stable modules, event-driven modules, and memory regions active for your organization. It is the same structure documented in Patient state.

Home

Home is the landing dashboard after sign-in and doubles as your configuration hub. It surfaces what is wired up before patients generate data:
  • Setup progress: a banner tracking event types and templates until initial configuration is complete.
  • Integrations: connected data sources, plus a panel to add new ones when integration setup is enabled for your organization.
  • Event types: the catalog log types your organization has enabled. This controls what data Olira accepts and which templates apply.
  • Templates: active and draft view templates, with shortcuts into the template builder. Inactive templates are listed separately so you can reactivate or clean them up.
  • Cohorts: create and manage patient groups used for filtering and template targeting. Available when enabled for your organization.
  • Historical data ingestion: upload and track backfill jobs: job status, per-job detail, and links to the affected patients and views. Available when enabled for your organization.

Setup wizard

The full-screen wizard at first sign-in (also reachable any time from Settings → Getting started) walks through initial configuration:
1

Select event types

Browse the catalog of log types, open any type to inspect its payload schema, and select the ones your organization will send. This drives both what data is accepted and which templates are relevant.
2

Review and confirm

A summary screen persists your event type selections to the organization.
3

Pick starting templates

Choose one or more curated view templates from the catalog as a starting point for patient views.
4

Customize

A guided editor lets you adjust block prompts before finishing. Deeper editing (execution modes, cadence, data sources) happens later in the full template builder.
After the wizard, Settings → Getting started keeps a four-step checklist (integrations, event types, templates, patient data import) so you can track what remains.