Skip to content
Innomesh Docs
Portal Since v3.3.0

RBAC Authorisation Guide

Overview

The Innomesh Role-Based Access Control (RBAC) system allows administrators to manage user permissions across the Portal and Room Manager environments through roles and user groups. Introduced in version 3.3.0, RBAC provides granular control over which features each user can access, ensuring that team members only see and interact with the areas relevant to their responsibilities.

How Access Works

A user’s access comes from their roles. Each role sets what the user can do (its permissions) and which rooms they can do it to (its scope). The scope works through two labels on each room: its user group and its site.

Boxes for User, Role, User Group, Room and Site, joined by arrows labelled with how many of each apply
A role decides what a user can do, and which rooms they can do it to
ItemWhat it isRule
UserA person who signs in to Innomesh. Users are added the first time they sign in.Needs at least one role, or has no access. Belongs to at most one user group.
User groupAn organisation, department or team.Groups users and rooms. Sets no permissions.
RoleA set of permissions plus a scope.Sets what a user can do, and to which rooms.
RoomA space managed in Innomesh.Has at most one user group and at most one site.
SiteA label for where a room belongs, typically a campus, department or regional office.Lets a role be limited to certain sites.

When a User Can See a Room

A user sees a room only when both of these are true:

  • The room’s user group is within the role’s User Group Resource Access.
  • The room’s site is within the role’s Site Access.

A room with no user group or no site is hidden from roles limited to specific user groups or sites.

For example, Company A builds rooms for Faculty A on a university campus:

  • Site: Faculty A is set up as a site.
  • User group: the rooms Company A builds are assigned to the Company A user group, and so are Company A’s staff.
  • Role: Company A’s staff have a role with User Group Resource Access set to Own user group, and Site Access set to Custom with only Faculty A selected.

Company A’s staff see only the rooms in Faculty A that Company A built, not the faculty’s other rooms or any rooms at other sites.

Scope applies to rooms across most of Portal and Room Manager, but some areas always show the whole tenancy. See What Site and User Group Access Covers.

⚠️ Warning
A user with more than one role gets every site, user group and permission from all of their roles combined. Each role’s permissions are not tied to that role’s scope. For example, a user with a view-only role for all sites and a full-access role for Faculty A has full access at every site.

Users

The Users section displays all registered users in your Innomesh tenancy. Administrators can view and edit user roles or assign groups to users from this page. User details include their SSO provider, account request date, and assigned roles.

Administration area showing the Users, User Groups, Roles, App Clients and Assistive UI Users tabs

To edit a user’s role or group:

  1. Navigate to Administration > Users.
  2. Locate the user in the list.
  3. Click the user row to open the edit panel.
  4. Select one or more Roles and, optionally, a User Group.
  5. Save the changes.

Role changes are enforced when the user next logs in.

📝 Note
If your organisation signs in through SAML, a SAML role can also assign roles and a user group, and these can take precedence over the ones set here. See SSO Integration using SAML2.

Users Management

Edit User dialog with the user group dropdown open

User Groups

User Groups categorise users by organisation, department, or specialisation. Groups serve an organisational purpose and are used for resource access scoping (see the General Tab section below), but they do not directly set permissions.

❗ Important
The User Group section is not the location to set permissions and access within your environment. Use the Roles section for access control.

To create a user group:

  1. Navigate to Administration > Users > User Groups.
  2. Click Add Group.
  3. Enter the group name and description.
  4. Save the group.

User Groups tab with the Create New and Delete buttons highlighted

Create User Group dialog with a name entered and the Create button highlighted

Roles

Roles define the specific access levels a user has across both Room Manager and Portal. Each role is configured through a set of tabs that control different aspects of the platform.

📝 Note
Avoid deleting the default Innomesh roles, as these support core organisational operations.

Roles tab listing built-in roles with the New Role button and row actions highlighted

Create Role dialog open on the General tab with a role name entered

General Tab

The General tab configures broad access parameters for the role:

SettingOptionsDescription
User Group Resource AccessAll, Own User Group, CustomControls which user groups’ resources the role can access. “Own User Group” restricts visibility to resources belonging to the user’s group. “Custom” allows selecting specific groups.
Site AccessAll, CustomRestricts the role to rooms at specific sites. Useful for teams who should only manage rooms on their campus or in their region.
Live Chat AccessYes, NoControls whether users with this role can access the live chat support feature.

