Control for Scope Module Access by User Role
C
Craig Walker
Ability to toggle access to the Scope module on or off for specific user roles within the Custom Roles & Permission Settings. This would allow project admins to limit visibility or editing rights within the Scope module based on a user’s assigned role — supporting more secure and tailored collaboration across teams.
Created by Louie Moran
Clive Jordan
Craig Walker Hey Craig, as part of the new Work Package features, we're also adding some new powerful Scope permissions features too
We're adding four new permission options:
- Manage work packages:This controls the ability to manage work packages.
- Create and delete tasks:This controls whether team members can create and delete tasks.
- Task/Work Package visibility:This controls whether team members can see certain tasks and, therefore, work packages. There will be three options:
* See all tasks.
* See assigned and yet-to-be-assigned tasks.
* See only assigned tasks (tasks assigned to their team).
- Edit scope tasks:This controls the permission to edit scope tasks, with these options:
* Edit all scope tasks.
* Edit assigned (to my team) and yet-to-be-assigned tasks.
* Edit only tasks assigned to my team.
* No edit access. Users might have access to the scope but not be able to edit any tasks.
I'm explaining these new scope permission features in detail here to get your feedback on whether they would be useful for you based on this request to hide the Scope completely.
We will certainly add this permission to hide the Scope completely, but I'm also interested in your views on these other permissions features and if you've seen the details about new Work Packages that we've been sharing in the BIM Summer Camp? Do you think these features might complement what you're trying to achieve?
Thanks!