A planning card to design per-user truck and storeroom scope on paper before anyone touches a screen. Decide the six things that make the scope hold up in production. Applies to MAS 8.x, 9.0, and 9.1.
This card gets your per-user storeroom scope designed before the build. It does not write the scope. It makes sure you have decided the six things that determine whether the scope holds up: the ownership attribute that ties a tech to a storeroom, the objects and views in scope, the broad groups that could defeat it, the supervisor pattern, and the test users who prove it.
You need one field that ties a tech to their assigned storeroom, and Maximo has no native assigned-truck field, so this is a real choice. The field I recommend is the Inventory Owner on the storeroom record, LOCATIONS.INVOWNER. You put the person on the storeroom rather than the storeroom on the person. It already exists on every storeroom and references the person ID directly. Whatever you pick has to be populated for every scoped user, because a blank value scopes them to nothing.
No email, no signup. The section that catches people is the broad-groups inventory, because a scope you built perfectly is defeated by one broad group you forgot the user was in. Test the full effective profile, every group the user is in, not the scoped group on its own.
This card plans the scope. Writing the conditions object by object, attaching the restrictions, and building the supervisor pattern is the AppPoints and Security Groups Workshop and Playbook.