> ## Documentation Index
> Fetch the complete documentation index at: https://docs.olira.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Console overview

> Tour of the Olira Console: navigation, the home dashboard, and the setup wizard that configures event types and view templates.

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:

<Columns cols={2}>
  <Card title="Patients" icon="users" href="/console/patients">
    Directory, enrollment, and the per-patient state explorer.
  </Card>

  <Card title="Settings" icon="settings" href="/console/settings">
    Team and roles, API keys, MCP access, and security policies.
  </Card>

  <Card title="Observability" icon="activity" href="/console/observability">
    Logs, state-affecting events, and generated views.
  </Card>

  <Card title="Playground" icon="flask-conical" href="/console/playground">
    Try agent behavior against real resolved patient state.
  </Card>
</Columns>

## Navigation

The sidebar has two workspace sections plus global items:

* **Data**: the observability screens: [Logs](/console/observability#logs), [Events](/console/observability#events), [Views](/console/observability#views), and [Population views](/console/observability#population-views).
* **Outputs**: [Patients](/console/patients) and the [Playground](/console/playground).
* **Home**, **Settings**, **Help**, and a link to these docs are always available.

<Info>
  The **Data** and **Outputs** sections require observability access on your account. If you don't see them, ask your organization admin.
</Info>

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](/read-data/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](/read-data/view-configuration). 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](/send-data/historical-backfill): 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:

<Steps>
  <Step title="Select event types" titleSize="h3">
    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.
  </Step>

  <Step title="Review and confirm" titleSize="h3">
    A summary screen persists your event type selections to the organization.
  </Step>

  <Step title="Pick starting templates" titleSize="h3">
    Choose one or more curated view templates from the catalog as a starting
    point for patient views.
  </Step>

  <Step title="Customize" titleSize="h3">
    A guided editor lets you adjust block prompts before finishing. Deeper
    editing (execution modes, cadence, data sources) happens later in the
    full [template builder](/read-data/view-configuration).
  </Step>
</Steps>

After the wizard, **Settings → Getting started** keeps a four-step checklist (integrations, event types, templates, patient data import) so you can track what remains.