Space Management - Users, Roles & Permissions

Laura CARBO

13 October 2026 08:07

Summary

Space Management is designed primarily for administrators responsible for managing and maintaining your organisation's space portfolio. Access to the application is controlled through a role-based permission system — each user is assigned a role, and each role is granted a specific set of permissions that determine what they can see and do in the application.

note25210259panel_c1

Note:

Roles are created and managed in the Studio application, not within Space Management. Login to your Studio application or Contact your Studio administrator to create roles or assign them to users.

wide760

Note:

Roles are created and managed in the Studio application, not within Space Management. Login to your Studio application or Contact your Studio administrator to create roles or assign them to users.

How It Works

Roles and permissions work together as follows:

A Permission controls access to a specific action in the application — for example, the ability to add a building or edit a space type.
A Role is a named collection of permissions that you define based on the needs of your organisation.
A User is assigned one or more roles, which determines what they can access.

There are no default roles. Your Tenant Administrator creates roles from scratch in Studio and assigns the relevant permissions to each. This gives your organisation full flexibility to define access levels that match your team structure.

Example Role Configurations

The following are examples of how you might structure roles in your organisation. These are for guidance only — your organisation can define any roles with any combination of permissions.

Example Role	Typical Permissions Assigned
space.admin	All permissions — full access to configuration and space management.
space.editor	Space management permissions only — can add and edit locations but cannot change configuration settings.
space.viewer	View-only permissions — can browse Space Explorer and view layouts but cannot make any changes.

How Permissions Behave in the UI

If a user does not have a permission, the corresponding action or button is hidden in the UI — they will not see options they cannot use.
For pages that have both a read-only and an edit panel — such as location records — users without edit permission will see the read-only panel.
For pages that only have an edit panel — such as most Settings pages — the panel is shown with all controls disabled, making it clear that changes cannot be made.

Full Permissions Reference

The following tables list all available permissions, grouped by area.

Settings

Permission	What it does
`settings.view`	The Settings section is visible and accessible.
`settings.general.edit`	The user can edit and save General Settings.

Space Explorer

Permission	What it does
`space_explorer.view`	The Space Explorer is visible and accessible.

Location Types

Permission	What it does
`building_types.add`	The user can add Building Types.
`building_types.edit`	The user can edit Building Types.
`building_types.archive`	The user can archive Building Types.
`building_types.view.archived`	The user can view archived Building Types
`building_types.import`	The user can import Building Types.
`building_types.export`	The user can export Building Types to xlsx.
`space_types.add`	The user can add Space Types.
`space_types.edit`	The user can edit Space Types.
`space_types.archive`	The user can archive Space Types.
`space_types.view.archived`	The user can view archived Building Types.
`space_types.import`	The user can import Space Types.
`space_types.export`	The user can export Space Types to xlsx.
`subspace_types.add`	The user can add Subspace Types.
`subspace_types.edit`	The user can edit Subspace Types.
`subspace_types.archive`	The user can archive Subspace Types.
`subspace_types.view.archived`	The user can view archived Subspace Types.
`subspace_types.import`	The user can import Subspace Types.
`subspace_types.export`	The user can export Subspace Types to xlsx.
`terrain_types.add`	The user can add Terrain Types.
`terrain_types.edit`	The user can edit Terrain Types.
`terrain_types.archive`	The user can archive Terrain Types.
`terrain_types.view.archived`	The user can view archived Building Types.
`terrain_types.import`	The user can import Terrain Types.
`terrain_types.export`	The user can export Terrain Types to xlsx.
`subterrain_types.add`	The user can add Subterrain Types.
`subterrain_types.edit`	The user can edit Subterrain Types.
`subterrain_types.archive`	The user can archive Subterrain Types.
`subterrain_types.view.archived`	The user can view archived Subterrain Types.
`subterrain_types.import`	The user can import Subterrain Types.
`subterrain_types.export`	The user can export Subterrain Types to xlsx.

Allocation Types and Values

Permission	What it does
`allocation_types.add`	The user can add Allocation Types.
`allocation_types.edit`	The user can edit Allocation Types.
`allocation_types.archive`	The user can archive Allocation Types.
`allocation_types.view.archived`	The user can view archived Allocation Types.
`allocation_types.export`	The user can export Allocation Types to xlsx.
`allocation_values.add`	The user can add Allocation Values.
`allocation_values.edit`	The user can edit Allocation Values.
`allocation_values.archive`	The user can archive Allocation Values.
`allocation_values.view.archived`	The user can view archived Allocation Values.
`allocation_values.import`	The user can import Allocation Values.
`allocation_values.export`	The user can export Allocation Values to xlsx.

Custom Attributes

Permission	What it does
`attributes.add`	The user can add custom attributes.
`attributes.edit`	The user can edit custom attributes.
`attributes.archive`	The user can archive custom attributes.
`attributes.view.archived`	The user can view archived custom attributes.

Amenities

