User group segregation in PPM

[Ahsan Kalyar]

Hi All, 

I am trying to onboard an external user group to our PPM system. This group will create and view their own projects and related items like risks, issues, change requests, financials, etc. I want to ensure that this external group cannot access our internal projects, and vice versa.

What is the best way to grant access to this external group? Should I use OBS, partitions, blueprints, or another method?

Here's what I've done so far:

1. Created a sub-partition in the system partition for the external group, giving them access to all the attributes our team has.
2. Developed a separate project creation template for the external group.
3. Created an individual blueprint for the modern/new user experience interface.
4. Granted access to projects using groups at the instance level.

Considerations:

1. The external group will need one admin account to create new projects and manage access for their team.
2. We use both the classical and new user experience interfaces of PPM, but the external group will only have access to the new user experience interface. 

[Nika Hadzhikidi]

Hi Ahsan,

Partitions are not used in MUX(Modern User Experience) so their use is not recommended, I would skip this step in your setup entirely. 

You can use OBS permissions for the projects and separate blueprints for the different group. You can create a Group and assign the specific OBS permission to it. This way each Group will only have access to see their own projects by OBS, including both Classic and MUX

In MUX you can also leverage Field Level Security (FLS) for some of your attributes visibility by access right, provided you are on a later version. 

You can also look into MUX Blueprint Rules (see documentation here)

Hope this helps -Nika

------------------------------
Nika Hadzhikidi
Sr Principal Support Engineer
Broadcom
------------------------------