> For the complete documentation index, see [llms.txt](https://docs.monogoto.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.monogoto.io/hub/intro/users/manage-users.md).

# Manage users

In the Monogoto Hub's user table, you can view and manage your list of current users.

{% hint style="warning" %}
A user with the same email address (for example: <mike@company.com>) cannot be created in mutiple user roles or multiple accounts. Either you insert a new email or you can use email alias (for example If you are using google workspace you should be able to add the following email <mike+1@company.com>).&#x20;
{% endhint %}

<figure><img src="/files/jnjVhWFCpvM5ZNctMAVe" alt=""><figcaption></figcaption></figure>

**Users table information explained:**

1. **Name** - here you can see a name given to a user.
2. **Email** - an email address of a user.
3. **Profile** - this is a profile of a user. Each profile has different permissions the user can manage.

<table><thead><tr><th width="155">User Profile</th><th>Description</th></tr></thead><tbody><tr><td>Admin user</td><td>Admin user has full permissions. This user can view and change everything in Advanced Console and Hub</td></tr><tr><td>Standard user</td><td>Standard user can do everything like Admin user, except it is not allowed to see/manage pricing and users in Advanced Console and Hub</td></tr><tr><td>Group user</td><td>Group user is limited to managing only selected Thing Groups. This is useful when you have end users that you would like to monitor/manage the status of only specific SIMs</td></tr><tr><td>Monitor user</td><td>Monitor user can only monitor information in Advanced Console and Hub. This user cannot do any changes</td></tr><tr><td>API user</td><td>API user is meant to be used only for API testing and documentation in Advanced Console and Hub</td></tr></tbody></table>

4. **Description** - an optional field where additional information can be written about the user.
5. **Status** - Status informs you about the current state of the user.

<table><thead><tr><th width="190">Status</th><th>Description</th></tr></thead><tbody><tr><td>Active</td><td>This is an activated user that can be successfully used.</td></tr><tr><td>Invited</td><td>This is a use that was created, but did not finish user creation.</td></tr><tr><td>Inactive</td><td>This is a user that was deactivated using the <code>Deactivation</code> action.</td></tr></tbody></table>

6. **Actions** - In actions you can see available actions with a user.

<table><thead><tr><th width="201.33333333333331">Action</th><th width="153" data-type="files">Button location</th><th>Description</th></tr></thead><tbody><tr><td>Edit</td><td><a href="/files/Um6SIdvjaUn6F0x0mR4j">/files/Um6SIdvjaUn6F0x0mR4j</a></td><td>Edit button allows you to edit user settings</td></tr><tr><td>Deactivate</td><td><a href="/files/6yshE8vFbDoaVOZ6t7bV">/files/6yshE8vFbDoaVOZ6t7bV</a></td><td>Deactivate button allows you to temporarily deactivate the user</td></tr><tr><td>Delete</td><td><a href="/files/uDYgGDVV1ek0jqjD2Oil">/files/uDYgGDVV1ek0jqjD2Oil</a></td><td>Delete button deletes the user</td></tr><tr><td>Resend Verification</td><td><a href="/files/MVG1MEWO7Rmo6JVHZB5d">/files/MVG1MEWO7Rmo6JVHZB5d</a></td><td>Resend verification button resend user verification in case the user was not activated or it can be used to reactivate the deactivated user</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 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://docs.monogoto.io/hub/intro/users/manage-users.md?ask=<question>&goal=<endgoal>
```

`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.