Start with organization, facility, and governance

Ovahol works best when the tenant structure is settled first. Organization context, facility context, governance rules, and roles decide how the rest of the application behaves for everyone who joins the workspace.

By the end of this stage: The right people are working in the right facility with the right operational rules already in force.

Modules involved: Organization Profile, Facilities, Governance, Invitations

What to do

1. Set the operating context

Create or join the organization, then select the facility where the operational records will live. The workspace switcher at the top of the sidebar controls which facility context is active.

2. Define governance rules

Set what the facility requires before devices can be commissioned, transferred, retired, or disposed. Organization-level governance sets the baseline; facility governance can layer in overrides and policy documents.

3. Bring the right roles in

Invite engineering, facility admin, and clinical users into the same governed workspace. Invitations can be issued at global, org, or facility scope depending on the role.

4. Use the structure everywhere else

Every registry, maintenance, acquisition, and reporting flow later depends on this scope being correct. Getting it right once here saves re-work across every downstream module.

5. Know the plan limits

The organization's plan caps device records, users, and facilities. When the plan no longer covers the facilities in use, the extra facilities open read-only: the application refuses writes and says so, rather than silently discarding data. Check the limits before a large intake. See Billing and plans.

6. Keep the workspace legible

Two surfaces cut across every stage. Notifications report what the system did on your behalf — an import finished, a lifecycle record changed — and the audit log records who changed what, which is what an auditor asks for. Neither replaces the operational records; they point at them.