> For the complete documentation index, see [llms.txt](https://docs.uptiq.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.uptiq.ai/ai-workbench-qore/control-center/admin/users.md).
# Users
The Users screen lists everyone with access to the account. Open **Admin → Users**.
The Users screen, listing everyone with access to the account.
Search by name or email. Filter by status. Select **+ Create User** to add someone.
Each row shows **Name**, **Email**, **Phone**, and **Status**. Status is **Invited** or **Active**. Use the row's **Actions** menu to manage that user.
### Create or edit a user
Creating or editing a user opens the same dialog.
* **First Name** and **Last Name** — required.
* **Email** — required. It receives the invitation and identifies the sign-in account.
* **Phone Number** — optional. Include the country code.
* **Role** — required. Select one or more roles. Roles determine what the person can do.
Assign one or more roles when creating or editing a user.
{% hint style="info" %}
Creating a user sends an invitation. Changing a role changes that person's access. Set roles deliberately.
{% endhint %}
### How invited people sign in
Qore is invite-only: nobody can sign up for themselves, whichever sign-in method they use. Once invited, a person can sign in with their email and the temporary password from their invitation, setting their own password the first time, or with Google or Microsoft if those are turned on for your Qore. Invite the exact address they'll sign in with, because a Google or Microsoft account with a different address is refused. See [Single Sign-On](/ai-workbench-qore/control-center/admin/single-sign-on.md) and [Password Sign-In](/ai-workbench-qore/control-center/admin/password-sign-in.md).
***
{% columns %}
{% column width="83.33333333333334%" %}
Maintained by Abhishek Paul AI-assisted, human-approved
{% endcolumn %}
{% endcolumns %}
---
# 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.uptiq.ai/ai-workbench-qore/control-center/admin/users.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.
