Roles help administrators control access to features and functionality in Sprinklr. By assigning roles, organizations can ensure users receive the permissions required to perform their responsibilities while maintaining security and governance.

​

Sprinklr supports two primary role categories:

• Global Roles
• Workspace Roles

1. Global Roles

Global Roles provide permissions across one or more workspaces.

When creating a Global Role, administrators can choose between Standard Roles and Custom Roles.

Standard Roles

Standard Roles are predefined role templates created and maintained by Sprinklr.

These roles:

• Represent common job functions and business use cases.
• Include recommended permissions.
• Cannot be edited or deleted.
• Can be cloned to create Custom Roles.

Custom Roles

Custom Roles allow organizations to configure permissions based on their business requirements.

Custom Roles:

• Can be created from scratch.
• Can be created from Standard Roles.
• Can be modified at any time.
• Can be assigned to users and user groups.

Global vs Local Scope

Global Roles support two scopes:

Global

The role applies across all workspaces.

Local

The role applies only to selected workspaces.

2. Workspace Roles

Workspace Roles apply only to a specific workspace.

These roles are typically used when:

• Access requirements differ between workspaces.
• Administrators need workspace-specific controls.
• Users perform different responsibilities across workspaces.

Workspace Roles do not include a Scope field because they are inherently workspace-specific.

Role Hierarchy

When multiple roles are assigned, Sprinklr applies permissions according to the following precedence:

1. Workspace Role - Applies only within a specific workspace.
2. Local Role - Applies only to selected workspaces.
3. Global Role - Applies across all workspaces when the scope is set to Global.

Workspace Roles override both Local Roles and Global Roles.

Local Roles override Global Roles.

If multiple applicable roles exist, permissions are combined wherever possible.

​

Role Summary During User Creation

When assigning roles to users, the Role Summary panel helps administrators understand what access will be granted.

The panel displays:

• Directly assigned roles
• Permission counts
• Applied permissions
• Overridden roles

The panel does not display roles inherited through user groups or dynamic user groups.

Package and Entitlement Considerations

A role may contain permissions that exceed a user's package, seat type, or add-on entitlements.

When this occurs:

• The role can still be assigned.
• A warning message is displayed.
• Restricted permissions appear in the Role Summary.
• Unavailable permissions appear grayed out.

This helps administrators understand why some permissions may not be available to a user after role assignment.