What inspired this wish list request?
We have 50 authorized users but I have no way to know all these users are actually really using the tool. I just have to trust their word that they are. And before we buy additional licenses it would be very useful to know if all these 50 licenses are actually used.
What is the improvement you would like to see?
Having a list of all the authorized users checking out a license every week for instance would be a good start. That way if we see that one user has not checked out any license in a given week, we can discuss it with them to get a sense of whether they really need to be authorized users. I suppose today the only way to find out would be to remove all authorized users and wait for them to complain but this is a rather frustrating way of doing things and you would have to do it every few months to account for users who have moved to different roles and are not using the tool anymore.
Why is this idea important?
Better license management. This kind of feature is very common with tools using flexlm with which you can know at any time how many licenses are used and who is using them, which makes it very easy for license administrators. With JMP you are entirely working in dark and you might end up buying licenses that are not used at all.
... View more
What inspired this wish list request?
Users are currently receiving an email from JMP after they are adding the MyJMP portal which is causing confusion because JMP 19 is automatically installed for our users through our internal processes.
What is the improvement you would like to see?
Need the functionality to disable sending user(s) email once they are added to MyJMP portal.
Why is this idea important?
... View more
What inspired this wish list request? Managing jmp licenses can be tedious if we have a lot of licenses and employees resign or arrive. Corporate user management systems (like Active Directory or other SSOs) always need to be up to date, so if we can have an API to add or remove users on my.jmp.com, that would be very useful.
What is the improvement you would like to see? All actions that we can do manually in the my.jmp.com console should be possible with API and be documented.
Why is this idea important? Manage jmp automatically and not manually.
... View more
What inspired this wish list request? I'm in charge of the management of the JMP Contract and with JMP18, the management of users had drastically been modified.
What is the improvement you would like to see? To improve the management of the list of authorize users for my company, I'd like to get an history of the JMP18 licence access. I mean the last date of JMP18 connexion and the history for each user.
Why is this idea important? Ease to manage the list of users authorized to use JMP and JMP renewal.
... View more
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
