> 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/settings/settings-users.md). # Users The **Users** tab of the [Settings](/amie-advanced/using-the-platform/settings.md) screen lists the people who can sign in to your [Space](/amie-advanced/introduction/how-your-space-is-organized.md), with each person's role and group, and is where you add a user. To reach it, select **Settings** in the sidebar, then the **Users** tab. ## Why this screen matters Who can see which handsets, and who can change anything, is decided here: each user is created with a role, which fixes what they can do, and a group, which fixes what they can see. When a colleague reports a grayed-out button or a handset they cannot find, this list shows the role and group behind it. **Last Login** also shows who is actually using the console and who never signed in after being added. ## Before you start Requires the **Admin** or **Owner** role. For other roles the tab reads **Failed to load users.** and an **Access Denied** dialog appears — see [Roles and permissions](/amie-advanced/using-the-platform/roles-and-permissions.md). The list shows the users placed in your own group and the groups beneath it. Users placed higher in the tree, or in another branch, are not listed. The tab does not follow the [group selector](/amie-advanced/using-the-platform/the-console.md#the-group-selector) in the header. ## Screen layout ### The controls above the table A search box reading **Search users...** until you type, a **Refresh** button that reloads the list, an **Export** button, and **Add user**, which opens the dialog for creating a user. Each is described under [Controls](#controls). ### The table One row per user, a checkbox in the first column and eight columns, described under [Columns](#columns). The list opens sorted by **First Name**, A to Z. Selecting a row does nothing beyond its checkbox; there is no page for a single user. With no one to list the table reads **No users to display.** — no user is placed in the groups you can see, or none matches your search. ### The paging controls Beneath the table: **Show** with a list of **10**, **25**, **50** and **100** rows per page (**25** when the tab opens); a note giving the rows in view and the total, in the form **Showing 1 to 25 of 60 users**; and **First**, **Previous**, **Next** and **Last**, with the page you are on and the number of pages between them, in the form **Page 1 of 3**. The buttons that cannot move further are grayed out. ## Controls | Control | What it does | | -------------------------------------------------------------------------------------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Search box | Narrows the list to users whose email address, first name or last name contains what you typed, ignoring case. The list refreshes a moment after you stop typing and returns to page 1 | | **Refresh** | Reloads the list with the same search, sort and page | | **Export** | Has no effect yet. \[GAP-users-1] | | **Add user** | Opens the **Add New User** dialog — see [Add a user](#add-a-user) | | Checkbox at the top of the table | Selects or clears every row on the page | | Checkbox on a row | Selects that user. Selecting has no further effect yet: no action uses the selection \[GAP-users-2] | | **First Name**, **Last Name**, **Username (Email)**, **Group**, **Role**, **Created Date** or **Last Login** heading | Sorts by that column — see [Sorting](#sorting) | | **Show** list | Changes how many rows a page holds and returns to page 1 | | **First**, **Previous**, **Next**, **Last** | Move between pages | ### Sorting Selecting a heading the list is not sorted by sorts it ascending — A to Z, or oldest first; selecting the heading it is already sorted by reverses the direction. Users with nothing in the column are listed last either way. Changing the sort returns you to page 1. **Service User** cannot be sorted. ## Columns | Column | What it shows | | -------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **First Name** | The user's first name. **—** if none is recorded. Sortable | | **Last Name** | The user's last name. **—** if none. Sortable | | **Username (Email)** | The email address the user signs in with. Sortable | | **Service User** | Always **No**. Not sortable | | **Group** | The name of the group the user is placed in — the group they see, with everything beneath it. **—** if the group is not one you can see. Sortable | | **Role** | **Admin**, **Owner**, **User** or **Viewer** — what the user can do; see [Roles and permissions](/amie-advanced/using-the-platform/roles-and-permissions.md). **Admin** is shown in blue, the others in gray. **—** if none is recorded. Sortable | | **Created Date** | The date the user was added, in your browser's time zone. Sortable | | **Last Login** | The date the user last signed in, in your browser's time zone. **—** if they have never signed in. Sortable | {% hint style="warning" %} TODO: what a service user is. Every row reads **No** and nothing in the console creates one. {% endhint %} ## Icons and indicators | Icon or indicator | Meaning | When it appears | | ------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------- | | Magnifying glass in the search box | Marks the search box | Always | | Circular arrows on **Refresh**, down arrow on **Export**, **+** on **Add user** | Mark the buttons | Always | | Up-down arrows beside a heading | The list is not sorted by that column. **Service User** shows them too, but selecting it does nothing: that column cannot be sorted | Every heading except the one sorted by | | Up arrow or down arrow beside a heading | The column the list is sorted by: up arrow ascending, down arrow descending | One heading at a time | | Blue **Admin** under **Role** | The user has the **Admin** role | Per row | | Gray role name under **Role** | **Owner**, **User** or **Viewer** | Per row | | Spinning icon in place of the rows | The list is loading and has nothing to show yet | While loading | ## Common tasks ### Add a user Requires the **Admin** or **Owner** role. {% stepper %} {% step %} Select **Add user**. The **Add New User** dialog opens. {% endstep %} {% step %} Fill in **First Name**, **Last Name** and **Username (Email)**. All three are required and marked with an asterisk on screen. The email address is the sign-in name and must not already belong to an AMIE user; it is stored in lower case. **Phone Number** is optional. {% endstep %} {% step %} Choose a **Role**: **Admin**, **Owner**, **User** or **Viewer**. **Viewer** is preselected. What each can do is on [Roles and permissions](/amie-advanced/using-the-platform/roles-and-permissions.md). {% endstep %} {% step %} Choose a group under **Group (Device Access)**. The list shows every group you can see, each as a path from the topmost group you can see, and that topmost group is preselected. The note beneath reads **Controls which devices this user can see and modify**: the user will see that group and everything beneath it — its handsets, batteries and users. The group sets how far the user's reach extends; the **Role** you chose in the previous step decides whether they can change anything within it. {% endstep %} {% step %} Select **Add User** at the bottom of the dialog (**Cancel** or the **×** closes it without saving). The dialog closes and the new user appears in the list, sometimes after a few seconds. {% endstep %} {% endstepper %} The new user receives an email with the subject **Welcome to AMIE - Set Your Password**, containing a six-digit code and a link to set a password. Both are valid for 48 hours. Until a password is set, the user can still sign in by choosing the email-code option on the sign-in screen — see [How AMIE works](/amie-advanced/introduction/how-it-works.md). If something goes wrong the dialog stays open and reads, in red: | Message | Meaning | | ----------------------------------------- | -------------------------------------------------------------------------------------- | | **A user with this email already exists** | The address is already an AMIE user, in your Space or another. Use a different address | | **Failed to add user. Please try again.** | The request did not complete. Try again; if it repeats, contact Spectralink | {% hint style="warning" %} TODO: whether an administrator can resend the password-setup email, and what a user who let the 48 hours pass should do. {% endhint %} ### Change a user's role or group, or remove a user Not available in this console. Role and group are fixed when the user is created, and the checkboxes select users for no action. To change or remove a user, contact Spectralink — see [Getting help](/amie-advanced/introduction/getting-help.md). {% hint style="info" %} Not yet available: removing a user. \[GAP-users-2] {% endhint %} ## What to look for * **—** under **Last Login** on a user added weeks ago. They have never signed in. Check that the welcome email reached them; it may be in a junk folder. * A user who cannot see a handset. Read their **Group**: they see that group and those beneath it, and nothing else. A user who needs the whole fleet must be placed at the top of the tree — see [Which groups you can see](/amie-advanced/using-the-platform/the-console.md#which-groups-you-can-see). * A user who cannot press a button. Read their **Role**; the [What each role can do](/amie-advanced/using-the-platform/roles-and-permissions.md#what-each-role-can-do) table says which role the button needs. **User** is the smallest role that can change anything. * More **Admin** rows than you expect. Every **Admin** and **Owner** can add users and groups, start enrollment and manage licenses for everything they can see. * A user you expect who is not listed. They are placed above your group or in another branch, or the search box still holds text. Clear the search; if they are still missing, an administrator at the top of the tree can see them. * **Failed to load users.** with an **Access Denied** dialog. Your role is **User** or **Viewer**. ## Metrics on this screen * [Time and time zones](/amie-advanced/metrics-reference/time-and-time-zones.md) — **Created Date** and **Last Login** are displayed dates in your browser's time zone ## Related * [Roles and permissions](/amie-advanced/using-the-platform/roles-and-permissions.md) — what each role can do * [The console](/amie-advanced/using-the-platform/the-console.md) — which groups a user can see, and the user menu * [Groups](/amie-advanced/using-the-platform/settings/settings-groups.md) — the groups a user can be placed in --- # 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/settings/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.