# Access policies

Canonical page: https://docs.ovok.com/access-policies

An AccessPolicy limits what a project member can do. It is the authorization layer for signed-in users: settings decide whether a flow can run, while an AccessPolicy decides which resources and operations a member can access.

Ovok uses AccessPolicies in two ways:

- **FHIR and project access:** policy rows grant interactions such as reading, searching, creating, updating, or deleting resources. Policies can also scope access with criteria.
- **Signals routes:** Ovok checks a small set of custom AccessPolicy rows for alert, configuration, and threshold operations. These rows work alongside the member's Patient access.

Start with the page that matches your question:

| If you need to… | Read |
| --- | --- |
| Understand policy rows, membership assignment, and what happens when a member has no policy | [AccessPolicy model and membership](/access-policies/policy-model) |
| Create a policy and attach it to members and new patients | [Create an access policy](/access-policies/create-access-policy) |
| Configure the policies assigned to new patients and practitioners | [Default policies](/access-policies/defaults) |
| Grant access to Signals alerts, thresholds, and settings | [Signals route policies](/access-policies/signals) |

## Who can call a route [#who-can-call-a-route]

Most Ovok routes check the caller's role before anything else. A route's page says which check it uses.

- **Practitioner session:** a signed-in practitioner passes the practitioner check. The access policy on the membership then decides which resources the route can read or write.
- **Project admin:** an admin passes the practitioner check and the admin-only check. An admin who holds no access policy also skips the Patient access check that applies to practitioners.
- **Super admin:** a super admin is also an admin, so it passes every check, the super-admin check included.
- **"System Owner" access policy:** a member whose access policy is named `System Owner` passes the practitioner check without being a practitioner. The name is matched case-insensitively.
- **Everyone else:** a patient or carer session is refused with 403 on routes that require one of these roles.

## The key safety rule [#the-key-safety-rule]

Do not assume that a missing policy means limited access. For ordinary project and FHIR access, a project membership without a policy is not restricted by one and can access the project broadly. Assign an intentional, least-privilege policy when you create or invite a member.

Signals routes have an additional check: non-admin callers need the named Signals capability as well as the corresponding Patient access. A broad FHIR policy by itself does not grant the custom Signals capabilities.

## Related setup [#related-setup]

- [Create an access policy](/access-policies/create-access-policy)
- [Set up your project](/authentication/project-setup)
- [Invite a project admin](/invitations/team-members)
- [DEFAULT_PRACTITIONER_ACCESS_POLICY](/settings-and-features/settings/default-practitioner-access-policy)
- [Signals](/signals)
