id that
Create User Offboarding returns.
The User Offboarding object
Attributes
All timestamps are UTC.
Statuses
Starting an offboarding
Create User Offboarding takes the identity’suser_id and returns the offboarding with 201. This request body schedules one:
scheduled_at to start the offboarding now. To schedule it, send a future ISO 8601
date-time. Lumos converts a value with a time zone to UTC, and reads a value without a time zone as
UTC.
Offboarding workflow configurations
workflow_config_id names an offboarding workflow configuration, which you create in Lumos. It
isn’t a workflow from /v1/workflows, and no v1 endpoint lists
configurations.
Omit workflow_config_id to use the configuration that your organization selected for automatic
offboarding. A workflow_config_id that Lumos can’t find returns 404.
If your organization doesn’t have the multiple offboarding workflows feature, sending
workflow_config_id returns 400. The response is the same as for an unknown field, as
Field-level errors describes.
Cancelling
Cancel User Offboarding stops an offboarding whose status isscheduled or in-progress, and returns 204. In any other status the
call returns 409.
Who can do what
Of the built-in roles, Admin can start and cancel offboardings, and Admin and Read Only Admin can read them. A custom role can also allow these actions. Any other role gets403.