Skip to main content
New organizations are provisioned using a signup code issued by Olira. The setup takes a few minutes and ends with your team on the Console landing page, ready to configure your platform.
1

Get your access code

Olira provides your designated admin with a signup code in the format OLIRA-XXXXXXXX. Codes are single-use and valid for 30 days.Don’t have a code yet? Contact your Olira representative to request one.
2

Create your organization

Go to console.olira.ai, click Get Started, and complete the two-step registration:
  1. Enter your Organization Name and your Access Code (the Console validates the code before proceeding)
  2. Create your admin account (sign in with SSO or register with email and password), then complete your profile (name, email)
Once complete, your organization is active in the Console.
3

Invite team members

During setup, or any time from Settings → Team, invite colleagues by email. Each person receives a link to join the organization and set up their own account.
RoleCan do
adminEverything: organization settings, user management, and all data access
devPatient data, observability tools, and user management (cannot promote members to admin)
memberPatient data and standard clinical features
4

Create API keys

Go to Settings → API Keys and create one or more keys for your backend services. Each key can be scoped to limit which Olira operations it can perform.
Keys are shown only once at creation. Copy and store them immediately in a secrets manager.
For scopes, the Authorization header format, and patient tokens, see Authentication.

Platform configuration

After registration, the Console landing page guides you through configuring your platform. Complete the steps below before going live. Your selections determine what data flows through Olira and how patient state is presented to your agents.

Configure integrations

Connect external systems (EMR/EHR, health-information exchanges, devices, and wearables) so data flows in alongside logs you submit yourself. See Integrations for the full walkthrough.

Select your data

In the Console, browse the full catalog of supported log types and toggle on the ones your platform will produce. Your selection determines which parts of the patient state are actively populated. Each log type has a source:
  • Python SDK / REST: your backend submits these via the Olira Python SDK or REST API (e.g. symptom_report, medication_list_update)
  • Integration: populated automatically from a connected integration (for example clinical systems, device feeds, or third-party health data sources)
  • App SDK: your iOS/Android app submits these directly via the Olira App SDK (coming soon). Used primarily for passive device data such as heart rate, sleep, and activity readings.
See the log types catalog for the complete catalog with payload schemas and required fields for every supported log type.

State views

See View configuration for how to choose templates, edit blocks, and manage patient views in the Console.