> 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/for-consultants/set-up-on-their-behalf.md).

# Set up on their behalf

The owner *can* do their own setup. But if you're helping several studios, or the owner would rather you handle it, you can do the connecting for them using a **single-use connect link** — without ever needing their passwords.

## How the connect link works

1. The owner creates their Kula account and, from their admin, mints a **single-use connect link** scoped to a **permission level** they choose.
2. They share that link with you — usually by having Kula **email it to you** straight from that screen.
3. Connect, either way:

   * **One click.** The invite email (and the connect page it links to) has an **Open in Claude** button. It opens Claude with the **Add custom connector** dialog already filled in — connector name and Remote MCP server URL — so you just review, **Add → Connect**, and approve.
   * **By hand.** The same screen shows the link in full. In your AI assistant, **Add custom connector** and paste it as the **Remote MCP server URL** (leave Advanced settings blank), then **Add → Connect** and follow the sign-in/approve prompts.

   Either way your assistant connects to *their* studio scoped to the link's permission level — no password of theirs changes hands.

The link is **single-use** and **time-limited**: once you've used it, it's spent, and it expires on its own if unused. The owner can revoke it at any time. This is the same secure front door the product uses everywhere — you never hold a long-lived secret, and the owner can cut access in one click.

## Connecting the studio's data sources

With access in hand, connect the studio's sources the same way the owner would — each source's page has the steps:

* [Stripe](/your-data-sources/stripe.md) · [Wix](/your-data-sources/wix.md) · [Mindbody](/your-data-sources/mindbody.md) · [Xero](/your-data-sources/xero.md)
* [Meta](/your-data-sources/meta.md) · [Google Analytics 4](/your-data-sources/ga4.md) · [CSV & ClassPass](/your-data-sources/csv.md)

A few things worth doing well, since you're the one setting up:

* **Start with the studio's spine** — usually their booking platform (Mindbody or Wix) plus payments (Stripe). That alone unlocks most questions.
* **Use the right keys.** Where a provider offers a read-only or restricted key (Stripe, Wix, Meta), use it. The connector pages call out which.
* **Kick off the import and let it run.** A big studio takes 20–30 minutes to import. Set it going, then move on to the diagnostic prep.

## Keep the owner's permission level sensible

When you connect, you're working at the **permission level** on the link. **Operations** is the right default — names visible, contact and payment details hidden. Only step up if a specific task needs it. See [Permission levels](/connect-claude-and-access/scopes.md).

## Next

Once the data's importing, work through the first questions *with* the owner, frame a short list of early wins, then [hand off cleanly](/for-consultants/hand-off.md).