> 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/roles-and-permissions.md). # Roles & Permissions Kick uses two types of roles: **Organization** and **Workspace**. Organization roles belong to your firm's team members. Workspace roles belong to client-side users within a specific client's books. *** ### Organization roles Organization roles control firm-level access: clients, team invites, and billing. * **Owner:** Full firm-level access, including managing billing. Can manage all users, clients, workspaces, and settings. * **Admin:** Full access to all clients, entities, and the firm workspace. Can manage all users (Admins, Managers, and Members). Cannot manage billing. * **Manager:** Access to assigned clients. Can create clients and manage Managers and Members on those clients. * **Member:** Access to assigned clients and entities only. | | Owner | Admin | Manager | Member | | -------------------------------------------------- | ------------------------------- | ------------------------------- | ------------------------------- | ------------------------------- | | Manage billing | | | | | | Add Admins to organization | | | | | |

Add Managers/

Members to organization

| | | | | | Add/delete clients | | | | | | Add entities | | | | | | Remove accounts | | | | | Organization roles carry a workspace role into each client. Owners, Admins, and Managers act as workspace Admins, and Members act as workspace Accountants. That is why a Member can add entities and remove accounts inside the clients they are assigned to, even though they hold no firm-level administrative access. *** ### Workspace roles Workspace roles control what client-side users can do within a specific client's books.

Role	What they can do
Primary Admin	Workspace-wide access. The only role that can manage workspace billing and transfer Primary Admin. Typically the business owner.
Admin	Workspace-wide access across all entities. Manage team members, entities, and accounting settings.
Accountant	Assigned entities only. Everything a Member can do plus manage team members, edit chart of accounts, and edit settings. Cannot invite Admins, and cannot reach entities they are not assigned to.
Member	Assigned entities only. Access to reports, transactions, documents, connect bank accounts, and create tasks.

| | Primary Admin | Admin | Accountant | Member | | --------------------------------------------------- | ------------------------------- | ------------------------------- | ------------------------------- | ------------------------------- | | Manage workspace billing | | | | | | Invite Admin to workspace | | | | | |

Invite Accountant/

Member to workspace

| | | | | | Add entities | | | | | | Remove accounts | | | | | | Add locks | | | | | | Edit chart of accounts | | | | | | Connect and manage integrations | | | | | {% hint style="info" %} **Note:** Once a period is locked, workspace Members can only view transactions and reports, add memos, and attach receipts. {% endhint %} *** ### Entity access Admins and the Primary Admin always have access to all entities, current and future. This cannot be scoped. Accountants and Members are scoped to the entities you assign them. *** ### Adjust permissions #### For team members 1. Go to **Team** from the sidebar. 2. Find the team member and click the **⋯** menu. 3. Select **Configure permissions**. #### For workspace members 1. Open the client's workspace. 2. Go to **Settings → Members**. 3. Click the **⋯** menu next to the person's name. 4. Select **Configure permissions**. *** {% hint style="info" %} By default, **Admins** always have access to all entities, including your personal account. You can only configure the access for **Accountants** and **Members.** {% 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 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/managing-clients/roles-and-permissions.md?ask=&goal= ``` `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. 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.