> 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/set-up-your-workspace.md).

# Set Up Your Workspace

Create your Kick account and get your business workspace ready.

### Create your account

Go to [use.kick.co/register](https://use.kick.co/register) to sign up. During registration you'll create your workspace and add your first business entity.

***

### Add your business entity

An entity represents a single business. When you register, Kick creates your first entity automatically. You'll be asked for:

* **Business name**
* **Entity type:** LLC, S-Corp, Sole Proprietor, etc.
* **Bookkeeping start date:** the date Kick will start pulling in transactions from

If you own more than one business, you can add additional entities at any time.

→ [Multi-Entity](/setting-up/multi-entity.md)

***

### What's next

Once your workspace is created:

1. [Connect your accounts and integrations](/setting-up/connect-your-accounts-and-integrations.md): link your bank accounts, credit cards, and financial tools
2. [Invite your team](/setting-up/invite-your-team.md): add your accountant, bookkeeper, or business partners
3. Review your [transactions](/common-workflows/transactions.md): Kick will start [categorizing](/common-workflows/categorization.md) automatically once accounts are connected

Review our [Setup guide](/best-practice-guides/setup-guide.md) for best practice from Kick.


---

# 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/set-up-your-workspace.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.