Grant elevated authority for a specific task
Powertech Authority Broker for IBM i is relevant when users need elevated authority temporarily rather than holding broad privileges throughout the day. Define the administrative task and its required rights before designing the approval. The project should distinguish the requester, the person authorising elevation and the person reviewing what occurred.
Map profiles, job functions and sensitive operations with IBM i administrators. Establish which existing access can be reduced after the new workflow is proven. Confirm the supported version and configuration before changing production authority, especially where older applications depend on profile behaviour.
Validate elevation, expiry and review
Use a non-production or otherwise approved task to test a permitted request, a denied request and the end of the authorised period. Check that the resulting evidence identifies the operator and the work performed sufficiently for the intended review. Emergency elevation needs its own criteria and subsequent review, not an informal route around the standard procedure.
Handover should include the authority mapping, approver responsibilities, exception record and recovery method if access is granted incorrectly. MMC can help scope the selected elevation workflows and knowledge transfer; the business retains ownership of decisions about who is entitled to privileged work.
Evidence to request for this scope
- Test an authorised elevated task and confirm the documented end of access.
- Verify that routine activity can continue under the intended lower-authority baseline.
- Retain the approval, operator identity and review procedure for normal and emergency elevation.