Hi,
As for projects, it would be great to restrict products visibility to people who are working on it.
Yet, anybody who grants access to configuration menu will be able to read all détails of all products.
What we expect is to restrict access to products to the only people / resources that are affected to.
So, is it possible to :
1) create an affectation to products
2) make resources affectable to products / versions
3) create rights in a good way
So, a user / resource that is not affected to a product will not be able to see it.
Regards,
Hi,
This is a very complex evolution.
All access rights are project bases, and the habilitation module is quite complexe.
This would add even more compexity...
Ticket #5147 recorded, low priority.
Hi,
Thanks for answering.
May be would it be simplier if products / versions could be linked to projects (one or many) and inheritate rights from projects ?
May be would it be simplier if products / versions could be linked to projects (one or many) and inheritate rights from projects ?
It is indirectly the case.
List of products are limited to products having a version linked to the project.
Possibly restriction could be extended.
Yes you're right, it is the case in lists and menus.
But in Configuration / Product Screen, all products are shown, no matter of user rights on projects, right ?
But in Configuration / Product Screen, all products are shown, no matter of user rights on projects, right ?
Well, I guess it should be, and I think it used to behave this way.
Possibly there was a change when changing access rights management for non project dependant items.
We'll have a look. Ticket #5156 recorded