> For the complete documentation index, see [llms.txt](https://help.digits.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.digits.com/client-management/client-management.md).

# Client Management

Manage client access, roles, settings, and day-to-day workflows—everything your firm needs to support clients smoothly in Digits.

***

### **Managing Clients**

<table data-view="cards"><thead><tr><th></th><th></th><th></th><th data-hidden data-card-cover data-type="files"></th><th data-hidden></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><i class="fa-users-gear">:users-gear:</i>  Managing Clients:</td><td><h4>Adding/Removing Clients</h4></td><td>Add new clients or remove inactive ones from your firm.</td><td></td><td></td><td><a href="/client-management/adding-and-removing-client-accounts.md">Adding &amp; Removing Client Accounts</a></td></tr><tr><td><i class="fa-users-gear">:users-gear:</i>  Managing Clients:</td><td><h4>Invite a Client to their Digits Account</h4></td><td>Invite clients to access their books and collaborate in Digits.</td><td></td><td></td><td><a href="/client-management/roles-and-permissions.md">Invite a Client to their Digits Account</a></td></tr><tr><td><i class="fa-users-gear">:users-gear:</i>  Managing Clients: </td><td><h4>What Clients Can &#x26; Can't Do</h4></td><td>What each client role can view, edit, and manage in Digits.</td><td></td><td></td><td><a href="/client-management/what-clients-can-and-cant-do.md">What Clients Can &amp; Can't Do</a></td></tr><tr><td><i class="fa-users-gear">:users-gear:</i>  Managing Clients:</td><td><h4>Upgrade/Downgrade a Client Plan</h4></td><td>Update or change a client’s Digits plan</td><td></td><td></td><td><a href="/client-management/upgrade-downgrade-a-client-plan.md">Upgrade/Downgrade a Client Plan</a></td></tr><tr><td><i class="fa-users-gear">:users-gear:</i>  Managing Clients: </td><td><h4>Client Pays in Digits </h4></td><td>Clients pay directly, firms keep access and oversight.</td><td></td><td></td><td><a href="/client-management/client-pays-in-digits.md">Client Pays in Digits</a></td></tr><tr><td><i class="fa-users-gear">:users-gear:</i>  Managing Clients:</td><td><h4>Customize Your Client's Home Dashboard</h4></td><td>Tailor each client's dashboard to highlight their key metrics.</td><td></td><td></td><td><a href="/firms-home/customize-dashbaords.md">Customize Your Client's Dashboard</a></td></tr><tr><td><i class="fa-users-gear">:users-gear:</i>  Managing Clients:</td><td><h4>The Client's Organization Dashboard (What Your Clients See)</h4></td><td>See what clients see: their home base for entities, team, and settings.</td><td></td><td></td><td><a href="/client-management/the-clients-organization-dashboard-what-your-clients-see.md">The Client's Organization Dashboard (What Your Clients See)</a></td></tr></tbody></table>


---

# 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.digits.com/client-management/client-management.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.
