> For the complete documentation index, see [llms.txt](https://docs.kula.digital/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.kula.digital/connect-claude-and-access/troubleshooting.md).

# Troubleshooting

Most problems fall into one of a few buckets. Find yours below. If you're still stuck, [contact us](#getting-help).

## Common messages and what they mean

**"401" or "invalid token"** Your connect link or access token has expired or has already been used. Create a fresh one in **app.kula.digital → Connectors** and reconnect — see [Connect Claude](/connect-claude-and-access/claude.md).

**"403" or "scope … cannot call …"** The task needs a higher **permission level** than your connect link or token has. For example, an Analytics-level credential can't see member names. Create a connector at the right level — see [Permission levels](/connect-claude-and-access/scopes.md).

**The AI says it can't see any tables, or returns nothing** Usually one of:

* Your first data import is still running. Give it a few minutes and ask again.
* The data source finished importing but the source has a gap. See [Keeping your connectors healthy](/your-data-sources/operating.md).

**The first answer is slow** The first time you ask a heavy question it does real work. Ask it again and it's quick — recent results are cached for a few minutes.

**A connector shows an error** A provider key may have expired, or the provider had a hiccup. The [Keeping your connectors healthy](/your-data-sources/operating.md) page walks you through reconnecting and recovering.

## Frequently asked

**Do I have to connect everything to get value?** No. One data source gives you real answers. Add more whenever you like.

**Can the AI change my data or charge a card?** No. It reads from your connected tools and can draft messages, but it never sends money, charges cards, posts to socials, or messages members on its own. See [Is my data safe?](/get-started/trust.md).

**Can two people use it at once?** Yes. Create a separate connector per person or assistant so each has its own access and trail. See [Permission levels](/connect-claude-and-access/scopes.md).

**How do I stop it?** Disconnect a data source, or revoke a connector in **app.kula.digital → Connectors**. Access stops within about a minute.

## Current limitations

We'd rather be upfront about what isn't here yet:

* **It reads; it doesn't act in the outside world.** It drafts the email; you send it. By design.
* **Answers are only as complete as your connected data.** If a source isn't connected, or a month is missing from a provider, the AI tells you rather than guessing — but it can't fill a gap it can't see.
* **Each provider has its own quirks and limits** on what we're allowed to read. Those are listed on each connector's page (for example, some Xero data needs a higher Xero plan). See [How connectors work](/your-data-sources/connectors.md).
* **The first import of a large studio can take 20–30 minutes.** It runs in the background; you don't have to wait on the screen.

## Getting help

Email **<support@kula.digital>** and include your studio name and what you were trying to do. If it's about a specific answer, copy the question you asked and what came back — it helps us help you faster.

Found a security issue? Please follow [Responsible disclosure](/trust-and-legal/disclosure.md) instead.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.kula.digital/connect-claude-and-access/troubleshooting.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.