AI assistants & API: troubleshooting
Fixes for common problems when connecting an AI assistant or creating an API key. For how it works, see AI assistants & API; for step-by-step instructions, see AI assistants & API: how-to.
I don’t see where to accept the terms
Section titled “I don’t see where to accept the terms”Why it happens: only an organisation owner or Admin (Write for API keys) gets the acceptance checkbox. Other roles are told to ask an owner or Admin. There is no separate Settings page for these terms.
How to fix it: ask an owner or Admin to accept the terms when they next connect an AI assistant or create an API key. Send them AI assistants & API: how-to.
COHO says an owner or admin must accept the API/MCP terms
Section titled “COHO says an owner or admin must accept the API/MCP terms”Why it happens: the organisation hasn’t accepted the current terms yet, and your role can’t accept them.
How to fix it: an owner or Admin follows Accept the API/MCP terms as an owner or Admin, then you click Connect again on the same page, or start a new connection from your AI assistant.
“Accept the current API/MCP terms for this organisation before creating an API key”
Section titled ““Accept the current API/MCP terms for this organisation before creating an API key””Why it happens: you’re creating a key, but the organisation hasn’t accepted the current terms.
How to fix it:
- If you’re an owner or Admin, tick I accept the API/MCP terms on behalf of my organisation on the create-key screen, then create the key.
- If you don’t see the checkbox, ask an owner or Admin to accept the terms (connect an AI assistant, or create a key themselves).
“You do not have permission to access the requested resource”
Section titled ““You do not have permission to access the requested resource””Why it happens: your role can’t manage API keys or accept the terms (common on restricted roles).
How to fix it: ask an organisation owner or Admin to accept the terms. To connect an AI assistant yourself afterwards, ask them to approve your MCP access — not to give you Write for API keys. If you only need an API key, ask them to create it.
COHO says my organisation requires owner or admin approval before I can connect MCP
Section titled “COHO says my organisation requires owner or admin approval before I can connect MCP”Why it happens: MCP access for people who aren’t owners or Admins is off until it’s approved. This is separate from accepting the API/MCP terms.
How to fix it:
- Click Request access on the connect screen.
- Ask an owner or Admin to open Users > MCP access requests and Approve your request (and to turn on Allow MCP connections if it’s off).
- Retry Connect from your AI assistant.
MCP connections are disabled for this organisation
Section titled “MCP connections are disabled for this organisation”Why it happens: Allow MCP connections is off under Users > MCP access.
How to fix it: an organisation owner or Admin turns Allow MCP connections on and clicks Save.
My existing API key or AI connection still works, but a new one is blocked
Section titled “My existing API key or AI connection still works, but a new one is blocked”Why it happens: existing keys and connections are not cut off when terms are updated. Only new API keys and new AI assistant connections need the current acceptance.
How to fix it: have an owner or Admin accept the current terms, then create the new key or connection.
Error messages
Section titled “Error messages”| Message (as shown) | What it means | What to do |
|---|---|---|
| “Accept the current API/MCP terms for this organisation before creating an API key.” | Terms not accepted for this organisation | Owner or Admin accepts them on create key or connect |
| “Terms version is out of date. Refresh and accept the current version.” | The terms were updated while you had the screen open | Reload the page or start the connection again, then accept the current terms |
| “An owner or admin of … must accept the API/MCP terms before anyone in the organisation can connect.” | Your role can’t accept; terms still needed | Ask an owner or Admin; then try again |
| “An owner or admin must accept the current API/MCP terms for this organisation before anyone can connect.” | Same, from the connection API | Same as above |
| “You do not have permission to access the requested resource.” | Your role can’t manage API keys / terms | Owner/Admin accepts terms; approve MCP access for a connection (don’t grant API keys Write just to connect) |
| “Your organisation requires owner or admin approval before you can connect MCP.” | MCP access not approved for you | Request access, then owner/Admin approves under Users > MCP access requests |
| “MCP connections are disabled for this organisation.” | Allow MCP connections is off | Owner/Admin turns it on under Users > MCP access |
| “You do not have permission to accept API/MCP terms for this organisation” | Your role lacks Write for API keys | Ask an organisation owner or Admin |
| “You do not have permission to view API/MCP terms status for this organisation” | Your role lacks Read for API keys | Ask an organisation owner or Admin |
Support reference like coho_mcp_… |
A correlation id for support | Include it if you contact COHO support |