Improved SSO and SCIM Applications Experience
JumpCloud continues to improve the SSO Applications experience for prebuilt and custom SCIM connectors. This article covers the latest updates to attribute mapping, group management, and related application controls.
The new enhancements are:
- Customizable Attribute Mapping Tables:
- A list showing the required and optional SCIM user and group attributes is available immediately when creating a custom or prebuilt SCIM connector. Previously, all available user attributes were automatically transmitted and there was no visible list
- Using the new Edit function, admins can now add or selectively exclude specific optional attributes:
- The
managerattribute is now included in the list of optional user attributes - Group attributes can be used to define roles and licenses
- The
- After clicking Preview Mappings, the User Schema Preview window shows both user and group schemas
- Clicking the Save and Sync button initiates a complete sync of all users and groups after making a change to the attribute mapping table. Previously, admins had to wait for the next scheduled sync for the attribute mappings to update
- New Actions menu - the side information panel has been removed. For new applications, Actions can also add capabilities you did not select when you created the app.
- Linking Applications to AI Gateway - MCP connections from the application’s AI Gateway tab.
- Name override on User Groups and Agent Groups: Retain your JumpCloud group names for internal standards, and send the group name each application expects. For example, keep
eng-all-internalin JumpCloud and sendEngineeringto the app.
Click any image in this article to enlarge it.
Customizable Attribute Mapping Tables
Customizable User, User Group Attribute, Agent, and Agent Group Attribute Mapping tables are now available when creating SCIM application connectors. These capabilities apply to both pre-built and custom SCIM connectors, providing increased transparency and improved troubleshooting.
User Attribute Mapping
From your application's Provisioning tab, you can now customize SCIM user attribute mappings to shape user data before it is sent to the SP. The new functionality enables:
- See and Edit Default Mappings: View the default mapping set for any connector and modify them to fit your requirements
- Flexible Mapping Types: Mappings can be direct (e.g.,
firstname→name.givenName) or configured using expressions, constants, and booleans - Standard and Custom Attributes: Map JumpCloud standard attributes and custom user attributes to SCIM attributes
- Manager Attribute: Map the
managerattribute from the JumpCloud system user record to the SCIM managers object on the SP side. Use the manager'sDistinguished NameorEmailfrom JumpCloud to themanager.valueattribute in the SCIM schema, ensuring reporting hierarchies are maintained in the target application - Group Attributes: Admins can drive application-specific roles and licenses by using user group custom attributes or group membership ensuring users automatically receive the correct entitlements. It also allows mapping of the active status value providing more control over user activation and deactivation in the SP
- Schema Extensions: Support for mapping to SP custom schema extensions where available
- Granular Inclusion/Exclusion: Include or exclude specific attributes at a granular level (not just optional ones) while maintaining the ability to Restore Defaults at any time
| Old | New |
|---|---|
![]() | ![]() |
Clicking Edit above your SCIM connector's attribute table will bring you to Export Attribute Mappings page where you can add, edit, or delete your attribute mappings. You can also preview your mappings and restore the default mapping table.
You can only delete optional mappings.

It's highly recommended you use all optional mappings. This creates a more complete user profile, enabling better automation and more accurate access management within the application.
After adding your new mappings, click Preview Mappings. The User Schema Preview window will appear where you can check both User and Group schemas.

After confirming your mappings are correct, click:
- Save and Sync to initiate an immediate full sync of the updated attributes
- Update to initiate the update during the next modification of the user group's record, like a group name change or a membership change
User Group Attribute Mapping
JumpCloud now also supports Group Export Attribute Mapping for both prebuilt and custom SCIM connectors. Admins can configure how JumpCloud groups are named and structured when synced to downstream Service Providers (SPs), enabling alignment with app-specific naming conventions and complex schema requirements. The new functionality enables:
- Group display name mapping: In Group Export Attribute Mapping, control how the JumpCloud group name is sent as the application’s group
displayName. By default, JumpCloud mapsjcGroup.nametogroup.displayName. ThatdisplayNamemapping is required. You can control what the group name is by either using a custom attribute on the group, using an expression, or directly overriding specific group names in the User Groups and Agent Groups tabs. Mappings configured in the User Groups and Agent Groups tabs take precedence over mappings in the Attribute Mapping tables - Extended schema support — Map vendor-specific or custom attributes beyond
displayNameandmembers, including complex SCIM schema extensions - Mapping Preview — Use the Preview Mapping button to see a side-by-side view of how group data will be translated before syncing
- Enhanced Test Connection — Specify a test group and representative user to validate
/verifyand/activatesteps before enabling live sync - Directory Insights logging — All group translation rules generate audit events for full visibility into group provisioning activity.

End users are unaffected — group membership syncs automatically, ensuring downstream role assignments and permissions are applied reliably.
Name Override on Groups
Many apps require specific group names for roles, licenses, or access rules. JumpCloud groups often use stricter internal names for standards across your org. If you rename a JumpCloud group to match one app, you can break name-based expressions, disrupt shared naming used by other apps, and create cleanup work in places that still expect the original name. Name override lets you keep the JumpCloud group name and send the name each application expects. In the UI, this is the Show In App As field.
The Show In App As column appears on the User Groups and Agent Groups tabs when provisioning is active and group management is enabled. The override applies only to that application. The same JumpCloud group can have a different name override in each app, or none.
For example, keep eng-all-internal in JumpCloud, send Engineering to Slack, and send Eng to Zoom.
To configure a name override
- Go to Access > SSO Applications and open the application.
- Click the User Groups or Agent Groups tab.
- Find the group associated with the application.
- In the Show In App As field, enter the group name the application should use.
- Click Save to store the setting in JumpCloud without updating the application yet. Or click Save and sync to store the setting and update the group name in the application.
- To remove a name override, clear the field, then click Save or Save and sync.
- If you disconnect the group from the application, JumpCloud clears that app’s name override. If you associate the group again later, set the override again if you still need it.
- Save stores the name override in JumpCloud. The application group name updates on the next group change (name, mapped attributes, or membership), or when you use Save and sync.
- Save and sync stores the name override and starts a full sync of users and groups for the application.
- If Group Export Attribute Mapping and Show In App As both define a group display name for the same group, JumpCloud uses the Show In App As value when it syncs that group to the application.
Actions Menu
On the application details page, use the Actions menu for certificate and IdP key tasks that used to live in the side panel. Use the Manage User Provisioning (SCIM) or Manage MCP Servers menu options to enable the respective capabilities at any time. After you add a capability, its tab appears on the application.

Linking Applications to AI Gateway
Applications can route AI tool access through JumpCloud AI Gateway using an MCP (Model Context Protocol) connection.
When you open an application from Access > SSO Applications, linked MCP servers appear on the AI Gateway tab. From there, you can view linked servers and click + Add Server to continue setup in AI Gateway.
Not all applications support MCP servers. Confirm MCP support with the vendor or JumpCloud’s supported integrations list before you configure the server. See Configure AI Gateway Integrations.
See Get Started: SSO Applications and Get Started: AI Gateway to learn more.
Agent Groups
Agents are denied access to SSO applications by default. To grant access, open the application, select the Agent Groups tab, choose the agent groups that should have access, then click Save.
You can also assign applications from an agent group’s Applications tab. Direct agent-to-application assignment is not supported.
See Get Started: Agent Groups and Get Started: Agent Identities to learn more.
Was this information helpful?

