ERM and "Teams" organization
My ERM version is 7.0.3 iFix020
I'm testing a "Teams"-based organization within ERM (Requirements Management).
I created a folder containing artifacts and assigned it to my test team.
I've noticed that a user assigned to the test team cannot:
- create or issue a Changeset
- accept or issue Changesets
- create a baseline
This isn't ideal, but it makes me wonder about the benefits of a "Teams"-based organization.
My questions are:
- Have you ever implemented a "Teams"-based organization within ERM?
- If so, in what use case?
- Do you have any best practices on this topic?
Thank you in advance for your advice.
One answer
Permissions are influenced by the Team structure so, if you have added a person to the Team then their permissions for folders owned by that team are controlled by the Role you assign them within that Team.
Some actions, however, are Project Area level actions, so they are controlled by their Role at Project Area level. Things like modifying project dashboards, creating shared views, and creating baselines are all project level.
So, if you want people within a team to be able to do project level actions, you need to add them to the top level project area and assign a role that controls their project wide permissions