IF IT FAILS
If something does not work.
| What you see | Why it happens | What to do |
|---|
| On the access-permission check screen, a form is not marked OK | The token’s user has no permission for that form | Give the user permission for the form in Priority. Go back to the wizard and click Check again. |
|---|
| I did not save the API key | The key is shown only once | You can renew it in the admin portal. |
|---|
| The sign-in code did not arrive | The email is on its way, or went to spam | Check your spam folder, or click Resend code when the countdown ends. The Use a different email link takes you back to enter a different email. |
|---|
Every known problem, in the help center
FAQ
Common questions
What prevents an agent from writing something you didn't intend?
Writing is off by default. When you turn it on, in a conversation every operation is shown for approval first and only then sent, with a server-signed, single-use token that expires after 90 seconds. An automation that runs with no person in front of it, such as n8n, skips the approval step only with an API key that was given write access and explicit permission to skip it, and that is off by default.
What data does the server see?
Only what your organization's API user may see in Priority, and within that only what each user's own permissions allow: read, write and modules. Credentials are stored encrypted, identifying details are masked in logs, and every tool call is recorded in an audit log.
Does it work with on-premises Priority, or only the cloud?
Both. The server connects to Priority's REST API in the cloud or on a local server reachable over HTTPS, and nothing is installed inside Priority. You need an API user with an API license and a personal access token (PAT). An on-premises server behind a firewall allows the service's fixed egress addresses.
What does our Priority admin need to do?
A little, and it arrives ready: after you sign up, they get an email with a live setup page and a printable guide, with the forms, menu paths and firewall addresses. Each step they finish is checked and turns green on your screen: server, token, company and API license.
Does it also work in Claude Code, and for a whole organization?
Yes. In Claude Code you add the server with one command in a terminal: claude mcp add --transport http leonai-priority https://priority-mcp.leonai.io/mcp. On Claude Team or Enterprise only the Owner adds a connector, and then each member clicks Connect and signs in as themselves.