You can assign Security Roles to specific users in CloudRadial manually via Usage > Users. While assigning these manually can work, Partners often seek a faster way to assign and maintain assignment of appropriate permission levels to their users.
Type Mappings can help do this extremely efficiently.
Type Mappings use "type" fields within your connected PSA (or a custom-made "TypeMapping" field, described further below) to drive user permission assignment from the PSA. They allow you to control the user's type from within the PSA and have that be translated into a user in CloudRadial with an appropriate role assignment.
Overall, type mappings mean less management between systems and better overall control.
- How to Set Up Type Mappings
- About Type Mapping Capabilities
- Type Mapping Setup Instructions By PSA
- Type Mapping Rules
How to Set Up Type Mappings
To set up Type Mappings, you'll first need to create the rules.
- Navigate to Partner > Settings
- Select Type Mappings (under the Configuration column on the right-hand side)
- Select +Add Mapping at the top right to create a rule
About Type Mapping Capabilities
Type Mapping rules can be used in several use cases. Below, we describe each option and what it does:
PSA Contact Type
The "type" of the user set within the PSA. Case and spelling sensitive.
Log-in Options
- Sync with CloudRadial? - Choose whether to let them sync into CloudRadial, or not. If unchecked, this option will prevent this type of user from syncing into the portal entirely.
- Set as Priority User? - Will automatically flag this user as "priority". If you have your priority users defined, this will change the user's priorities upon ticket submission. More details here.
- Disable log in? - Makes it so users of this type will be synced into the portal BUT not allowed to log in. This is used for those who need to report on users but don't wish to give any access.
Role Assignment
-
Role - Sets the security/permission role of the user. Be sure to read and understand roles before applying type mappings to avoid giving users inappropriate permission levels.
- More about roles here: https://radials.io/SecurityRoles
Note: A role is not required; a partner may want to check 'Set as Priority User?' for 'VIP' users but want the role of the 'VIP' to be different between clients.
In this case, the 'role' for 'VIP' would be left blank and wouldn't change, but the users' priority could be updated.
Comments
0 comments
Article is closed for comments.