> 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/reference/roles-and-permissions.md). # Roles & Permissions Control what each person on your team can see and do in your workspace. Every person you invite to your Kick workspace is assigned a role. Roles control what they can access - from viewing reports to managing accounts and billing. *** ### Workspace roles
RoleWhat they can do
AdminWorkspace-wide access. Manage team members, entities, accounting settings, and view billing.
MemberAssigned entities only. Access to reports, transactions, documents, connect bank accounts, and create tasks.
AccountantAssigned entities only. Everything a Member can do plus manage team members, and edit chart of accounts, locks and Accounting settings.
View-onlyAssigned entities only. Can view all data in those entities, but cannot make changes. Can still download from reports.
*** ### Choosing the right role. **Admin** is the right role for someone who needs full control across your workspace: managing team members, entities, and accounting settings. Admins automatically have access to all current and future entities, and can view your plan and billing details in Stripe. **Member** is the right role for a business partner, office manager, or collaborator who needs to work in the books on specific entities - reviewing reports and transactions, uploading documents, connecting bank accounts, and creating tasks - without changing accounting settings or managing team members. **Accountant** is the right role for a bookkeeper or outside accountant who needs to do everything a Member can do plus manage team members and edit chart of accounts, categories, locks, and settings. You can scope their access to specific entities. **View-only** is the right role for someone who needs to review the books without making changes: a tax advisor, investor, or partner. They can see all data in the entities you assign them, and they can still download from reports. *** ### Entity access When you invite someone, you choose which entities they can access - one specific business, or all of them. You can also enable **New business entities** so they automatically get access to any entity you add in the future. Admins always have access to all entities, current and future. This cannot be scoped. *** ### Change a team member's role 1. Go to **Settings → Members** 2. Click **⋯** next to the person's name 3. Select **Configure permissions** 4. Update their role and entity access 5. Click **Save** *** ### The Primary Admin Every workspace has one Primary Admin - typically the business owner. The Primary Admin is the only person who can manage billing and transfer the Primary Admin role to someone else. There can only be one Primary Admin per workspace, and the role cannot be removed - only transferred. *** ### FAQs
Can a Member invite other people? No. Only Admins and Accountants can invite and manage team members.
What's the difference between Admin and Accountant? Both have the same ability to manage your books. The difference is scope - Admins automatically get access to all entities, while Accountants are scoped to the specific entities you assign them.
Can I have more than one Admin? Yes. You can have multiple Admins. There is only one Primary Admin, but you can have as many Admins as you need.
What if I need to remove someone's access? Go to **Settings → Members**, click **⋯** next to their name, and select **Remove from workspace**. Their access is revoked immediately.
Can my accountant change my chart of accounts with a template? Yes. Your accountant's firm can apply its Chart of Accounts template to your entities. This can add accounts and groups to your chart, move accounts into different groups, and archive accounts to match the firm's standard. Your existing transactions, journal entries, and reports stay intact. If you want a change undone, ask your accountant.
--- # 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/reference/roles-and-permissions.md?ask=&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.