> For the complete documentation index, see [llms.txt](https://help.givechariot.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.givechariot.com/account-management/team-management.md). # Team Management Chariot allows you to manage who has access to your account and control what each team member can do. ### User Roles There are four roles in Chariot, each with different levels of access. Choose the role that best matches each team member’s responsibilities.
OwnerAdminFinanceDevelopmentViewer
Add & Remove Userstruetruefalsefalsefalse
Add & Remove External Financial Accountstruefalsefalsefalsefalse
Transfer Funds (Money Movement)truetruetruefalsefalse
Export Datatruetruetruetruefalse
View Datatruetruetruetruetrue
Free accounts support up to 10 users. If you need additional access, you can upgrade your plan or reach out to our team. *** ### Inviting Team Members
To invite someone to your account: 1. Navigate to Settings → Team 2. Select “Invite user” 3. Enter their email address and assign a role Invited users will receive an email to join your Chariot account. *** ### Removing Team Members
To remove a user: 1. Navigate to Settings → Team 2. Find the team member 3. Select “Remove” This will revoke their access immediately. Account Owners and Admins will be notified via email when a user is removed. *** ### Updating User Roles Account Admins and Owners can update a user’s role at any time from the Team settings page. --- # 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://help.givechariot.com/account-management/team-management.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.