Edit Role General tab with User Group Resource Access set to Own user group

User group picker for Custom User Group Resource Access

What Site and User Group Access Covers

Site Access and User Group Resource Access limit what a user sees in these areas:

  • The Hotlist, Rooms, Information and Assets pages in Innomesh Portal
  • Rooms in Innomesh Room Manager
  • meshIQ chat
  • Global Alert History, Q-SYS global views and the Microsoft Teams Rooms device list

These areas show the whole tenancy to anyone whose role grants access to them:

  • Vitals and Insights dashboards
  • The asset actions history (Assets > Actions)
  • The list of users an alert can be assigned to
  • Audit logs
  • Sight password management
  • Administration, including users, roles, user groups and App Clients
  • Data returned through the Platform API, the meshIQ MCP server and scheduled data exports, where App Client scopes limit the type of data rather than the site

A role with the Manage Roles permission can change any role or user group, so grant it only to administrators trusted with the whole tenancy.

Room Manager Tab

The Room Manager tab defines access to Room Manager features. Each access area supports the four permission levels described below.

Room Manager tab listing Administration, Rooms and Templates access areas

Administration Access

PermissionIncluded in “View Only”Description
Access AdministrationYesAdministration menu
Zones: view zonesYesView zones; download zones CSV
Zones: rotate hostsNoRotate hosts
Hosts: view hostsYesView hosts; download hosts CSV; launch host website
Hosts: manage hostsNoEnable Space VC host; disable Space VC host; drain Space CE host (future)
View logsYesView room manager logs only; view all logs (if ip-admin-logs also enabled)

Room Manager Administration Access custom permissions picker

Rooms Access

PermissionIncluded in “View Only”Description
View roomsYesView rooms (main Rooms tab); search, download rooms as CSV; view “Rooms Deployed” against template
Create & delete roomsNoCreate new Space/Sight/Pulse rooms; delete, duplicate, mass create, mass delete rooms
Edit room configurationNoEdit existing room; move rooms between zones; update room software; upgrade Pulse to Sight; load room from file; update XPanel, VNC, web panel; pull/push template updates
Edit room informationNoEdit room information
Expose all room optionsNoExpose all room options (for Space CE rooms)
Launch remote UI panelYesLaunch XPanel, VNC, Web Panel
Create & delete third-party roomsNoCreate or delete third-party room
Edit third-party room configurationsNoEdit third-party room; move between zones; update XPanel
Mass onboard UC roomsNoMass create Sight rooms for UC management (Microsoft Teams)

Rooms Access custom permissions picker for a role

Templates Access

PermissionIncluded in “View Only”Description
View templatesYesView templates; download as CSV; view template via “Template Name” link
Create & delete templatesNoCreate, delete, duplicate, or mass delete templates
Edit template configurationNoEdit existing template; update software, XPanel, VNC, web panel; load from file; room state mapping (Sight templates)
Edit information template associationNoUpdate information template
Edit template room optionsNoUpdate room options
Create & delete third-party TemplateNoCreate or delete third-party template
Edit third-party template configurationsNoEdit third-party template; move between zones; update XPanel

Templates Access custom permissions picker for a role

Portal Tab

The Portal tab defines access to Portal features. Each access area supports the same four permission levels described in Permission Levels. The most commonly configured areas are detailed below; the tab also includes Filtered Views and Integrations Management access areas, which follow the same All / View Only / None / Customise model.

Portal tab listing Filtered Views, Hotlist, Vitals, Room Management, Room Information, Insights, Asset Management, Integrations Management, and Administration access areas

Hotlist Access

PermissionIncluded in “View Only”Description
View HotlistYesView, search, filter, sort Hotlist; group by room
View “Critical” severity alertsYesCritical alerts in the unified alert list
View “High” severity alertsYesHigh alerts in the unified alert list
View “Medium” severity alertsYesMedium alerts in the unified alert list
View “Low” severity alertsYesLow alerts in the unified alert list
View “Notice” severity alertsYesNotice alerts in the unified alert list
View “Suppressed” severity alertsYesSuppressed alerts tab
Claim alertsNoClaim, mass claim, update alerts; add alert notes (including mass)
Manage alertsNoAssign, mass assign, create ticket, resolve, mass resolve (future), set non-SLA, suppress; manage suppression rules; view alert history

