Reconcile identity changes with IBM i access
Powertech Identity Manager for IBM i is an identity-lifecycle enquiry. Begin with the authoritative source of a person’s status and the IBM i access that should change when they join, move or leave. A reliable workflow needs business ownership of entitlement, not merely a technical connection between directories.
Inventory profiles, roles, target systems and manual provisioning steps. Confirm supported integrations and how the selected product handles conflicting or incomplete identity information. Service and shared accounts require explicit ownership because they may not follow the lifecycle of an individual employee.
Prove joiner, mover and leaver outcomes
A pilot should create a controlled test identity, change its role and remove its authorised access. Check the actual resulting state on the IBM i target, not only a successful workflow message. Record reconciliation failures and the manual route for correcting them safely.
Handover should identify approved mappings, target permissions, exception owners and the audit evidence retained for access decisions. For multi-entity UAE groups, establish whether identity attributes or approvals differ between legal entities or business units. MMC can scope the selected mappings and deployment; periodic access certification and the legal basis for personnel processing remain separately governed.
Evidence to request for this scope
- Confirm authoritative identity attributes and supported target actions.
- Validate a complete test joiner/mover/leaver lifecycle against actual IBM i access.
- Document service-account ownership, reconciliation failures and approval history.