All versions of this manual
X
Welcome to Linkurious administration manual v4.1.9. Use the menu to access other documentations.
  1. Introduction
  2. FAQ
  3. Getting started
    1. Version support policy
    2. Release notes
    3. Client requirements
    4. Graph DB Feature Map
  4. Deploying on premise
    1. Technical requirements
    2. Downloading
    3. Installing
    4. Starting Linkurious
    5. Stopping Linkurious
  5. Configuring
  6. Troubleshooting
    1. Checking Linkurious status
    2. Reading the logs
    3. Getting support
    4. Managing licenses
    5. Vulnerabilities
  7. Importing graph data
    1. Neo4j
    2. Memgraph
    3. Amazon Neptune
    4. Cosmos DB
    5. Updating your graph data
  8. Updating Linkurious
    1. Checking for updates
    2. Backing up your data
    3. Update procedure
  9. Configuring data-sources
    1. Neo4j
    2. Amazon Neptune
    3. Memgraph
    4. Cosmos DB
    5. Alternative IDs
    6. Merging data-sources
    7. Advanced settings
  10. Resource management
    1. Managing spaces
    2. Managing tags
  11. Search index
    1. Search Option Comparison
    2. Neo4j Search
    3. Elasticsearch
    4. OpenSearch for Amazon Neptune
    5. Azure Search
    6. Incremental Indexing
    7. Numerical/Date search
  12. User-data store
    1. Migrating to an external database
    2. Backing-up your store
  13. Web server
  14. Authentication
    1. Getting started
    2. LDAP / Active Directory
    3. SSO with Azure AD
    4. SSO with Google
    5. SSO with OpenID Connect
    6. SSO with SAML2 / ADFS
    7. Configuration
  15. Access control
    1. Managing users
    2. Managing groups
    3. Standard access-rights
    4. Property-key access-rights
  16. Guest mode
    1. Guest mode
  17. Data Schema
    1. Property types
    2. Hiding data
    3. Strict mode
  18. Alerts
    1. Configuration
  19. Email Notifications
    1. Configuration
  20. Visualizations appearance
    1. Default styles
    2. Default captions
    3. Default properties order
    4. Geographic tiles
  21. Audit trail
    1. Log format
  22. Webhooks
  23. Observability
  24. Plugins
  25. Deep link
 

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.

property-key-access-rights-switch

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.

property-key-access-rights-panel

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