Appearance
Account Provisioning & Equipment/Assets (HCM)
This page documents two shipped Onboarding screens (hcm-onboarding) covering what a new joiner needs before or on day one. Not for plugin developers.
Account Provisioning
Request a system or account for a new joiner (14 real account types — identity/IAM, ERP, email, and more). If you mark a request as needing approval, Start is blocked until someone Approves it first — a real, if simple, gate. From there: Activate (records the real account name and external ID once it exists), Fail/Retry (retries are capped by a max-attempts count, not an unlimited retry loop), Suspend/Reactivate, Deactivate, Cancel.
Equipment & Assets
Request equipment for a new joiner (20 real categories). Walk it through Allocate (asset tag required) → Schedule Delivery → Deliver → Acknowledge (the recipient confirms receipt, condition required) → Return Request → Return — or Report Damage / Report Loss at any point along the way. Every step is logged to a real history.
Known gaps
- Neither screen actually provisions anything for real — there's no IAM/SSO connector, no live account creation, no asset-inventory system behind these. Activating an account records what you type (a name, an external ID); allocating equipment records an asset tag you type. These are tracking/confirmation screens for IT/Facilities to record what's been done, not systems that do the provisioning themselves.
- No multi-party approval routing — Account Provisioning's single approval toggle is the only approval concept here; there's no Manager → Application Owner → Security chain.
- No reusable request bundles — a "standard new-hire laptop + badge + email" bundle has to be requested item by item, not as one preset.
- Nothing is auto-generated from a new joiner's role/department — every request starts from the dialog here, manually.