Permissions: what do they do?
Gepland
Not all permissions an admin can give to a role are documented or self-explaining.
I have trouble understanding the permission-levels of "Relations & Diagrams" and "Worksets" for each objecttype.
What is the effect of changing "Worksets" from "Read-only" to "Read & Write" for objecttype "X"?
What is the effect of changing "Relations & Diagrams" from "Read-only" to "Read & Write" for objecttype "X"?
What I want to achieve is that the data in the repository can only be managed/altered by users with the specific knowledge (grouped in roles). I don't mind if all roles can see everything in the repository and use everything in their worksets.
-
Hi Ray,
Thanks for your feedback. I will take a look at the current documentation and rewrite it. When it's finished, I will let you know in this post.
0 -
Hi Ray Stapel
I will update the documentation later, but I will already give you some more information about permissions.
The difference between ‘Read-only’ and ‘Read & Write’ at the tab ‘view’ is the possibility to navigate to the views. With ‘Read & Write’, you can look at a the list of views and click on it so you can navigate to another view. ‘Read’ doesn’t give the possibility to navigate, so you can only take a look at the list of views.If you give someone the right to ‘Read & Write’ at the tab ‘diagram’ they can open the diagram, change the diagram, create a view of the diagram and add relations in the diagram. With 'read' you can open the diagram and create a view of the diagram. But you can not change the structure of the diagram or add relations.At the relation-tab, ‘Read & Write’ includes adding and deleting relations and change labels. With ‘Read’ you can only take a look at the relations.I hope this information is helpfull. If you need anything alse, please let us know in the comments!Happy holidays!0 -
Thnx.
0
U moet u aanmelden om een opmerking te plaatsen.
Opmerkingen
3 opmerkingen