Type Mapping: Mapping PSA Types to CloudRadial Roles and User Groups

You can assign security roles and user groups to specific users in CloudRadial manually, typically 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 and user group allocation.

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
  
  • ConnectWise
  • Autotask
  • Syncro
  • Kaseya BMS
• Type Mapping Rules

How to Set Up Type Mappings

To set up Type Mappings, you'll first need to create the rules. To do so:

1. Navigate to Partner > Settings
2. Select Type Mappings (under the Configuration column on the right-hand column)
3. 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:

1. PSA Contact Type - The "type" of the user set within the PSA. Case and spelling sensitive.
   
   
2. 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 that need to report on users but don't wish to give any access. 
     
     
3. CloudRadial User Groups - The user group(s) that the type-mapped user will be placed into. If the user is already in user groups, they will be added to these groups in addition to any current group.
   
   
4. Remove from CloudRadial user groups? - Removes the type-mapped user from any user groups they're into and ensures they're only in the ones defined in option #3 above. 
   
   
5. 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. 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.

Type Mapping Setup Instructions By PSA

ConnectWise

• Click here to read the article on setting up Types in ConnectWise. 

Autotask 

• Click here to read the article on setting up the TypeMapping field in Autotask.

Syncro

• Click here to read the article on setting up the TypeMapping field in Syncro.

Kaseya BMS

• Click here to read the article on setting up the TypeMapping field in Kaseya BMS.

Halo

• Halo PSA does not currently support TypeMapping

Type Mapping Rules

1. All types and group names are case-sensitive
   
   
2. A user should only be tied to one Type Mapping rule in CloudRadial
   • If a user is tied to multiple Type Mapping rules, a few things are considered. If any rule denies access to CloudRadial, that rule will take precedence. If all applied rules allow syncing with CloudRadial, then the first rule alphabetically, will be applied. 
     • Example: A user is assigned both End User and Approver contact types in the PSA.
     • Similarly, there are two Type Mapping rules in CloudRadial for these two distinct user types.
     • In CloudRadial, the user will have only the Approver type mapping applied to them because it is alphabetically prioritized over End User.
3. Once a user is assigned to a group based on Type Mappings, the group will be automatically created if it doesn't exist.
   • Note that there are no ways to bulk remove these user groups - you must manually do so via Usage > Users > User Groups (tab) > Select > Delete group. 
     
   • This must be done for each individual company that had the user group added to it.
     
     
4. If you need to set CloudRadial access via Type Mappings without creating a new group, specify the Everyone group since it already exists and cannot be removed.
   
   
5. Assigning someone a security role that has admin permissions (such as Company Reporting) will automatically add them to the Admin user group.
6. You cannot use Type Mapping to assign a role that has Partner Level access for security reasons.

Use caution when specifying "disable login" via Type Mappings, as it is possible to lock your own account out. This occurs if your user profile exists within your PSA and is tagged with a certain user type, and that user type is being Type Mapped into CloudRadial with a disabled log in.

If this occurs, contact support by submitting a ticket and we can reset your login.