Hello,

In the Django admin I see that there are some groups:

   - graph editor
   - application administrator
   - crowdsource editor
   - etc.

And also many permissions:

   - models | node group | delete
   - models | node group | read
   - etc.
   
For example the Application Administrator group has just one permission: 
models | node group | read, while Graph Editor has also delete and 
create/update permissions.

This is what I have observed:

   - When I log into Arches with a user that is part of the Application 
   Administrator group it has access to all functionalities
   - While when I log in with a user that is part of the Graph Editor 
   group, though it has more permissions granted, I can do less things in 
   Arches
   - If I make a new group and I grant the same only permission that the 
   Application Administrator group has, I don't have the same functionalities 
   available when I log in.
   - If I make a new group and I grant the same permissions that the Graph 
   Editor group has, I don't have the same functionalities available when I 
   log in.

*Regarding all this, we don't understand the behavior of permissions in 
Arches - django.*
*I don't see a direction correlation between granting permissions and 
functionalities available in Arches.*
*Are we missing something? Did we miss some configuration?*
*Is there some documentation of what do all permissions mean? *

We are currently working in a project to implement Arches and we need to 
create very specific users with specific roles in order to satisfy the 
project needs.

Thank you!

Arnau

-- 
-- To post, send email to [email protected]. To unsubscribe, send 
email to [email protected]. For more information, 
visit https://groups.google.com/d/forum/archesproject?hl=en
--- 
You received this message because you are subscribed to the Google Groups 
"Arches Project" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to