Contact support@responsive.io to access this feature or request enablement.
The Restricted Access feature strengthens security and protects data in projects shared across Business Units (BUs), making it so users from shared BUs get limited access only.
This means that invited users can perform their assigned actions only instead of being granted full access based on their role, so:
Users with an Admin role assigned to both the Primary Business Unit (PBU) and Secondary Business Unit (SBU) will have complete access to projects from both BUs. This is expected behavior as they have explicit access to both BUs.
Users with an Admin role assigned to only the PBU can gain unintended full access to a project or module from the SBU. This is a security risk as they inherit full access based on their role.
Restricted Access applies only when users gain project access through Module Level Sharing (project sharing), not through User Level Sharing (direct BU sharing).
Enabling Restricted Access prevents users from gaining full control over the module; they're only able to view and respond to assigned questions.
Sharing Level | Description | Access Level |
User Level Sharing | The user is explicitly granted access to a BU. | Full access based on role |
Module Level Sharing | The user is invited to collaborate on a specific project of a BU. | Restricted access to assigned questions only |
User | Primary Business Unit | Secondary Business Unit | Sharing Type | Role | Access Type |
John | InfoSec | Pre-Sales | User Level | Admin | Full Access |
Daniel | InfoSec | Module Level | Admin | Restricted Access |
Restricted Access limits users from shared BUs to:
They can't: