# POLICY_READ_ONLY

Canonical page: https://docs.ovok.com/errors/policy-read-only

**HTTP 403.** Problem type: [`https://docs.ovok.com/errors/policy-read-only`](https://docs.ovok.com/errors/policy-read-only).

## What this means [#what-this-means]

The access policy is read-only, so updating or deleting it was refused. Either Ovok provisions it (a Signals role, shown as `managed`), or it is a copy of a parent project's policy (shown as `copyOf`). The error says which. Nothing was changed.

## Troubleshooting [#troubleshooting]

1. Check the policy's `managed` and `copyOf` fields with `GET /v1/access-policies/{id}` or `list_access_policies`.
2. For a copy, change the policy named in `copyOf` in the parent project. The copy follows.
3. For a policy Ovok provisions, leave it as it is. To grant different access, create a policy of your own and give it to the members who need it.

## Retry safely [#retry-safely]

Do not retry the same call: it returns the same error. Nothing was changed.

## If the problem persists [#if-the-problem-persists]

Share the HTTP status, problem `type`, request path, response timestamp and `traceId` with your administrator or support contact. Remove access tokens, provider secrets and patient data first. The [Error responses guide](/errors) explains the response fields, and the [machine-code registry](/errors/machine-codes) lists every endpoint-specific type.
