> For the complete documentation index, see [llms.txt](https://www.opentimeclock.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://www.opentimeclock.com/docs/product-q3/settings/users.md).
# Users
It is where administrators add, edit, and manage employee accounts.
This section allows you to create new users, assign roles (such as employee, manager, or administrator), set login credentials, configure pay rates, and control access permissions. By managing users here, you ensure every employee has the correct setup for time tracking, scheduling, and reporting.
***
**Active Users Only (Dropdown)**
Filters the list of users shown — you can view only active users or include archived/inactive ones.
***
**User List Panel**
Displays all employees/users in your company account. Clicking a name lets you view or edit that user’s details.
***
**Add User**
Button to create a new user profile.
***
**Select to Archive**
Lets you archive (deactivate) selected users without deleting their records.
***
**Import Excel**
Allows you to bulk-upload user information from an Excel file to quickly add multiple employees.
***
**Tabs (General / Personal / Access / Employment / Notes)**
Switch between different sections of the user profile:
* **General:** Basic user info (name, username, email).
* **Personal:** Employee’s personal details (address, phone, etc.).
* **Access:** Role, permissions, and login credentials.
* **Employment:** Job-related information like department, pay rate, or hire date.
* **Notes:** Add custom notes about the employee.
***
**User Information Fields**
Fields to edit or add employee’s name, username, and email address.
***
**Delete This User**
Option to permanently delete a user from the system (use carefully — this removes their 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://www.opentimeclock.com/docs/product-q3/settings/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.