Permission	What it does
`amenities.add`	The user can add amenities.
`amenities.edit`	The user can edit amenities.
`amenities.delete`	The user can delete amenities.

Attachment Tags

Permission	What it does
`attachment_tags.add`	The user can add attachment tags.
`attachment_tags.edit`	The user can edit attachment tags.
`attachment_tags.delete`	The user can delete attachment tags.

Attachments

Permission	What it does
`attachments.add`	The user can add attachments.
`attachments.edit`	The user can edit attachments.
`attachments.delete`	The user can delete attachments.
`attachments.download`	The user can download attachments.
`attachments.tags.manage`	The user can manage tags on attachments.

Locations — Regions

Permission	What it does
`regions.add`	The user can add Regions.
`regions.edit`	The user can edit Regions.
`regions.archive`	The user can archive Regions and all child locations.
`regions.view.archived`	The user can view archived Regions.
`regions.import`	The user can import Regions.
`regions.export`	The user can export Regions to xlsx.
`regions.amenities.manage`	The user can manage Amenities for Regions.

Locations — Sites

Permission	What it does
`sites.add`	The user can add Sites.
`sites.edit`	The user can edit Sites.
`sites.archive`	The user can archive Sites and all child locations.
`sites.view.archived`	The user can view archived Sites.
`sites.import`	The user can import Sites.
`sites.export`	The user can export Sites to xlsx.
`sites.amenities.manage`	The user can manage Amenities for Sites.

Locations — Buildings

Permission	What it does
`buildings.add`	The user can add Buildings.
`buildings.edit`	The user can edit Buildings.
`buildings.archive`	The user can archive Buildings and all child locations.
`buildings.view.archived`	The user can view archived buildings.
`buildings.import`	The user can import Buildings.
`buildings.export`	The user can export Buildings to xlsx.
`buildings.amenities.manage`	The user can manage Amenities for Buildings.

Locations — Floors

Permission	What it does
`floors.add`	The user can add Floors.
`floors.edit`	The user can edit Floors.
`floors.archive`	The user can archive Floors and all child locations.
`floors.view.archived`	The user can view archived Floors
`floors.import`	The user can import Floors.
`floors.export`	The user can export Floors to xlsx.
`floors.amenities.manage`	The user can manage Amenities for Floors.

Locations — Spaces

Permission	What it does
`spaces.add`	The user can add Spaces.
`spaces.edit`	The user can edit Spaces.
`spaces.archive`	The user can archive Spaces and all child locations.
`spaces.view.archived`	The user can view archived Spaces
`spaces.import`	The user can import Spaces.
`spaces.export`	The user can export Spaces to xlsx.
`spaces.amenities.manage`	The user can manage Amenities for Spaces.
`spaces.allocations.manage`	The user can manage Allocations for Spaces.

Locations — Subspaces

Permission	What it does
`subspaces.add`	The user can add Subspaces.
`subspaces.edit`	The user can edit Subspaces.
`subspaces.archive`	The user can archive Subspaces.
`subspaces.view.archived`	The user can view archived Subspaces
`subspaces.import`	The user can import Subspaces.
`subspaces.export`	The user can export Subspaces to xlsx.
`subspaces.amenities.manage`	The user can manage Amenities for Subspaces.
`subspaces.allocations.manage`	The user can manage Allocations for Subspaces.

Locations — Terrains

Permission	What it does
`terrains.add`	The user can add Terrains.
`terrains.edit`	The user can edit Terrains.
`terrains.archive`	The user can archive Terrains and all child locations.
`terrains.view.archived`	The user can view archived Terrains
`terrains.import`	The user can import Terrains.
`terrains.export`	The user can export Terrains to xlsx.
`terrains.amenities.manage`	The user can manage Amenities for Terrains.

Locations — Subterrains

Permission	What it does
`subterrains.add`	The user can add Subterrains.
`subterrains.edit`	The user can edit Subterrains.
`subterrains.archive`	The user can archive Subterrains.
`subterrains.view.archived`	The user can view archived Subterrains
`subterrains.import`	The user can import Subterrains.
`subterrains.export`	The user can export Subterrains to xlsx.
`subterrains.amenities.manage`	The user can manage Amenities for Subterrains.

Locations — General

Permission	What it does
`locations.move`	The user can move a location from one parent to another.
`locations.duplicate`	The user can duplicate a location tree.

Drawings

Permission	What it does
`drawings.view`	The user can view Drawings.
`drawings.import`	The user can import Drawings.
`drawings.export`	The user can export Drawings.
`drawings.prepare`	The user can prepare Drawings.
`drawings.delete`	The user can delete Drawings.

Layouts

Permission	What it does
`layouts.add`	The user can add a Layout.
`layouts.edit`	The user can edit a Layout.
`layouts.explore`	The user can explore and view a Layout.
`layouts.activate`	The user can activate a Layout.
`layouts.archive`	The user can archive a Layout.
`layouts.view.archived`	The user can view an archived Layout. (i.e. seeing that it exists, without exploring it)