HelioFleetDocs

Workspaces explained

Workspaces are how you slice a single tenant's device pool between different groups of people, without standing up multiple tenants. If your QA team and your dev team share the same HelioFleet account but shouldn't be staring at each other's devices, workspaces are the answer.

The model#

Three pieces fit together:

  • Tenant - your organization. Every device, user, and workspace belongs to exactly one tenant.
  • Workspace - an access group inside the tenant. Both devices and users get assigned to workspaces.
  • Membership - a user can be in any number of workspaces. A device can be in any number of workspaces. A non-admin user sees the union of devices across the workspaces they're a member of.

No nesting, no hierarchies - that's the whole concept.

Admins vs users#

The workspace model only applies to non-admin users:

  • Tenant admins bypass workspace filtering entirely. They see every workspace and every device in the tenant, regardless of assignment.
  • Tenant users are workspace-scoped. If they're not a member of a workspace, devices in that workspace are invisible to them on the Devices page and they can't open sessions on them.

Roles are covered in more detail on Roles & permissions.

Setting them up#

In the console, tenant admins manage workspaces from Admin → Workspaces:

  1. Create workspaces named after the teams or purposes they represent. A short description is optional but helps future-you remember what they're for.
  2. Assign devices to workspaces from Admin → Devices - each device has a row of workspace chips you can toggle on or off.
  3. Assign users to workspaces from Admin → Users - each user card has the same chip pattern. (See Inviting users for how to add a user in the first place.)

Changes take effect immediately. Users will see their device list update on the next refresh of the Devices page.

A few things to watch out for#

  • A device with no workspace assignment is invisible to every non-admin user, even one who's a member of every existing workspace. If you want non-admins to use a device, give it at least one workspace assignment.
  • Deleting a workspace doesn't delete its devices or users - only the assignments. Devices and users remain in the tenant and can be re-assigned.
  • Tenant admins always see everything, so a device with no workspaces is still reachable for them - useful for staging a device before you decide who should have access.