Role and access restrictions on projects
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
4 hours ago
Hi all,
We are starting with the SPM module.
I have the following use case:
A user named Peter is the project manager for project A (full access).
He needs to be able to collaborate on project B (access to tasks with write permissions and, but without being able to modify general project information).
He needs to be able to view (read-only) project C.
Is this type of configuration possible natively? If so, how do I implement it?
If I grant Peter the "it_project_manager" permission, my user can modify all the projects he has access to.
Regards,
Karine
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
4 hours ago
Hi @Karine_M,
Yes, this type of configuration is possible natively, use the SPM‑specific roles plus ACLs to differentiate access across projects. Meaning use an ACL on pm_project to prevent Peter from editing Project B’s general information while still allowing him to edit tasks.
Hope this helps addressing your requirements...
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
an hour ago
Hi @fknell ,
Okay, so we need to create specific ACLs for each project?
So it's not natively possible to configure project editing only for the project manager it's attached to.
Ragards,
Karine
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
an hour ago
No, you should create a generic one, that sets the fields to read-only if the project manager is not the project manager associated with the project record.
