This article replaces a shorter version that described a single Role selection per mapping. You can now assign several roles to one type, and there are settings for ticket visibility and for what happens when a contact matches more than one type. Nothing you have already configured has changed or needs redoing, and all the per-PSA setup links are still at the bottom.
You can assign roles to users by hand in CloudRadial UCP, one user at a time. Type Mappings let you do it from your PSA instead: you set a contact's type in the PSA, and CloudRadial turns that type into portal access on the next sync. Change the type in the PSA, and the access follows.
That makes Type Mappings one of the highest-consequence settings you will touch. A mapping decides whether someone appears in the portal at all, what role they get, and which tickets they can see. This article covers every control on a mapping and what each one does.
- What a Type Mapping Decides
- Before You Start
- Creating a Type Mapping
- Sync Settings
- Role Assignments
- Remove From Other Role Assignments
- Advanced Settings: Ticket Visibility
- When a Contact Matches More Than One Type
- What Happens When a Contact's Type Changes
- Checking What a Mapping Actually Granted
- Setting Up Your PSA
What a Type Mapping Decides
One mapping can decide five separate things about a user:
| It decides | Control |
|---|---|
| Whether the contact syncs into the portal at all | Sync with CloudRadial? |
| Which roles the user is given | Role Assignment(s) |
| Whether the user's other role assignments are cleared | Remove from other role assignments? |
| Whether the user is flagged as a priority user, and whether they can log in | Set as Priority User?, Disable log in? |
| Which tickets the user can see | Advanced Settings |
Type Mappings are available for ConnectWise, Autotask, HaloPSA, Kaseya BMS and Syncro.
Before You Start
CloudRadial reads the type from a field in your PSA, and that field has to exist before a mapping can match anything. ConnectWise uses its native Contact Type; the other four PSAs use a custom field or UDF named TypeMapping that you create yourself. The Setting Up Your PSA links at the bottom cover that for each PSA - do that part first.
You also want to know what your roles grant before you attach them to a type. A mapping applies a role to everyone of that type across every client at once, so a role that is more permissive than you remember is a mistake that lands everywhere simultaneously. See Understanding Security Roles.
Creating a Type Mapping
- Go to Partner > Settings and select Type Mappings. (On the Settings page it is listed under Configuration on the right; once open, it is a tab beside Setup.)
- Select Add Mapping at the top right.
PSA Contact Type is the first field and it is the only one you must fill in. (Role Assignment(s) carries a required marker, but a mapping saves without a role; see below.) The value has to match the type in your PSA exactly, including capitalisation - Power User and power user are not the same type. Two things depend on it: whether a contact is included in the sync at all is decided by an exact match, so a value with different capitalisation can leave a contact out when another type they carry is switched off; once a mapping does match, its roles are applied without regard to capitalisation. Match the PSA's spelling exactly in every case. There is no picker here; you type the value, so it is worth copying it out of the PSA rather than retyping it.
Creating and editing mappings needs Edit permission on Partner Settings; deleting one needs Delete.
Sync Settings
Sync with CloudRadial? controls whether contacts of this type come into the portal at all. It is also the master switch for the rest of the mapping - with it unchecked, every other control on the mapping is disabled and the mapping grants nothing.
Leaving it unchecked is how you deliberately keep a class of contact out of the portal. Note what that does and does not do:
- A contact whose type matches only unsynced mappings is excluded from the sync.
- A contact whose type matches no mapping at all still syncs. Type Mappings are not an allow-list; an unmapped contact is not filtered out.
- If a contact carries several types and any one of them matches a synced mapping, the contact syncs.
Set as Priority User? flags the user as a priority user, which affects how their tickets are treated on submission.
Disable log in? brings the contact into the portal as a user but blocks them from signing in. This is for people you need to report on but do not want to give access to.
Both of these are re-asserted on every sync rather than merged with what is already there. If a user matches a mapping and that mapping does not set Priority, the sync clears Priority on that user - including if you set it by hand. The same applies to Disable log in. If you need a per-person exception to either, it cannot be maintained by hand on a contact whose type matches a mapping.
Role Assignments
Role Assignment(s) is a multi-select. A single type can carry several roles, and the user is given all of them.
A role is not required. You can create a mapping that only sets Priority, or only disables login, and leave the role list empty - the mapping then grants no role, and roles you assigned by hand are left alone. It does still handle roles that an earlier type mapping gave the user, as described in What Happens When a Contact's Type Changes: they are kept as Direct assignments by default, or removed if automatic revoke is on. Leaving the list empty is the usual way to handle a "VIP" type where the right role differs from client to client.
Roles that carry Partner-level permissions cannot be picked here. They are left out of the Role Assignment(s) list, because type mappings assign access within a client, not access to your partner portal. If an older mapping still lists one, it is skipped when the sync runs.
Roles granted this way are labelled as coming from the type mapping, not as roles someone assigned by hand. See Where a User's Roles Came From.
Remove From Other Role Assignments
Remove from other role assignments? turns the mapping from additive into exclusive. Instead of adding its roles to whatever the user already has, it clears the user's other role assignments for that client first, then applies its own.
The checkbox is only available once you have selected at least one role - an exclusive mapping with no roles would strip a user's access and give nothing back, so the product does not let you build one.
What it removes: role assignments scoped to the user's own company that were not granted through a group.
What it never removes:
- Partner-level roles
- Inherited roles
- Roles inherited from a user group (a legacy feature)
- Microsoft 365 group roles
Those four exemptions are exact. If a user keeps a role you expected this setting to strip, one of those four is why - check the Attribution column on the user to see which.
Advanced Settings: Ticket Visibility
Below the role controls there is an Advanced Settings section. It is collapsed by default, which is the main reason partners do not know it is there. Expand it and you get controls that decide which tickets a user of this type can see: Override Visible Tickets for this User? (the Visible Tickets choice of Personal, Site or Company only appears once you tick it), Ticket Status Overrides and Ticket Board Overrides. Board restrictions are honoured on ConnectWise, Autotask, Kaseya BMS and HaloPSA; on Syncro the control is shown but has no effect.
These interact with what the user's roles already grant, and the interaction is not "most permissive wins" - the override replaces the role-derived answer outright, so it can narrow access as well as widen it. That is enough of a trap to deserve its own article: see Controlling Ticket Visibility From a Type Mapping.
Like everything else on the mapping, these controls are disabled unless Sync with CloudRadial? is checked.
When a Contact Matches More Than One Type
Contacts can carry more than one type. In ConnectWise a contact can be tagged with several Contact Types natively - Billing, CEO, VIP. In Autotask, HaloPSA, Kaseya BMS and Syncro you get the same effect by putting a comma-separated list in the TypeMapping field, for example Billing,Power User. Values are trimmed, so Billing, Power User works too.
When more than one mapping matches, CloudRadial combines them in a single operation rather than applying them one after another. The rules:
- Only mappings with Sync with CloudRadial checked take part. A matched mapping with Sync unchecked contributes nothing - no roles, no priority, no ticket settings. It can still keep the contact out of the portal, but only if none of the contact's other matched mappings is synced.
- Roles are combined. The user gets every role from every matched synced mapping.
- If any matched mapping has Remove from other role assignments checked, it applies to the combined result. The user's other company-scoped role assignments are cleared first, then all the combined roles are applied together. The four exemptions above still hold.
- Priority and Disable log in are on if any matched mapping sets them, and off if none does.
- Ticket visibility takes the most permissive answer among the mappings that tick the override. If one matched mapping says Personal and another says Company, the user gets Company.
- Ticket status and board restrictions are combined into one list. A user matching two mappings with different board restrictions can see both sets of boards, not the overlap.
The practical consequence: adding a second type can narrow access as well as widen it. A second mapping that is exclusive can shrink the role list; one that ticks the override at Personal replaces the role-based ticket visibility; and one that sets a board or status list restricts a user who had no restriction before. Check the result on the user after you add a type.
What Happens When a Contact's Type Changes
When a contact's type changes in your PSA - or the type is cleared, or the contact stops matching any synced mapping - the roles that mapping gave them do not disappear by default.
Instead, those role assignments stay in place and are relabelled as Direct, as though an administrator had assigned them by hand. The user keeps the access until someone removes it deliberately. This is the default and it is the safe behaviour: a mistake in the PSA cannot quietly take away someone's access.
If you want the opposite - roles removed as soon as the type stops matching - there is a partner-level setting for it, off by default. It deletes role assignments, so read Automatically Revoking Roles When a PSA Type Changes before turning it on.
Checking What a Mapping Actually Granted
Type Mappings are applied by the PSA sync, not when you save the mapping. Nothing changes for existing users until the next sync runs.
To see the result on a specific person, open them under Partner > Clients > Users > [user] and look at the Role Assignments tab. The Attribution column tells you whether each role came from a type mapping, from a group, or from someone assigning it by hand. That is the fastest way to answer "why can this user see that?" - see Where a User's Roles Came From.
Setting Up Your PSA
Each PSA holds the type value differently. Start with yours:
Related
- Controlling Ticket Visibility From a Type Mapping - the Advanced Settings block, and how it overrides roles
- Where a User's Roles Came From - reading the Attribution column
- Automatically Revoking Roles When a PSA Type Changes - the default-off setting that deletes role assignments
- Understanding Security Roles - what you are actually granting
- Understanding the User Groups to Roles Migration
If you are still having trouble, we're here to help!
Submit a ticket here for assistance, and don't forget to check our status page to ensure there are no outages in your area.
Comments
0 comments
Article is closed for comments.