{% load i18n %}
{% blocktrans %}Arches allows you to define user and user group permissions on a per-nodegroup basis. For example, you may want to hide the coordinates of a Resource from the public, or allow a certain group of users to only update the condition assessment section of a Resource Model. Rules like these are all enforced using permissions.{% endblocktrans %}
Permissions Levels{% trans "Delete" %} | {% blocktrans %}Allows users to delete instances of this nodegroup. Note, this is not the same as being allowed to delete an entire resource, permissions for which are not handled here.{% endblocktrans %} |
{% trans "No Access" %} | {% blocktrans%}Disallows users from seeing or editing instances of this nodegroup. Use this permission level to hide sensitive data from non-authenticated users (the public).{% endblocktrans %} |
{% trans "Read" %} | {% trans "Allows users to see this nodegroup's card. If disallowed, the card/nodegroup will be hidden from the map and resource reports." %} |
{% trans "Create/Update" %} | {% blocktrans%}Allows users to create or edit instances of this nodegroup. This provides the ability to let users edit some information about a resource, while be restricted from editing other information.{% endblocktrans %} |
{% blocktrans %}You may notice that by default Arches comes with a "Guest" group, as well as user named "anonymous" who is a member of that group. Any non-authenticated user is treated as the "anonymous" user. This means that all permissions applied to the Guest group will be given to anyone who views the website without logging in.{% endblocktrans %}