Skip to main content
A user offboarding runs your organization’s offboarding workflow for one identity, either now or at a time you schedule. With v1 you can start one, read it, and cancel it. No endpoint lists offboardings, so store the 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’s user_id and returns the offboarding with 201. This request body schedules one:
Omit 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 is scheduled 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 gets 403.

Endpoints