Antylogic
DemoApp login

399 operational guides

Docs sections
DocsUsers and roles
Device

How to review organisation users

Use the Users tab in Users and roles to review the external users visible in an organisation, search the server-side list, check status and contact details, and confirm linked locations.

In this article

The organisation Users tab gives administrators one place to review external users for Harbor Demo Group, including status, email, phone and linked locations such as Harbor Soho and Harbor Borough.

Search and pagination are handled by the server, so the table reflects the current organisation membership list rather than a client-side filter.

Before you start

  • You are signed in and the app has a selected organisation context.
  • Open Configuration > Organization > Users and roles, or use `organization/access?tab=users`.
  • The Users tab can appear with organisation `users:view` or `users:manage`; the list request itself requires `users:view`.
  • Use `users:manage` only when invite, edit or remove actions are part of the workflow.

Instructions

  1. 1.

    Open Users and roles

    Go to Configuration > Organization > Users and roles and select the Users tab. The page shows `Users and roles`, the `Users` section, the search field and, when allowed, `Invite user`.

  2. 2.

    Review the user table

    Read each row across `Name`, `Status`, `Email`, `Phone` and `Locations`. Empty contact fields show `-`, status appears as a badge, and linked locations appear as up to three avatars with a `+N` count for the rest.

  3. 3.

    Search users

    Type into `Search by name or email`. The page waits briefly, resets to page 1 and reloads the server-side list with the query. The backend also matches phone values, even though the placeholder names only name and email.

  4. 4.

    Move through pages

    Use the table pagination controls when there are more users than the current page size. The default page size is 10, and the page values are sent to the organisation users endpoint.

  5. 5.

    Open a user record

    Select a row or use the row action. Operators with `users:manage` see `Edit`; read-only operators see `View`. The list opens the organisation user detail screen for the selected user.

  6. 6.

    Handle unavailable states

    If the list is loading, wait for `Loading users and roles...`. If loading fails, verify organisation access and refresh. If there are no matching rows, the table shows `No users found.`

Validations and limits

  • `GET /api/app/{orgId}/users` requires `users:view`; `users:manage` controls management actions but is not equivalent for the backend list request.
  • The organisation list excludes users whose `primary_auth_provider` is `internal-credentials`.
  • Search text is trimmed and applied against full name, email and phone; blank or whitespace-only searches are not sent.
  • Invalid UI page and page-size values fall back to page 1 and page size 10.
  • The API accepts `status` values, but the standard organisation Users UI does not expose a status filter.
  • The owner is shown as `Owner` when the user matches the organisation owner, and the owner cannot be removed from the row action.
  • A user with only role permissions may open Users and roles but will not see the Users tab.

Expected result

Administrators get a current, server-backed view of external organisation users, including status, contact details and linked locations, and can open each user for review or management according to their permissions.