Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Global Permissions Table: TYPE_MODIFY & TYPE_DELETE entries were swapped

The Global Privilege management capabilities of the Syndeia Web Dashboard are presented on this page. After reviewing the details on this page, we highly recommend reviewing the General Recommendations for User Privileges page for guidance on Global and Digital Thread Project privileges needed for most Syndeia end-users.

Contents

Table of Contents
minLevel1
maxLevel6
outlinefalse
styledisc
typelist
printabletrue

...

Permission UI Name

Permission Value (used in API)

Description

CONTAINER: CREATE

CONTAINER_CREATE

Permission needed for creating new containers.

  • Required for creating new Digital Thread Projects (Containers).

  • Required for creating relations in Digital Thread Projects. Creation of new relations between artifacts in external repositories will need to persist artifacts and their parent containers in Syndeia.

CONTAINER:  DELETE

CONTAINER_DELETE

Permission needed for deleting containers.

CONTAINER:  MODIFY

CONTAINER_MODIFY

Permission needed for updating name and description of containers.

  • Required for updating name and description of Digital Thread Projects.

REPOSITORY: CREATE

REPOSITORY_CREATE

Permission needed for creating/adding new external repositories.

REPOSITORY:  DELETE

REPOSITORY_MODIFY

Permission needed for deleting external repositories. See Repository Deletion.

REPOSITORY:  MODIFY

REPOSITORY_DELETE

Permission needed for updating name and description of external repositories.

TYPE:  CREATE

TYPE_CREATE

Permission needed for creating types for repository, container, artifact or relation.

  • Required for creating relations in Digital Thread Projects. Creation of new relations between artifacts in external repositories will need to persist types of artifacts and their parent containers in Syndeia.

TYPE:  DELETE

TYPE_MODIFYDELETE

Permission needed for deleting types for repository, container, artifact or relation.

TYPE:  MODIFY

TYPE_DELETEMODIFY

Permission needed for modifying types for repository, container, artifact or relation.

USER:  CREATE

USER_CREATE

Permission needed for creating local users. See https://intercax.atlassian.net/wiki/spaces/SYN36/pages/3405053969.

USER:  MODIFY

USER_MODIFY

Permission needed for modifying/updating users.

USER:  READ

USER_READ

Permission needed for viewing the list and details of all users. See https://intercax.atlassian.net/wiki/spaces/SYN36/pages/3405053969. permission

USER:  REMOVE

USER_REMOVE

Permission needed for removing users.

ARTIFACT / RELATION: WRITE

ARTIFACT_RELATION_WRITE

Permission needed for authoring (adding, updating, deleting) artifacts and relations.

  • Required for authoring relations in Digital Thread Projects.

RESTFUL:  WRITE

RESTFUL_WRITE

Permission needed for authoring (creating, updating, deleting) collections and requests in RESTful repositories.

GRAPH:  QUERY

Status
colourPurple
titleNew in 3.6

GLOBAL_GRAPH_QUERY

Status
colourPurple
titleNew in 3.6

  • Permission needed for running global graph queries. See Global Graph Queries - Web Dashboard for details.

  • In earlier releases, all users were able to run global graph queries. With the introduction of Digital Thread Projects and User Privileges specific to Digital Thread Projects, users can run and manage graph queries in the context of their Digital Thread Projects. See Queries - Digital Thread Project.

  • (info) This permission provides an admin level capability to run graph queries across ALL Digital Thread Projects. As a result, this permission should ONLY be assigned to admins or advanced users who are overseeing ALL Digital Thread Projects on the given Syndeia Cloud deployment See General Recommendations for User Privileges to learn more.

ALL (except USER): READ

READ

Permission needed for accessing the basic capabilities of Syndeia.

  • This permission must be assigned to ALL active (enabled) users by default.

  • (warning) We do not recommend removing this permission directly via the API if any others are enabled.  

...