Before
Support or IT likely looked up each employee in the relevant business application, made the account change, and checked the result separately. For applications without a direct integration, the request depended entirely on an IT team member to perform and report the change manually.
How it works
- Normalize the request and identify the target application and account action.
- Create or disable the account in a supported application, or mark unsupported applications for manual handling.
- Read the account back and return a status that reflects the verified result.
Workflow details
- Request preparation: The flow receives an account request containing the application, requested action, role, and user details, then normalizes the application and action values and derives a login from the email address.
- Application routing: It evaluates the requested application and action, directing supported create and disable requests to the relevant application path while sending unsupported applications to an explicit manual-handling outcome.
- Account creation: For supported creation requests, it submits the user identity, organizational details, and selected role, then checks that the account can be found afterward using the requested email address.
- Account disabling: For disable requests, it first locates the account, changes it to inactive rather than deleting it, and reads the account again to confirm that the inactive state is present.
- Verified result: The workflow returns the application, action, status, and supporting detail. It distinguishes completed and verified changes from failed operations, missing accounts, and requests that IT must complete by hand.
What changed
The requesting workflow now receives a specific, evidence-based outcome instead of assuming the account change succeeded. Supported account creations and disables are checked automatically, while unsupported applications are clearly returned as manual actions.
Work removed
Manually repeating account lookups, entering user and role details, applying create or disable changes, checking the account afterward, and determining whether the request succeeded or needs escalation.
Expected outcome
For supported applications, each request replaces the manual change sequence with at least two automated account-state checks—lookup or action verification—while reducing access changes closed without confirmation.
