> 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/setting-up.md).

# Setting Up

- [Set Up Your Workspace](https://docs.kick.co/setting-up/set-up-your-workspace.md): Create your Kick account and get your business workspace ready.
- [Multi-Entity](https://docs.kick.co/setting-up/multi-entity.md): Manage multiple businesses from one Kick workspace.
- [Connect Your Accounts](https://docs.kick.co/setting-up/connect-your-accounts-and-integrations.md): Link your bank accounts, credit cards, and financial tools so Kick can pull in your transactions automatically.
- [Universal Importer](https://docs.kick.co/setting-up/universal-importer.md): Upload bank statements or CSVs to bring in transactions when a live bank connection isn't available.
- [Receipts](https://docs.kick.co/setting-up/receipts.md): How to attach receipts to transactions in Kick, and why it matters for taxes and audits.
- [Opening Balances](https://docs.kick.co/setting-up/opening-balances.md): Set starting balances for your accounts so your Balance Sheet and reports are accurate from day one.
- [Chart of Accounts](https://docs.kick.co/setting-up/chart-of-accounts.md): See the accounts behind your books and change how they're grouped, so your Profit & Loss and Balance Sheet read the way you think about your business.
- [Invite Your Team](https://docs.kick.co/setting-up/invite-your-team.md): Add your accountant, bookkeeper, or business partners to your workspace.


---

# 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/setting-up.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.