Manage user accounts across workspaces
What this achieves
Section titled “What this achieves”This screen lists the accounts that can sign in, across every customer workspace on the platform. It exists so that an access problem can be fixed when nobody inside that workspace is able to fix it.
Required role: Humavera platform staff.
- Go to Platform → Platform Users.
- Search by name or email to find the account.
- Open the actions menu at the end of that row.
- Select Edit to change the name or the Role, then Save.
- Select Block or Unblock to stop or restore sign-in, and confirm.
- Select Reset Password to send that person a password reset email.
What the list shows
Section titled “What the list shows”| Option | Description |
|---|---|
| User | Name and sign-in email. |
| Tenant | The workspace the account belongs to. |
| Roles | The roles held in that workspace. |
| Status | Whether the account is active, invited, inactive, or blocked. |
| Last Login | When the account last signed in, or Never. |
| MFA | Whether multi-factor authentication is on for that account. |
These are account facts. Nothing here shows what the person does inside their workspace, what they can see there, or any HR record belonging to them.
Creating an account in a customer’s workspace
Section titled “Creating an account in a customer’s workspace”Create User makes an account inside a workspace you choose. It asks for the Tenant / Workspace, the Email, the First Name and Last Name, an Initial Password, and a Role. The roles offered are that workspace’s own roles, so they are read once the workspace is chosen.
Use this to give a new customer their first administrator, or to restore access where a workspace has locked itself out — nobody left who can invite anyone. Routine account creation belongs to the customer’s own administrators, in their own settings, where they can see the context you cannot.
Example: HC Corp is created as a workspace, and their first administrator account is created here so somebody can sign in and begin setting it up. Every account after that is theirs to create.
Blocking, unblocking, and password resets
Section titled “Blocking, unblocking, and password resets”| Option | Description |
|---|---|
| Block | Stops that person signing in. Offered on an active account. |
| Unblock | Restores access. Offered on a blocked account. |
| Reset Password | Sends a password reset email to the address on the account. It is not offered on an account that has been invited and has not yet accepted. |
A password reset sends a link to the account holder. It does not reveal or set anyone’s password, and it does not sign you in as them.
What this screen does not do
Section titled “What this screen does not do”There is no way from here to sign in as a customer’s user, to view what that user sees, or to open anything inside their workspace. Changing a role changes what that person is permitted to do in their own workspace; it does not give the platform side a route in.
What happens next
Section titled “What happens next”An account change applies immediately: a blocked user is signed out of the ability to return, and a role change takes effect the next time they sign in. Inside the customer’s workspace, their own administrators see the same account under their user management and can undo anything done here.
Related
Section titled “Related”© 2025-2026 Humavera Documentation - BPilot Ltd. All Rights Reserved