Invite and manage users

Open Organization → Org Structure → Users.

Access

• Read User shows the Users tab, list, and details.
• Create User shows Invite User.
• Update User permits profile, classification, organization, preference, identity, next-of-kin, and restriction changes. Without it, the section Edit actions are not shown.
• Export User shows the export action and permits user-detail PDF export.

Changing an existing user's role also requires Update Role. A user with Update User but without Update Role can edit the other classification values, but the role selector remains read-only. Data-access scope applies to the users that can be listed, opened, or changed; having an entity permission does not grant access to every tenant or every user record.

Users do not use maker-checker.

Before inviting a user

Create the user's branch, department or unit, and cost centre as needed. Create and review the role that will control Dashboard or Workbench access and entity actions.

Invite a user

1. Select Invite User.
2. Complete General, Organization, Security, and Next of Kin.
3. Review the summary and send the invitation.

General

Enter the user's sign-in email and full name, then select:

• User Type: Internal for staff, or External for a partner, agent, or contractor. Only L0 can create a System user.
• Data Access Scope: Organization, Branch, or Self. System users use System scope.
• Role: the permission and application-access bundle assigned to the user.

You can also record a private email, private phone, and primary identity document. Disposable sign-in email addresses are rejected, and the sign-in email domain must be able to receive mail.

Organization

Choose the language and primary branch. A branch is required for non-System users. Internal users also require a staff number. Optionally assign a department or unit, cost centre, and reporting user. The official work phone may be a shared Department or Unit number. Use Extension to identify the individual who uses that shared number.

Every selected organization record and role must belong to the same tenant as the user.

Security

For a Branch-scoped user, Accessible Branches defines the permitted branch set. If it is empty, remoteEaze falls back to the user's primary branch; it does not grant organization-wide access. The field does not narrow Organization or Self scope in the same way. See Data-access scope.

You can also configure non-working days, a working-hours start and end, and whether weekend or public-holiday access is allowed. Enter both working-hours values together, with the end later than the start.

Next of Kin

At least one next-of-kin entry is required for non-System users. Record the name, relationship, and phone number. Email, address, and identity details are optional.

What happens after invitation

remoteEaze creates the sign-in account, generates a password that satisfies the tenant policy, marks the email as verified, and sends the welcome email with the temporary credentials. The user must change the password at first sign-in. The temporary password is not returned by the production API.

The role controls whether the user enters the Dashboard, Workbench, or both. Read Dashboard and Workbench access before inviting field agents.

Manage a user

Open the user to review profile, classification, organization and work contact, restrictions, preferences, identity, next of kin, audit details, external IDs, and registered passkeys.

Use the section-level Edit actions to maintain the permitted values. A change to role, data-access scope, primary branch, or Accessible Branches revokes the user's existing sessions. A change affecting working-hours evaluation refreshes that policy; changes that also alter a security-sensitive assignment revoke sessions as well.

Access changes take effect immediately

Changing a Role, Data Access Scope, Primary Branch, or Accessible Branches can revoke sessions and remove access immediately. Confirm the complete access combination before saving.