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

# Admin Users

### **Admin Users — User Management**

The **Admin Users** page lets you view and manage all administrator accounts that have access to your CubiLock workspace. These admin accounts represent IT team members, managers, and other internal staff who can perform administrative actions such as enrolling devices, applying policies, and configuring profiles.

Centralized admin user management is a standard feature in MDM solutions to ensure that responsibilities and access rights are properly assigned and controlled across your organization’s device management infrastructure.

### Navigation:

User Management → Admin Users

#### **What You Can Do on This Page**

The Admin Users screen provides a comprehensive list of all users with administrative privileges. You can:

* **View existing admin users** — including their name, username, email, assigned role, phone number, and last login.
* **Create new admin accounts** for additional team members.
* **Assign roles** to define what administrative functions a user can perform.
* **Deactivate or remove admin users** (depending on your permission structure).

This centralized view helps you ensure that only authorized personnel can access and manage enterprise devices securely.

#### **Admin Users List**

When you open this page, you’ll see all currently configured admin users in a table format.

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

The table typically includes:

* **Name** — The full name of the admin user.
* **Username** — The login name used to sign in.
* **Status** — Whether the account is active or disabled.
* **Email** — Contact email associated with the admin account.
* **Role** — The assigned access level (e.g., Admin, Manager, User).
* **Phone No.** — (Optional) Phone number of the admin.
* **Last Seen** — The last time the admin logged into CubiLock.

#### **Creating a New Admin User**

To add a new administrator:

1. Click **Create Admin User** in the top right corner of the Admin Users page.

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

2. A **Create New Admin User** modal will appear with fields to enter the admin’s details.

* Fill in the required information:
  * **Name**
  * **Username**
  * **Email**
  * **Password** (and confirm)
  * **Role** — Select from a predefined list of user roles with corresponding permissions
  * **Phone number** (optional)
* After completing the form, click **Create** to add the admin user.

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

#### **Roles and Permissions (Optional Context)**

Admin roles define what actions a user can take within the CubiLock console. Common role types include:

* **Admin** — Full access to all features and settings.
* **Manager** — Can manage devices and profiles, but may have limited access to user management.
* **User** — Limited access, typically restricted from sensitive admin functions.

Assigning roles helps enforce least‑privilege security principles and ensures team members have access only to the features needed for their function.


---

# 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.cubilock.com/user-management/users/admin-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.