# CHAT_WRITE_NOT_ALLOWED

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

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

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

Your own access policy does not let you create a `Communication` about this patient, so you may not open a thread or send a message about them. Ovok writes chat on your behalf only after your policy allows the write.

## Troubleshooting [#troubleshooting]

1. Ask your project's admin for an access policy row that allows `create` on `Communication` for this patient, for example `Communication?subject=%patient` for patients or `Communication?_compartment=%org` for clinic staff.
2. Then try again with a new token.

## Retry safely [#retry-safely]

Retrying gives the same answer until your access policy changes. Opening a thread and sending with the same `clientId` are both safe to repeat.

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