Permissions

Permissions enable users to view different data and content in Salted CX and perform actions. Salted CX has granular permissions that give individual users the level of access they need.

By default, a user logged to Salted CX using an Identity Provider has no permissions and cannot access any part of the application. To enable users to access Salted CX you have to explicitly add permissions in the identity provider.

Always give users the minimum level of access they need to do their job efficiently. We recommend identifying just a few combinations of permissions you will be giving your users so it is fairly consistent across your company. We have tried to put some common combinations of permissions into Permission Sets.

Scope

Scope defines to what metadata, content, and objects the permissions apply.

Permissions List

Each permission has a scope. Supported scopes depend on the permission.

Permission Sets

To simplify permission management we also provide permission sets that group multiple permissions under one common named item. By convention, the permission sets are in capital letters.

One user can have multiple permission sets and also have additional permissions that expand their permissions. Users can view and perform all actions listed in any permission set they have attached or in any individual permission.

Permissions sets are managed by Salted CX and we may add more permissions to give users access to features suitable for the given roles. If you need to be really strict with access to individual features of Salted CX do not use permission sets but always list individual permissions.

The following matrix contains what permissions are enabled for each permission set.

Permissions Definition

You define permissions for individual users in a JSON object that you edit in your Identity Provider. Each user that should have access to Salted CX has to have the permission definition in stored in their attribute.

The example permission definition below uses just one permission set without version. User with this permission will able to perform tasks that we consider suitable for agents including getting new features.

{
	"sets": ["ALL"]
}

The example permission definition below uses combination of 2 roles and individual permissions. This enables to empower Team Leaders with all AI features available and also gives them permission to review engagements.

{
	"sets": ["TEAM_LEADER", "AI"],
	"review.view": "*",
	"review.edit": "*"
}

If the permission definition is not in a valid format the user has no access to Salted CX. Issues include invalid JSON structure, unknown permission set name, unknown permission name, values are not of the expected type and unsupported scope for a permission.

The limit for permissions is 2048 characters (including spaces, new lines and other empty characters). For this reason Salted CX enables you to specify permissions in a short way using permissions sets. If the length of the permissions exceeds the 2048 characters and thus the permissions are not in valid JSON format Salted CX ignores the permissions and the given user has no access to Salted CX.

Setting Permissions

Permissions are evaluated during login as they are passed to Salted CX from an identity provider. Users have to logout and login to have updated permissions.

User permissions are passed to Salted CX from identity providers in custom user attributes. Claim is a key-value pair associated with the user. Claims can be used to provide additional attributes that might be useful for applications such as Salted CX.

To give users access to Salted CX you need to provide value in cxsaltedpermissions in the JSON format that Salted CX expects. How the value is set depends on your identity provider.