How to implement access control on web
user-a have the following defect:
defect-d1
defect-d2
user-b have the following defect:
defect-d3
defect-d4
user-a can't access defect-d3 and defect-d4,user-b can't access defect-d1 and defect-d2
How to implement it?
I want to use elm workflow on public internet .
|
3 answers
Ralph Schoon (63.5k●3●36●46)
| answered Nov 28 '22, 2:51 a.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER 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 Thank you very much.
One sub team only have one user.
How would that scale? You would have to maintain many teams. You can play with it however. Access groups are also an option, but do not have built in automation. How would that scale? You would have to maintain many teams. You can play with it however. Access groups are also an option, but do not have built in automation. Same scalability concerns apply.
I want to use ELM workflow on public internet .
Many customers use the same ELM Workflow ,but a customer can't see other customer defects.
Please consider using comments on answers, instead of always writing more answers to your own question.
Creating a sub team for each client is what I have previously done. While there may be a single user in the sub team on the client side, you will also have internal team members assigned there as well so that they get notified of client changes etc.
There is some maintenance getting this set up initially but then it's pretty simple to keep going. Your top level categories will reflect the client name and that makes it very easy to see and manage work items across many clients or within a single client
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
|
Ralph Schoon (63.5k●3●36●46)
| answered Nov 30 '22, 7:20 a.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER edited Nov 30 '22, 7:44 a.m. I think we have answered what options you have already at least twice.
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.
|
Your answer
Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.