Skip to main content

Role-Based Access Control (RBAC) - An Overview

With the Syntasa 9.1 release, user access management has been enhanced with a structured Role-Based Access Control (RBAC) model.

This update introduces:

  • Consolidated roles
  • Module-based access
  • Permission inheritance (create vs non-create)
  • Enhanced sharing and override capabilities

Prior to 9.1, Syntasa supported the following roles:

  • Syntasa Admin
  • Administrator
  • Composer
  • Synthesizer
  • Orchestrator
  • Dashboards Viewer

These roles were primarily function-based, where multiple roles often had intersecting responsibilities across the platform.

Updated Roles (9.1)​

In 9.1, roles have been restructured to provideclearer ownership and streamlined access management.

Unchanged Roles​

The following roles remain unchanged to maintain continuity for platform-level administration and dashboard access:

  • Syntasa Admin
  • Dashboards Viewer

Renamed / Consolidated Roles​

Several legacy roles have been merged into a single unified role to eliminate overlap and simplify role assignment:

  • Administrator → DataAI Admin
  • Composer → DataAI Admin
  • Synthesizer → DataAI Admin
  • Orchestrator → DataAI Admin

So, user can see following roles from 9.1 release:

  • System Admin
  • DataAI Admin
  • DataAI User
  • DonorAI Admin
  • DonorAI User
  • CCDP Admin
  • CCDP User
  • Audience Admin
  • Audience User
  • Dashboards Viewer
  • Dashboards User

Create vs Non-Create Access for Roles​

In Syntasa 9.1, roles are no longer limited to just module access. Each role also determines whether a user can create components (e.g., connections, apps, processes) or only view/use existing components.

This means:

  • Access to a module ≠ ability to create within that module

  • Create permissions areinherited as part of the role

  • Each role carries:

    • Access scope
    • Create capability (enabled or restricted)

Multiple Roles per User​

Syntasa allows assigning multiple roles to a single user, enabling flexible access across different modules. For example, a user can be assigned both CCDP Admin and Audience User roles. In this case, the user will have access to both the CCDP and Audience modules.

To see the list of each roles and its permission, please visit following article: