How to implement access control on web
3 answers
To my knowledge, EWM does not provide a user based permission mechanism as suggested above.
Here are some links to what EWM can do: https://jazz.net/library/article/554
I have written up, what mechanisms there are and how to provide more automation here: https://rsjazz.wordpress.com/2016/01/27/manage-access-control-permissions-for-work-items-and-versionables/
Comments
showing 5 of 6
show 1 more comments
As Ralph mentioned, you can't control visibility on a user basis - it's done on a team basis.
Set up sub teams, create a set of categories, and then map a sub team to the categories. Then on each category you can:
- "Restrict Category Visibility", which hides the Category from all but members of the associated Team
- "Restrict Work Item Access", which hides Work Items assigned to this Category from all but members of the associated Team
- "Use As Default", which makes the Category the one selected by default when a user in that sub team creates a new Work Item
I think we have answered what options you have already at least twice.
- You can set up category based restricted access and manage the members of the teams that can see the shared work items in team areas associated with the category. Teams can have one or more members. See the links above. Note that users not member of such a team can not see the work items filed against that team.
- You can manage access groups where each access group has one or more members (including project or team areas). You can set the restricted access of each work item to an access group and only the members of that access group can see the work item. There is no automation for this, but it would be possible to write a follow up action to automate this. See my blog links for how that would work. The amount of access groups might be limited, but I know a customer who is using this for at least SCM access.
I will stay with my comment: access management, where only one person has access is pointless and EWM is not designed for this. EWM is designed to share to be able to work together. There are capabilities to limit access to team areas or access groups for more fine grained control.