I changed a Maximo security group. Why does the user still have the old rights?

Maximo keeps each user’s security profile in server memory. In our lab, rights changes reached the user only after every session of that user had ended and the user logged in again.

Versions: On Maximo Application Suite 9.1 we confirmed, read-only, that the same group settings and the Manage Sessions action are present; the applications are listed there as “Security Groups (Manage)” and “Users (Manage)” (17 November 2026). The behaviour described here was tested in our lab on Maximo 7.6.1.0 (3 November 2026). We have not re-run it on Maximo Application Suite 9.1, where users sign in through the suite, so session behaviour may differ.

IBM’s page: IBM’s current Maximo Manage documentation says: “A security profile is the list of rights a user derives from the security groups to which the user belongs.” That page does not say when a change reaches a user who is signed in.

Last checked: 17 November 2026

How it works

The profile holds the user’s groups, sites, application options, storerooms, limits and tolerances. It is built when the user logs in, and in our lab it was rebuilt only when the user had no session left.

Change made while the user had a live sessionSeen by the user?
Added to a new groupNo
New application option in a group the user is inNo
New site in a group the user is inNo
Group flag changed (Independent of Other Groups, all storerooms)No
A second login while an older session was still liveNo, still the old profile
Users > Manage Sessions, flag the session for log-outNot within 5 minutes
All sessions ended (timed out after about 30 minutes idle), then a new loginYes, all changes at once

What we observed in our lab: a second login is not enough while an older session is still alive — including a REST client or a second browser. And data restriction edits on a group the user was already in took effect at once.

Steps

  1. Make the change in Security Groups (or in Users for group membership) and save. On Maximo Application Suite 9.1 these applications are listed as “Security Groups (Manage)” and “Users (Manage)”.
  2. Ask the user to sign out with the sign-out link, not just close the browser. Closing the browser leaves the session alive until it times out.
  3. If the user has more than one session (two browsers, a REST client, a mobile device), every one must end. Users > select the user > Manage Sessions shows them.
  4. The user logs in again. Check the result with the user’s own login, not with yours.

Where it breaks

How we checked it

On a Maximo 7.6.1.0 lab system we created a test user, a test person and three test groups. A test script read the user’s profile (groups, sites, options by site, storerooms, tolerances) after each change, while the user logged in through REST with its own password. We changed membership, options, sites and flags and watched when the profile changed. Everything we made was given a test marker and removed afterwards; we checked with read-only queries that nothing was left behind.

Not tested: the Security Groups screen path, the sign-out link, a server restart. On Maximo Application Suite 9.1 we only read the configuration; we did not create users or groups or test sessions there.

This page is part of our Maximo knowledge pages: answers we have checked on a real Maximo system in our lab. For questions about your own Maximo data, see Interpretos for Maximo.