HelioFleetDocs

Inviting users

Tenant admins add new people to the tenant by sending an email invitation. The invitee picks their own password, lands inside your tenant, and shows up in the user list. You then assign them to the workspaces they should see.

Sending an invitation#

From the console:

  1. Open Admin → Users.
  2. Click Invite user in the top right.
  3. Enter the email address and pick a role - User for a workspace-scoped member, Admin for someone who should be able to manage the tenant. (Roles & permissions covers the difference.)
  4. Click Send invitation.

An invitation email is sent. The recipient gets a link, sets their own password, and is dropped straight into your tenant - no manual approval step on your side.

After sending, the console shows a confirmation dialog with the invitation URL. Copy link is your fallback if the email doesn't arrive - paste it to the invitee in whatever channel you normally use. The link is the same one in the email.

Pending invitations#

Until the invitee accepts, they appear in a Pending invitations section at the bottom of the Users list, tagged with their email, role, and expiry date. They are not yet a real user account, so you can't assign workspaces to a pending invite - workspace assignment becomes available the moment they accept.

If a pending invite expires before the user accepts, just send a new one.

After they accept#

Once the invitee picks a password and signs in for the first time, their user row materializes in the main Users list. From there:

  • Workspaces - each user card has a row of workspace chips. Click chips to toggle membership, then Apply to save. Admin users always show "All workspaces (admin)" instead - they're not workspace-filtered.
  • Role - set at invite time. Changing a user's role today means deleting them and re-inviting at the new role.
  • Search and filter - the toolbar at the top of the list filters by username/email and by role (all, admin, user).

Removing access#

Deleting a user from Admin → Users ends their active sessions immediately and revokes future access. The deletion is permanent - you can't undo it; you'd send a fresh invitation to bring them back.

Two users can't be deleted from the console:

  • Yourself - the delete button is hidden on your own row, to prevent locking yourself out of admin.
  • The seeded admin user - the original admin account created with the tenant is protected.

Common gotchas#

  • Invitation email didn't arrive - check the recipient's spam folder. If it's still missing, re-invite to get a fresh link and send it to them directly via Copy link.
  • User accepted but can't see any devices - they're a non-admin user with no workspace assignments yet. Assign them to at least one workspace; see Workspaces explained.
  • Wrong role - there's no in-place role flip yet. Delete the user and re-invite with the correct role.