> For the complete documentation index, see [llms.txt](https://docs.docbits.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.docbits.com/administration-and-setup/settings/global-settings/groups-users-and-permissions/users.md). # Users {% embed url="" %}
User list with names and accounts hidden.

User list with names and accounts hidden.

The Users page allows administrators to manage all user accounts in your DocBits organization. Here you can add new users, assign roles, and control access. ## User List The user table displays the following columns: | Column | Description | | ---------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Name** | The full name of the user. | | **E-Mail** | The user's email address, used as their login identifier. | | **Last Login** | Date and time of the user's most recent login. | | **Admin** | Checkbox indicating whether the user has administrator privileges. Admins can access all settings and manage other users. | | **System Admin** | Checkbox indicating the organization's single System Admin — the account DocBits uses for automatic, behind-the-scenes actions (such as automated imports and exports). A System Admin always has Admin privileges too. See [Admin Privileges](/administration-and-setup/settings/global-settings/groups-users-and-permissions/users/admin-privileges.md#admin-vs-system-admin) for the difference between Admin and System Admin. | | **Active** | Checkbox showing whether the user account is currently active. Inactive users cannot log in. | | **Actions** | Menu with options such as editing user details, resetting passwords, or deactivating the account. | Use the **Search** bar at the top to quickly find users by name or ID. ## Login Analytics Click **Login Analytics** to view login activity data across your organization, including login frequency and patterns. See [Login Analytics](/administration-and-setup/settings/global-settings/groups-users-and-permissions/users/login-analytics.md) for the full breakdown. ## Adding a New User 1. Click the **Add User** button in the top-right corner. 2. Fill in the required information: * **Username**: A unique name for the user. * **First Name** and **Last Name**: The user's full name. * **Email Address**: Used for login and notifications. * **Password**: Must comply with your organization's security policies. * **User Role**: Assign the appropriate role (Standard User, Admin, or System Admin). 3. Click **Save** to create the user account. The new user will receive an email notification with their login details and a link to set their first password on the Set Password page. See [Getting Access and Signing In](/end-user-and-partner-section/end-user-section/getting-access-and-signing-in.md#first-password-for-admin-created-accounts). > **Note:** The **System Admin** role can only be chosen while creating a user — it cannot be added or removed later. Each organization can have only one System Admin, and choosing it automatically grants Admin rights too. See [Admin Privileges](/administration-and-setup/settings/global-settings/groups-users-and-permissions/users/admin-privileges.md#admin-vs-system-admin) to learn when to use it. --- # 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.docbits.com/administration-and-setup/settings/global-settings/groups-users-and-permissions/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.