> For the complete documentation index, see [llms.txt](https://help.doctorlogic.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.doctorlogic.com/docs/agency-permissions/adding-a-new-user.md).

# Adding a New User

1. In the admin center’s side menu, click on **Users** (the little human icon 👤) 
   1. Or visit: <https://admin.doctorlogic.com/manage/authorization/userlist>
2. From the page’s top menu, click **Users** then click the green **Create New** button
3. The new user will automatically have the **Default Roles applied.** You may adjust as needed. (in the case of most customers, the selections should be **Customer Approver, Reporting, Opportunities, and Articles\_Publisher.**)
4. Fill in **Email**,  **Last Name**, and **First Name.**&#x20;
   1. Note: If the last name is not provided, try looking on the client’s website to see if it’s listed in a bio. If not, use the practice name as their last name.
5. **Suite**: Add the same suite name found in the main site home page under the “Suites“ section
   1. *You can also find it by looking for any active user under the same customer or with the same email address*
6. Check the **Active** checkbox, and click **Create**.&#x20;
7. Repeat steps for each user
8. Once you are done making changes, click **“Clear Authorization Cache”.**


---

# 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.doctorlogic.com/docs/agency-permissions/adding-a-new-user.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.