# RELATED PERSON WITHOUT ACCESS POLICY

Canonical page: https://docs.ovok.com/errors/related-person-without-access-policy

**HTTP 409.** Stable Problem Details type: [`https://docs.ovok.com/errors/related-person-without-access-policy`](https://docs.ovok.com/errors/related-person-without-access-policy).

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

A membership with no AccessPolicy reaches the whole project. A carer membership always gets Ovok's built-in carer policy, so this means the membership was changed by hand. Ovok refuses to add the share rather than change what the account can reach. Clients should branch on `type` and `status`, not on human-readable `detail` text.

## Troubleshooting [#troubleshooting]

Ask a project admin to restore the carer's membership with its built-in policy, or remove the membership and have the patient invite the carer again. Do not give a carer membership full project access. Compare the request with the relevant endpoint's documentation and confirm the authenticated project and environment. Record the request path and `traceId` before escalating; the identifier lets an administrator find server-side context without sharing credentials or patient data.

## Related endpoint guidance [#related-endpoint-guidance]

Use these pages to check the route, project settings, and request requirements associated with this error:

- [Carers](/authentication/carers)
- [Share readings with a carer](/invitations/share-with-a-carer)

## Retry safely [#retry-safely]

Correct the request, configuration, access or project state described above before retrying. Repeating an unchanged request will normally return the same error; for writes, check whether the first attempt changed state before sending it again. Follow endpoint-specific idempotency and concurrency guidance. Do not retry in a tight loop or use a broader permission or project setting to bypass the check.

## 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 sensitive patient data from the report. The [Error responses guide](/errors) explains the response fields, while the [machine-code registry](/errors/machine-codes) lists every endpoint-specific type audited for this release.