Page tree

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Next »



What is Role Based Access Control?

The Authoring Platform uses Role Based Access Control (RBAC) to authorise an authenticated user account with permissions to perform particular actions within the platform.

The current roles defined on the AP can be considered in three groups

Technical support and platform administration

  • ADMIN

Authoring and content promotion control

AUTHOR
PROJECT_MANAGER
PROJECT_LEAD

SNOMED CT release control

RELEASE_USER
RELEASE_MANAGER
RELEASE_LEAD
RELEASE_ADMIN

These roles are assigned to particular access control groups, which are mapped to global or project level content branch permissions on the Terminology Server. The technical support and platform administration, and SNOMED CT release control roles are outside the scope of this AP user guide, but mentioned here for completeness.

AUTHOR is the core permission which enables an authenticated account to work on SNOMED CT content through authoring projects and their related tasks.

PROJECT_MANAGER adds permissions to define Service Acceptance Criteria (SAC) which are used by Authoring Access Gateway (AAG) controls to grant (or deny) permissions for promotion of content at task and project level.

PROJECT_LEAD adds permissions to approve SAC items which allow project content promotion to the content mainline.

These roles also determine the visibility and presentation of access-controlled features in the AP user interface.

  • No labels