Access control: Property-key access-rights

Enabling Property-key access rights

• In order to switch Property-key access rights, a strict schema is required.
• The Property-key access rights can switched on/off from the top-right corner of the Users & Groups page.
• Property-key access rights can be applied only to custom groups.

Defining property-key access rights

To define property-key access rights, the administrator needs to create (or edit) a custom group: after the access-rights configuration page, with the property-key access rights feature switched on, a second panel will be displayed.

From here:

• For each node category (resp. edge type), the administrator is able to set one of the following access-rights (exactly the same as for Standard access rights):

  • NONE: The user can't access (search or display) nodes (resp. edges) of that category (rest. type).
  • READ: The user can search display nodes (rest.edges) of that category (resp. type).
  • EDIT: The user can edit properties of nodes (rest. edges) of that category (resp. type).
  • CREATE AND DELETE: The user can:
    • Create new nodes of that category (resp. edges of that type).
    • Delete nodes of that category (resp. edges of that type).
    • Add or remove that category from existing nodes of that category (resp. edges of that type).

• For each property the administrator is able to set one of the following access rights:

  • NO ACCESS: neither the property nor its value can be seen by this user group.
  • READ: the property value is displayed to this user group but cannot be edited.
  • EDIT: the property value is dipsplayed to this user and can be edited.

• Access rights are cumulative (see example below).

Example

• User Foo belong to the groups Accounting and Sales
• Group Accounting has:
  • READ access right on node-category COMPANY
  • READ access right on the property address of the category COMPANY
• Group Sales has:
  • EDIT access right on node-category COMPANY
  • NO ACCESS access right on the property address of the category COMPANY

As a result, user Foo has:

• EDIT access right on node-category COMPANY
• READ access right on the property address of the category COMPANY