# Signals route policies

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

Ovok guards every Signals route with custom AccessPolicy rows named `signals_<area>`. They are not FHIR resource types: each one says what a caller may do with Signals, and it is checked on top of the caller's project. Add the exact resource type and interaction to the policy. A catch-all FHIR rule (`*`) does not grant them.

```json
{ "resourceType": "signals_alerts", "interaction": ["read", "update"] }
```

## Capabilities [#capabilities]

A route needs every capability listed for it. The table is built from the [API reference](/api), so it always matches what Ovok serves.

<SignalsCapabilities />

`signals_config:update` also opens [Enable Signals for a Patient](/signals/with-ovok/flows#enrol-patients-one-by-one), together with `Patient` update access in the same policy. Writing a patient's alerting fields through the standalone API needs `signals_config:update` and `signals_silence:update` on top of the route's own capability.

## App types [#app-types]

A **Manager** or **Submitter** application's policy is made from the routes its Signals role may call, so it holds the capabilities in the App types column. Its policy is kept at those rows when Ovok starts: add capabilities through your own policies, not by editing it.

## Example policy [#example-policy]

A ward role that reads alerts and acknowledges them, for its own patients:

```json
{
  "resourceType": "AccessPolicy",
  "name": "Ward alert handling",
  "resource": [
    {
      "resourceType": "Patient",
      "criteria": "Patient?organization=Organization/ward-a",
      "interaction": ["read", "search"]
    },
    { "resourceType": "DetectedIssue", "readonly": true },
    { "resourceType": "Flag", "readonly": true },
    { "resourceType": "signals_alerts", "interaction": ["read", "update"] }
  ]
}
```

The example is illustrative. A `signals_*` row is project-wide: it does not narrow to the Patient criteria, and Patient access alone grants no Signals route.

## Admin and integration behavior [#admin-and-integration-behavior]

Super Admins and project admins pass the capability check for project users. Project scope still applies. `ClientApplication` callers do not get the admin bypass, even if marked as admins: give an integration the exact rows it needs.

## Related [#related]

- [Signals standalone](/signals/standalone)
- [Signals with Ovok](/signals/connected-ovok)
- [AccessPolicy model and membership](./policy-model)
- [Default policies](./defaults)
