> For the complete documentation index, see [llms.txt](https://docs.spectralink.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.spectralink.net/amie-advanced/using-the-platform/roles-and-permissions.md). # Roles and permissions Every AMIE user has a role — **Owner**, **Admin**, **User** or **Viewer** — that decides which actions the user can take, and a group that decides which handsets, batteries and users they can see. Both are set when the user is created, under **Settings** on the **Users** tab, and neither can be changed in this console afterwards. This page lists what each role can do. ## Why this page matters If a button is grayed out for you, or an **Access Denied** dialog appears when you try something, your role is almost always the reason. This page tells you which role you would need, so that your AMIE administrator — an **Owner** or **Admin** — can request the right one for you rather than "more access". If you are that administrator, it tells you which role to give a new colleague. A **Viewer** can look at the fleet and change nothing, and is the role selected by default when you add a user. ## Before you start Your own role appears beneath your name in the [user menu](/amie-advanced/using-the-platform/the-console.md#your-user-menu) at the top right of every screen. To see other people's roles you need the list on the **Users** tab under **Settings**, which loads only for **Owner** and **Admin** users. ## The four roles | Role | In one line | | ---------- | -------------------------------------------------------------------------------------------------- | | **Viewer** | Sees the fleet in their group and the groups beneath it; changes nothing | | **User** | Everything a **Viewer** can, plus editing a handset's notes and sending a message to a handset | | **Admin** | Everything a **User** can, plus handset log bundles, users, groups, enrollment, sites and licenses | | **Owner** | Everything an **Admin** can. In this console an **Owner** and an **Admin** can do the same things | Each user holds one role, and what a role can do cannot be changed in this console. ### What each role can do Actions the console offers today, and the roles that can take them. Yes means the role can take the action; a dash means it cannot, and the button is grayed out, except in the three places listed beneath the table. | Action | Where | Viewer | User | Admin | Owner | | ----------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------------------------ | ------ | ---- | ----- | ----- | | Edit a handset's **Notes** | [Device details](/amie-advanced/using-the-platform/device-details.md) | — | Yes | Yes | Yes | | **Send Message** to a handset | [Device details](/amie-advanced/using-the-platform/device-details.md) | — | Yes | Yes | Yes | | **Request Log Bundle** and **Delete Selected** log bundles | [Log Bundles](/amie-advanced/using-the-platform/device-details/device-log-bundles.md) | — | — | Yes | Yes | | See the list of users, and **Add user** | [Users](/amie-advanced/using-the-platform/settings/settings-users.md) tab under **Settings** | — | — | Yes | Yes | | **Add Group**, and the **+** beside a group that adds one beneath it | [Groups](/amie-advanced/using-the-platform/settings/settings-groups.md) tab under **Settings** | — | — | Yes | Yes | | **Start Enrollment** and **End Enrollment**, and see and copy the **Enrollment ID** | [Group Details](/amie-advanced/using-the-platform/settings/settings-group-details.md) tab under **Settings** | — | — | Yes | Yes | | **Add Site** | [Sites](/amie-advanced/using-the-platform/sites.md) | — | — | Yes | Yes | | See the list of licenses, **Add license** and **Delete Selected** licenses | [Licenses](/amie-advanced/using-the-platform/settings/settings-licenses.md) tab under **Settings** | — | — | Yes | Yes | Enrollment is how a handset is joined to your Space — see [How AMIE works](/amie-advanced/introduction/how-it-works.md). An action not listed here is available to every role (the **Users** and **Licenses** tabs are the exception — see below): opening every screen in the sidebar — **Dashboard**, **Devices**, **Batteries**, **Alerts**, **Performance**, **Sites**, **Access Points** and **Settings** — searching, filtering and sorting, opening a handset's or a battery's page, and downloading a handset's log bundle. Three places do not follow the grayed-out rule. For a **Viewer** or **User**, the **Users** tab reads **Failed to load users.** and an **Access Denied** dialog appears; the **Licenses** tab opens to an **Access Denied** dialog and an empty tab; and on the **Group Details** tab the **Enrollment ID** reads **You don't have permission to view this**. ## What a role does not decide A role decides what you can do. Which handsets, batteries and users you can see is decided by the group your user was placed in: you see that group and every group beneath it, on every screen, and nothing else — see [The console](/amie-advanced/using-the-platform/the-console.md#which-groups-you-can-see). An **Admin** placed at a regional group administers that region only: the users they add are placed in groups within it, and the handsets they can message are the region's. ## Common tasks ### Add a user See [Add a user](/amie-advanced/using-the-platform/settings/settings-users.md#add-a-user), where the role and the group are chosen. ### Change someone's role or group Not available in this console. A role and a group are set when the user is created; to change either, your AMIE administrator contacts Spectralink support — see [Getting help](/amie-advanced/introduction/getting-help.md). ## What to look for * A grayed-out button. Your role does not include that action; the [What each role can do](#what-each-role-can-do) table says which role does. Hover over the button and the pointer changes to a "not allowed" symbol; no explanation appears. * **Access Denied** when you press a button that was not grayed out. Your role was changed after you signed in. Sign out and back in; the buttons that no longer apply to you are then grayed out. Opening the **Users** or **Licenses** tab as a **Viewer** or **User** also shows it — see [What each role can do](#what-each-role-can-do). * **Device not found.** on a link a colleague sent you. This is about your group, not your role: the handset sits in a group you cannot see. To change that, your AMIE administrator asks Spectralink support to move your user to a higher group — see [Change someone's role or group](#change-someones-role-or-group). * A **Viewer** who needs to send messages to handsets needs the **User** role, not **Admin**. **User** is the smallest role that can change anything. * An **Admin** who cannot see all the users in the Space. The **Users** tab lists only users placed in groups that **Admin** can see. Space-wide administration needs a user placed at the topmost group in the Space. ## Related * [The console](/amie-advanced/using-the-platform/the-console.md) — the group selector and what you can see * [Users](/amie-advanced/using-the-platform/settings/settings-users.md) — the list of users, their roles and groups * [How your Space is organized](/amie-advanced/introduction/how-your-space-is-organized.md) — groups and how they nest * [Getting help](/amie-advanced/introduction/getting-help.md) — who to contact to change a role or a group --- # 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.spectralink.net/amie-advanced/using-the-platform/roles-and-permissions.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.