# POLICY_NOT_IN_PROJECT

Canonical page: https://docs.ovok.com/errors/policy-not-in-project

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

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

The `id` names an access policy that exists but belongs to another project, such as a project yours links to. `/v1/access-policies` and the access policy tools manage only the policies of the caller's own project. Nothing was changed.

## Troubleshooting [#troubleshooting]

1. List this project's policies with `GET /v1/access-policies` or `list_access_policies` and take the `id` from there.
2. To change a policy of another project, sign in to that project and change it there.

## Retry safely [#retry-safely]

Retry with an `id` from this project. An unchanged call 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.
