# PROFILE_NOT_ALLOWED

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

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

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

Only a person signed in as a Patient, Practitioner or RelatedPerson can register push devices, because each device belongs to that person's own profile. This session signed in as something else, such as a client application.

## Troubleshooting [#troubleshooting]

1. Register the device from the app after the person signs in, with their own token.
2. Do not register devices for people from a server with client credentials: Ovok would have no person to attach them to.
3. Check that the token you send belongs to the person using the device, not to an admin or integration account.

## Retry safely [#retry-safely]

Retrying with the same token returns the same error. Nothing was written.

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