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

# Users

Read and manage the active or inactive status of Tier 1 users in your Mimeeq account. These are account users; they are different from the company contacts and Tier 2 dealer or partner users represented elsewhere in Mimeeq.

Use List Users to find account user IDs before inspecting a user, changing their status or assigning them to a role. To invite a person to the account, use Invitations; to manage their permissions, use Roles.

### What you can do

| Task                 | Reference                                                                   |
| -------------------- | --------------------------------------------------------------------------- |
| Find available users | [List Users](https://help.mimeeq.com/developers/users/list-users)           |
| Read one user        | [Get User](https://help.mimeeq.com/developers/users/get-user)               |
| Change user status   | [Set User Status](https://help.mimeeq.com/developers/users/set-user-status) |

### Before you start

Your API key needs `users:read` to read these resources. Use `users:write` for write operations.

### Important behaviour

List Users returns the available users in one data array; it has no cursor or filter parameters. This section does not create users, edit profiles or delete users. Set User Status accepts `ACTIVE` or `INACTIVE` and first checks that the user belongs to this account.


---

# 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.mimeeq.com/api/users.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.