> ## Documentation Index > Fetch the complete documentation index at: https://docs.getunbound.ai/llms.txt > Use this file to discover all available pages before exploring further. # Users > Everyone in your organization, their roles, groups and connected tools | | | | ----------- | -------------------------------------------------------------------------------------------------------- | | **URL** | `/users` | | **Sidebar** | Users | | **Roles** | Everyone · the list is scoped to what your role may see, and **User Groups** is Admin · Analytics Viewer | Users is the directory of your organization — who is here, what they can do, and which AI tools they have connected. An Admin and an Analytics Viewer see everyone; a manager sees themselves and their reports; anyone else sees only their own row. ## What's on the page ### Tabs | Tab | URL | Roles | | --------------- | -------------------- | ----------------------------------------------------------- | | **Users** | `/users` | Everyone | | **User Groups** | `/users/user-groups` | Admin · Analytics Viewer, who reads it without the controls | ### User table | Column | Contents | | ------------------- | --------------------------------------------------------------- | | **Email** | The person's address | | **Department** | Their department · shown once anyone in the org has one | | **Manager** | Who they report to · shown once anyone in the org has one | | **Role** | Admin, Analytics Viewer or Member. An Admin changes it in place | | **Connected Tools** | The AI tools they have set up | | **Status** | Their account status. An Admin changes it in place | Department and Manager come from your identity provider, so they are changed there rather than here. See [Settings → Integrations](/dashboard/settings). ### Rows named after a serial number During an MDM rollout you may see rows whose name and email are a hardware serial at your organization's email domain — `C02XK1ABCDEF@yourcompany.com` — with an information icon beside the email pointing at **Settings → Devices**. Nothing is broken: each row stands in for one device whose owner is not yet known. These rows read **Accepted** in the **Status** column like anyone else, so the serial-shaped email and that icon are what identify one. | | | | ---------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Is it a person?** | No. It stands in for one device whose owner is not yet known | | **Does it count as an adopted user?** | No. A placeholder stands in for a device, not a person, so adoption and usage figures leave it out — the **Status** badge is not a reliable tell here | | **What happens when the owner is identified?** | Map the serial to an existing person and the serial-number row leaves the list — that device, its connected tools and everything already recorded against it appear on the person's row instead. If your MDM starts reporting the owner's own first and last name for that serial, the same row simply becomes their ordinary account | | **Does a directory sync touch it?** | No. An Okta sync skips these rows, so it will neither enrich one with a department or manager nor suspend one | A stand-in persists for as long as the serial has no owner attached to it. Resolve one by mapping the serial to a person on the **Devices** tab of [Settings](/dashboard/settings), or by making sure the [connected MDM](/mdm-integrations/overview) reports a first and last name for that serial. ### User Groups Groups scope policies. They carry no permissions of their own — a group decides which policies reach someone, not what they may do in the dashboard. | Column | Contents | | ----------- | ------------------------------------------------------------------------------------ | | **Name** | What the group is called | | **Members** | How many people are in it | | **Scope** | **All Users** for the whole organization, or **Selected** for the members you picked | | **Created** | When it was made | ### Unbound Setup in the side panel A person's panel shows an **Unbound Setup** section headed **Setup Tampered**, listing each machine by serial number with one line per tool: | Line | Meaning | | ------------------------------- | ------------------------------------------------------- | | *Setup removed*, then the tool | The managed configuration is no longer present | | *Setup modified*, then the tool | The configuration is present but the hook script is not | ## Filters and controls | Filter | Values | | ----------------- | -------------------------------------------------------------------- | | **Role** | The roles in your organization | | **Department** | Departments · shown once your organization has them | | **Team Manager** | Managers · shown once your organization has them | | **Status** | Account status, including **Suspended** | | **Unbound Setup** | **Removed** · this one appears as a chip only while the filter is on | **Search by name, email…** filters the directory, from three characters up. **Search members…** is the picker inside a group. The Unbound Setup filter is held in the URL as `?tampered=true`, so a filtered view can be shared. ## What you can do | Action | Result | | ---------------------- | ------------------------------------------------------------------------------------ | | **Invite User** | Adds someone to your organization · Admin | | Select a person | Opens the **person panel**, below | | Create or edit a group | Sets which members it covers · Admin | | Select rows | Shows a count of what you have picked, with a control to clear the selection · Admin | | **Update Role** | Sets Admin, Analytics Viewer or Member across the selected people · Admin | | **Update Status** | Suspends or reactivates the selected people · Admin | | **Delete User Group** | Removes it, with the warning *This action cannot be undone* · Admin | Both bulk changes confirm first, listing every person you picked with the value they move from and to. Anyone already at the target value reads **No change** and is left alone; if that is the whole selection, the dialog is skipped and the page says *No changes needed*. Role and Status can also be changed one person at a time, from the badge in their row. ### Person panel | Section | Contents | | ------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **Details** | Their department and manager · shown when either is known | | **Connected Tools** | The AI tools they have set up and when each was last active, or **No activity yet** | | **Policies** | Every policy that reaches them, in four groups — **Tool**, **Security**, **Model** and **Cost** — each with a count, and each tool policy naming its MCP server or command family and the action it takes | | **Unbound Setup** | Their machines and the state of the Unbound install on each · shown only when a setup has been tampered with | Developers can repair their own machines with `unbound doctor --fix`. Where a tool was set up by the organization, the command says so and prints the form to run instead: `sudo unbound doctor --fix`, or the same command in an Administrator terminal on Windows. ## Messages you may see | Message | What it means | | ----------------------------------- | --------------------------------------------------------------------------------------------------- | | `Could not update users. Try again` | A bulk change was not saved. The dialog stays open with your selection intact | | `Some users were not updated` | Part of the selection changed. The message names how many of how many, and retrying covers the rest | | `No changes needed` | Everyone you picked already holds the value you chose | | `Failed to delete user group` | The group is still present | ## Common questions **Why is a developer being blocked?** Select them and read the **Policies** section of their panel, which resolves every policy reaching them across all their groups, grouped into Tool, Security, Model and Cost. **How do I give someone access to Unbound?** **Invite User**, which is an Admin action. **Why can a colleague see something I cannot?** Roles differ in what they reach. The [role table](/dashboard/overview) lists which parts of the dashboard each role uses. **A developer's Unbound setup shows as removed — what now?** Their panel lists the affected machines and tools. They run `unbound doctor --fix`; if a tool was set up by the organization, the command names it and prints the form to run instead — `sudo unbound doctor --fix`, or the same command in an Administrator terminal on Windows. ## Related | Page | For | | --------------------------------------------------------- | -------------------------------------------------- | | [Home](/dashboard/home) | The Tampered Devices card that opens this filtered | | [Analytics — Users](/dashboard/analytics/users) | Per-developer activity and spend | | [Policies — Agentic Use](/dashboard/policies/agentic-use) | Scoping policies to the groups set here |