View user detail
Open the detail page for an organisation or Harbor Soho user to review identity, account status, visible memberships and assigned roles. If the selected user is internal, the same route opens the internal user edit form instead.
In this article
Use this guide when an access administrator or location manager needs to check what a user can see and do before changing membership or roles. The action works from both organisation access and location access, so the selected scope is part of the review.
For Harbor Demo Group, the organisation detail can include location membership such as Harbor Soho or Harbor Borough. For Harbor Soho, the location detail focuses on the user summary and location-level roles.
Before you start
- You are signed in and Harbor Demo Group is selected in the app context.
- For the location variant, Harbor Soho is selected as the active location.
- The selected user exists in the organisation or location scope being viewed.
- You have `users:view` or `users:manage` in the relevant scope.
- To view assigned roles, you also have `permissions:view` or `permissions:manage` in the same scope.
- To change role assignments from the detail page, you have `permissions:manage`.
Instructions
- 1.
Open Users
Open the Users tab from organisation access or location access. Use organisation access to review group-wide membership across Harbor Demo Group, or location access to review the user in Harbor Soho.
- 2.
Open the detail
Use the row action labelled View or Edit for the selected user. The label depends on your permissions, but both actions open `organization/access/users/:userId` or `location/access/users/:userId` for the current scope.
- 3.
Review identity and status
Check the summary for the display name, avatar, email, phone number and status. Owner status takes priority, invited users remain invited, and accepted users appear as active or inactive depending on the active flag.
- 4.
Check organisation locations
In organisation scope, use the Locations table to confirm which locations are associated with the user and whether a staff role is shown for each one. This table is not part of the location-scoped detail.
- 5.
Review roles
If role visibility is available, use the roles section to review assigned roles, their scope and their descriptions. View role opens a real role detail while preserving the parent user context; the synthetic owner role cannot be opened as a real role.
- 6.
Update roles if allowed
When role management controls are visible, select or clear assignable role checkboxes and choose Save changes. Saving only adds or removes roles in the current organisation or location scope; Cancel discards the unsaved selection.
- 7.
Handle internal users
If the selected user uses `internal-credentials` and has matching `internal_access`, the same route opens the internal user edit form. Operators with `users:manage` can edit allowed fields; view-only operators see disabled fields.
Validations and limits
- The detail route needs a `userId`; the location variant also needs both `selectedOrgId` and `selectedLocationId`.
- Without `users:view` or `users:manage` in the selected scope, the users area and detail show no access.
- Without `permissions:view` or `permissions:manage`, the user summary can still be visible but the roles section is hidden.
- Without `permissions:manage`, role checkboxes and Save changes controls are hidden.
- The synthetic owner role cannot be selected, deselected or opened as a normal role detail.
- Full name and login id are required when saving an internal user edit form.
- Password is optional on internal user edit, but must be at least 6 characters when entered.
- The backend rejects invalid email values and unsupported email changes for non-native authentication providers.
Expected result
The operator leaves the page knowing the selected user identity, status, visible memberships and assigned roles in the current scope. If permitted role changes were saved, they are applied only to that organisation or location context.