organization vs workspace.md
Organization vs Workspace
Organization
Your organization represents your firm in Kick — the company that owns the subscription and manages the team.
At the organization level, you:
- Manage your team and their client access from Team in the sidebar
- View and manage all clients from Clients in the sidebar
- Control organization-level settings and billing (for Owners)
Everyone under your organization belongs to the same firm, even if they only work on some clients. Organization roles (Owner, Manager, Member) determine what someone can do at the firm level — like creating clients, inviting team members, or managing billing.
Workspace
A workspace is the environment for one client. It contains the chart of accounts, transactions, rules, documents, and an unlimited number of entities — each entity representing a separate set of books. This makes it easy to manage clients with multiple businesses, holding companies, or related LLCs in one place.
Common setups:
- One workspace per client
- A free firm workspace for your firm's own books and to test workflows
Each workspace has its own members and roles. A team member's workspace role determines what they can do inside that workspace — independent of their organization role.
How they work together
| Organization | Workspace |
|---|---|
| Your firm | One client (with one or more entities) |
| Team, clients, firm settings, firm billing | Entities, transactions, COA, workspace members, workspace billing |
| "Should this team member work on this client's books?" | "What can this person do inside this client's workspace?" |
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, and the optional goal query parameter:
GET https://docs.kick.co/accountants/setting-up/organization-vs-workspace.md?ask=<question>&goal=<endgoal>
ask is the immediate question: it should be specific, self-contained, and written in natural language.
goal is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.