> For the complete documentation index, see [llms.txt](https://research-amp.gitbook.io/research-amp-user-documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://research-amp.gitbook.io/research-amp-user-documentation/configuration/customization-and-layout/adding-users.md).
# Adding Users
To add new users of the back end of your Research AMP site, go to Dashboard > Users > Add New. Fill in their information, assign their role, and send them a notification. You may edit the users and ascribe them new roles in the Users section of the dashboard.
You are likely to need a couple of users with full administrator privileges, which allow them to install WordPress plugins, change themes, delete content, and add or delete other users.
An editor can add, edit, publish, and delete their own and others' WordPress posts, but cannot access admin features.
Authors can add, edit, and publish their own posts, while contributors can edit their posts but not publish them. The subscriber role is not supported by Research AMP.
---
# 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://research-amp.gitbook.io/research-amp-user-documentation/configuration/customization-and-layout/adding-users.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.