> For the complete documentation index, see [llms.txt](https://docs.kick.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.kick.co/accountants/managing-clients/add-your-first-client/add-existing-kick-users-as-clients.md).

# Add Existing Kick Users as Clients

If your client already has a Kick workspace, they can invite your firm directly — no need to create a new workspace from your Clients tab.

### Is your client already on Kick?

This flow is initiated by your client, not by the accountant. Your client adds your firm from within their existing workspace, and you receive an email invitation to accept.

Share these steps with your client:

1. Click your **profile icon** in the top right.
2. Click **Members** (under the Workspace section).
3. Click **Add team**.
4. Enter one or more accountant email addresses.
5. Set the role to **Accountant**.
6. Select which entities (businesses) you'd like them to access.
7. Click **Confirm** for the popup below to send invites.

<div data-with-frame="true"><img src="https://290614220-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FiOfJtU5BnOhuPqTiOHth%2Fuploads%2FwA07RIAVe3M9zKnhkqA1%2FCleanShot%202026-03-09%20at%2010.19.38%402x.png?alt=media&#x26;token=5db39f63-b657-4204-b68d-3526e84e7866" alt="Confirmation popup showing &#x22;We&#x27;ve found an organization linked to this invite&#x22; with firm name and Confirm button"></div>

After your client completes the steps above, you'll receive an email invitation. Once you accept, their workspace will automatically appear in your Clients tab.

{% hint style="info" %}
Tip: If the invite doesn't arrive, ask your client to go back to Members and resend it using the options menu (⋯) next to the pending invitation.
{% endhint %}


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.kick.co/accountants/managing-clients/add-your-first-client/add-existing-kick-users-as-clients.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.