Coco Kanban — Troubleshooting

Common issues and how to fix them. If your question isn't here, contact your workspace administrator or our support team.

Signing in & access

I can't see a project or workspace. You must be a member of a workspace to see it. Ask an admin to invite you. Being able to sign in doesn't grant access to every workspace.

A feature says "not authorized". That action needs a higher role (Admin/Member). Ask your workspace admin.

Premium features missing

A premium feature (Reports, Teams, AI Agent…) isn't showing up. Premium features are enabled by your plan's license:

  1. Check your plan under Settings → Billing & Plans — the feature may be in a higher tier. See Pricing.
  2. If you believe it should be included, your license may have expired or your team may have exceeded its seat count. When that happens, premium features step down to the core set until the license is renewed. Contact support to refresh your license.
  3. Admins: confirm the license is installed and valid on the instance.

Your data is never removed when a license lapses — only premium features are hidden.

Claude connector

"Couldn't register with Coco Kanban's sign-in service" when adding the connector in Claude's web app. This means Claude tried to use OAuth sign-in, which self-hosted Coco Kanban doesn't offer. You need to send your API key as a request header instead:

  • In the "Add custom connector" dialog, find the Request headers section, choose Authorization, and enter Bearer <your key>.
  • If there's no "Request headers" section — only "OAuth Client ID / Secret" — your Claude account doesn't have that feature yet (it's rolled out gradually by Anthropic). Until it does, use Claude Code instead, which works today. Do not fill in the OAuth fields; they won't work here.

See Connecting Claude & AI for all three methods.

Claude connects but says a tool failed with "permission" / 403. Your key is for a workspace you're not a member of, or the wrong workspace slug is in the URL. The connection URL is .../mcp/<your-workspace> — make sure <your-workspace> is one you belong to. Generate the URL and key from that workspace's Settings → Connect to Claude.

Claude says the connector is "not connected."

  • Check the URL is exactly https://<your-instance>/mcp/<workspace>.
  • Check the header is Authorization: Bearer <key> — the word Bearer, a space, then the key. The key already starts with coco_api_.
  • Regenerate the key if unsure (Settings → Connect to Claude), and reconnect.

Claude connects, but asking "what projects do I have?" fails while creating a work item works. Your instance may need an update. Contact support and we'll bring it up to date.

Integrations

GitHub/Bitbucket won't connect.

  • Re-check the token/app-password and its permissions (repo read, issue write).
  • For Bitbucket, use your workspace slug and username from your profile URL, not your email.
  • Ensure your instance can reach the provider over the internet.

Slack/Teams notifications aren't arriving. Re-run the connection from Settings → Integrations, and confirm the channel / webhook is still valid.

The app is slow, down, or unreachable

We run the infrastructure, so this is ours to fix — not yours.

If Coco Kanban is unreachable, slow, or behaving oddly across the whole workspace (rather than one feature misbehaving), it's an infrastructure issue. You don't need to diagnose it.

Contact support and tell us:

  • what you were doing,
  • roughly when it started,
  • whether it affects everyone or just you.

We'll take it from there — provisioning, uptime, upgrades, backups, and performance are all managed for you.

(Running Coco Kanban on your own infrastructure under a self-hosted agreement? Contact your support channel — your deployment has its own runbook.)

Still stuck? Contact support.