Leaver Offboarding

Track leaver requests, schedule access removal, confirm asset return, and escalate risky offboarding exceptions.

Get in touch

Coordinate access removal and asset return

Keep offboarding work visible across the people and systems involved. The agent tracks the leaver request, coordinates access removal and asset return, and escalates exceptions that need a person’s attention.

How it works

A requester submits a leaver offboarding through Slack, Teams, or the Leaver Offboarding Form, creating a tracked request row. The agent confirms the request type, retrieves context from HRIS, identity provider, and ITSM records, checks the relevant policy source, and asks for any missing details in chat.

Where policy permits, the agent completes standard access suspension and checklist creation when the leaver record is complete and records the outcome without waiting for manual handling. The agent escalates executive leavers, immediate terminations, missing dates, or unreturned assets to the responsible owner with a decision summary and supporting context.

An approver reviews the escalation in chat or the Offboarding Exceptions Queue, then approves, rejects, or returns it for more information.

Where people stay in control

People remain responsible for approval exceptions; risky or ambiguous requests.

Adapt it to your organization

Connect the systems listed alongside this description and configure the workflow for your organization’s data, permissions, and policies. Review the named agents, apps, and automations before using them with your own records.

Contact sales

Interested in modernising processes with Budibase?

Enter a valid email address so our team can reply.

The security check will load when the form is visible.

Having trouble submitting? Email sales@budibase.com.