Hotlist Access custom permissions picker for a role

Vitals Dashboard Access

PermissionIncluded in “View Only”Description
View Vitals Infrastructure dashboardYesInfrastructure dashboard
View Vitals Rooms dashboardYesRooms dashboard
View Vitals Network dashboardYesNetwork dashboard
View Vitals Pulse dashboardYesPulse dashboard
View Vitals Sight dashboardYesSight dashboard
View Vitals Compliance dashboardYesCompliance dashboard
View Vitals VNOC dashboardYesVNOC dashboard
View Vitals Custom dashboardYesCustom dashboard

Vitals Dashboard Access custom permissions picker for a role

Room Management Access

PermissionIncluded in “View Only”Description
View roomsYesView Rooms page, Live Info, Insights; sort, filter; “Show Room” link from Assets
Manage roomsNoSet Maintenance; trigger room operations
Launch remote UI panelNoLaunch XPanel, VNC, Web Panel

Room Management Access custom permissions picker for a role

Room Information Access

PermissionIncluded in “View Only”Description
View room informationYesView, search, sort Room Information; download CSV
Edit room informationNoToggle edit mode and mass edit mode; save or discard edits

Room Information Access custom permissions picker for a role

Insights Dashboard Access

PermissionIncluded in “View Only”Description
View “Rooms” dashboardYesRooms dashboard
View “Usage” dashboardYesUsage dashboard
View “Alerts” dashboardYesAlerts dashboard
View “Proactive Support” dashboardYesProactive Support dashboard
View “Consumption” dashboardYesConsumption dashboard
View “Sight” dashboardYesSight dashboard
View “Ops” dashboardYesOps dashboard
View “Custom” dashboardYesCustom dashboard

Insights Dashboard Access custom permissions picker for a role

Asset Management Access

PermissionIncluded in “View Only”Description
View assetsYesView Assets page, asset details, live info; sort, filter, customise view; download CSV; view room assets and Hotlist alert asset
Manage assetsNoEdit asset details
Perform asset operationsNoTrigger asset operations (including mass); filter by operations

Asset Management Access custom permissions picker for a role

Administration Access

PermissionIncluded in “View Only”Description
Access administrationYesAdministration menu
Trigger “Change Mode”NoChange Mode page access and trigger
Manage assets & asset profilesNoAsset profiles; driver, compliance, and custom fields management; asset operations update and file management; operations schedule (future); campaigns (future)
View logsYesView room manager logs only; view all logs (if ip-admin-logs also enabled)
Manage UsersNoUpdate or delete user
Manage RolesNoCreate, update, or delete role, user group, or SAML role
Manage Smart Room AttributesNoManage Smart Room Attributes
View data import / export configurationsYesView data import and export configurations
Edit data import / export configurationsNoCreate, edit, duplicate, or delete data import and export configurations
Manage Summary ViewsNoCreate, edit, duplicate, or delete Summary Views

Portal Administration Access custom permissions picker for a role

Permission Levels

Each access area within a role offers four permission levels:

LevelDescription
AllFull access to all functions within the area
View OnlyRead-only access; the user can see data but cannot make changes
NoneNo access; the section is hidden from the user
CustomiseSelect specific individual permissions within the area

When Customise is selected, a list of granular permissions appears. Toggle each permission on or off to tailor access to the exact requirements of the role.

App Clients

The App Clients tab under Administration > Users is where you manage the credentials that external systems use to authenticate to the Innomesh Platform API. Each App Client has its own permission scopes, which control the API endpoint families it can reach, independently of the user roles described above.

App Client creation, permission scopes, and management are covered in full in the Innomesh Platform API article.

Assistive UI Users

The Assistive UI Users tab under Administration > Users controls which users may use the Assistive UI application and which rooms each of them can access. See Assistive UI Users for details.

Best Practices

  • Start with the default roles and create copies for customisation rather than modifying the originals.
  • Use User Group Resource Access to scope data visibility. For example, a regional operations team should only see rooms belonging to their user group.
  • Apply the principle of least privilege by granting only the permissions each role requires.
  • Review roles periodically to ensure they still align with team responsibilities, especially after organisational changes.
  • Document custom roles internally so that new administrators understand the purpose of each role and its intended audience.