CHAT_WRITE_NOT_ALLOWED
Access policy does not allow chat writes: what the CHAT_WRITE_NOT_ALLOWED error means and how to fix it.
HTTP 403. Problem type: https://docs.ovok.com/errors/chat-write-not-allowed.
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
- Ask your project's admin for an access policy row that allows
createonCommunicationfor this patient, for exampleCommunication?subject=%patientfor patients orCommunication?_compartment=%orgfor clinic staff. - Then try again with a new token.
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
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 explains the response fields, and the machine-code registry lists every endpoint-specific type.
Last updated on