Updates

Transfer Responsibilities — a new board permission

Apr 20, 2026
The Transfer Responsibilities permission shown in the board access settings

We've added a new board-level permission: Transfer Responsibilities . It makes it easy for responsible users to hand over their own responsibilities to someone else — without needing the Manage Settings permission.

Why this matters

Previously, only users with Manage Settings could assign or reassign responsibilities on a board. This meant that if a Fire Safety Officer was leaving a site and wanted to hand over the role to a colleague, an admin had to step in to make the change.

With the new Transfer Responsibilities permission, you can let responsible users reassign their own slots directly — no admin intervention needed. The permission is scoped to self-transfers only: a user can reassign responsibilities that are currently assigned to themselves, but cannot modify other people's assignments.

Perfect for SCIM-provisioned users

This is especially useful for organizations using SCIM provisioning (e.g., via Microsoft Entra). SCIM users are managed centrally, and their board access is often controlled through user groups. By granting the Transfer Responsibilities permission to a user group, you can empower all provisioned users to hand over their own responsibilities when they change roles or locations — keeping your responsibility matrix up to date without manual admin work.

How it works

  • Manage Settings — Can assign and unassign any responsibility, for any user
  • Transfer Responsibilities — Can only reassign responsibilities currently assigned to yourself
  • The permission is available on both compliance boards and insurance boards
  • It's included by default in the Admin access role

Getting started

Navigate to your board's access settings , find the user or group you want to empower, and toggle the Transfer Responsibilities permission. You can also use the Custom access role to combine it with other permissions.

You can read more about responsibilities in our docs here.