# CHAT_PARTICIPANT_NOT_ALLOWED

Canonical page: https://docs.ovok.com/errors/chat-participant-not-allowed

**HTTP 403.** Problem type: [`https://docs.ovok.com/errors/chat-participant-not-allowed`](https://docs.ovok.com/errors/chat-participant-not-allowed).

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

Someone you named may not see the patient the thread is about, so they may not take part in it. Everyone in a thread must be able to read its patient under their own access policy; `participants` in the answer lists who may not.

A patient's thread about another patient who shares with them is between the two of them only; naming anyone else answers this code without `participants`.

## Troubleshooting [#troubleshooting]

1. Leave the people listed in `participants` out of the thread.
2. Or give them access to the patient first, for example by the patient sharing their record with them, then open the thread again.

## Retry safely [#retry-safely]

Retrying with the same people gives the same answer until their access changes. Opening a thread is safe to repeat: the same patient and people return the same thread.

## 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.
