New to JMP? Let the Data Analysis Director guide you through selecting an analysis task, an analysis goal, and a data type. Available now in the JMP Marketplace!
What inspired this wish list request?
This request is inspired by the cumulative burden of teams licensing JMP v19 on systems that are intentionally air-gapped, i.e. not connected to the internet. In the current offline activation workflow, JMP generates a ~70 character request code that is entered on the JMP website, which then returns a 700+ character response code that is hundreds of characters long and must be typed back into the offline machine. In highly restricted or air-gapped environments, transferring files onto a system can be extremely difficult or prohibited, making manual entry the only option. Typing long character codes is slow, error-prone, and often leads to failed activations even when the license itself is valid.
What is the improvement you would like to see?
I would like to see an option for simplified offline activation entry. Instead of requiring the full response code to be manually typed, JMP could accept a short verification code derived from the response (e.g. 6 characters from a cryptographic hash), while still validating the full response internally. To maintain security, JMP could limit the number of failed attempts and require contacting JMP support after repeated failures. This approach would preserve the existing licensing model while making the human interaction portion of the process far more manageable.
Why is this idea important?
This change would significantly improve usability for customers working in regulated or other environments where offline installation is common. It would reduce transcription errors, activation failures, and time spent retrying license entries, while also lowering support burden. Overall, it would make JMP more practical and user-friendly in real-world offline deployment scenarios without meaningfully weakening security.
... View more
What inspired this wish list request?
When adding users on then JMP authorization page, it is stated that users will be sent an email notifying them of access and providing download instructions. Newell Brands does not allow users to install software so this notification will cause confusion. We want users only to be notified that they have access and they can install JMP via Software Center.
What is the improvement you would like to see?
Add an option for users not to get a link to the software download when receiving notification that they have access to JMP.
Why is this idea important?
If download link is included, users will be confused and will most likely submit IT Service Requests instead of following company policy to install JMP via Software Center.
... View more
What inspired this wish list request?
User does not have access to prior version(s) of the JMP from their myJMP portal. It is limiting them as the latest version still has some unresolved issues.
What is the improvement you would like to see?
If the portal already has latest plus couple prior stable versions that will provide users the freedom and flexibility which could significantly enhance their autonomy and reduce their dependency on admins for such installations.
Why is this idea important?
... View more
With JMP 18, user management has become entirely manual, which is not sustainable. What plans are there for programmatic access, such as SSO or AD integration? We have an enterprise license, and the expectation that we need to manually add every user as they wish to leverage JMP Pro is not realistic. Presently, we can only either type in an e-mail address or upload a CSV.
... View more
What inspired this wish list request?
The myJMP portal currently lacks essential administrative capabilities required for managing users and licenses at scale. As an administrator, user provisioning must be performed manually because there is no support for Active Directory (AD) security group–based provisioning or SCIM integration. This makes onboarding, offboarding, and license management time-consuming, error-prone, and difficult to sustain as the user base grows.
Additionally, there is no visibility into actual JMP usage. Administrators cannot determine who is actively using JMP, as the portal does not provide basic analytics such as last login date or recent activity, despite JMP already validating licenses through myJMP.
Example use case: When an employee joins or leaves the organization, licenses must be manually assigned or revoked, and there is no reliable way to identify inactive users to reclaim licenses. This leads to inefficient license utilization and unnecessary administrative overhead.
What is the improvement you would like to see?
Automated user provisioning via:
Active Directory security group mapping
SCIM-based provisioning and deprovisioning
This would allow users to be automatically granted or removed access to JMP based on enterprise identity management policies.
User activity and license usage analytics, including:
Last login date per user
Active vs. inactive user indicators
Basic usage reporting within the myJMP admin portal
Comparable enterprise software platforms routinely provide these capabilities as standard administrative features.
Why is this idea important?
These improvements are critical for effective license governance, operational efficiency, and scalability. Manual license management is not sustainable in modern enterprise environments and directly results in productivity loss for support teams.
Providing automated provisioning and basic usage analytics would:
Reduce administrative overhead
Improve license utilization and cost control
Enable data-driven decisions around license allocation
Align JMP with current enterprise standards for automation and identity management
Without these capabilities, myJMP falls short of expected functionality for enterprise deployments, particularly in organizations that prioritize automation, efficiency, and AI-driven workflows.
... View more
