Offboarding Ownership Transfer Report
Maps everything a departing employee owns - applications, tickets, pending approvals, desks, and agents - into one ticket before their last day.
- Triggers ahead of an employee's end date, two weeks by default
- Looks up the departing employee to title the report
- Gathers everything they own: applications, tickets, approvals, desks, and agents
- Opens a ticket with the full ownership report attached
- Notifies the assignee, falling back to the desk managers
- Stays silent when the employee owns nothing
What Offboarding Ownership Transfer Report does
Offboarding Ownership Transfer Report answers the question that surfaces a week after someone leaves: what were they responsible for? Ahead of a departure - two weeks by default - it gathers the employee's full ownership footprint from Harmony: the applications they own, the tickets assigned to them, the approvals waiting on them, the desks they belong to, and the agents that reference them. That becomes one ticket, with the report attached, notified to whoever needs to reassign it. Revoking access is a different job, handled by offboarding proper. This is about the responsibilities that have no owner the moment someone walks out.
Who Offboarding Ownership Transfer Report is for
IT and HR operations teams running offboarding, and the managers who inherit a departing employee's responsibilities.
Offboarding checklists are built around taking things away: accounts, devices, licences. They rarely ask what the person was responsible for. So an application keeps an owner who no longer works here, approvals queue behind someone who will never respond, tickets sit assigned to a deactivated account, and a desk quietly loses a member. Each one surfaces later as a small mystery, usually when something is already blocked.
How the Offboarding Ownership Transfer Report works
An employee termination event from your HRIS, fired relative to their end date - 14 days before, by default, and configurable. The workflow ships disabled and must be turned on.
- Fetch the employee profile
Looks up the departing employee so the report and its ticket are titled with their name.
- Query their ownership footprint
Gathers everything attached to them: applications they own, tickets assigned to them, approvals awaiting their response, desks they belong to, and agents that reference them.
- Create the report ticket
Opens a ticket carrying the ownership report and its attachments on the configured desk. Skipped entirely when the employee owns nothing.
- Resolve who to notify
Uses the configured assignee, falling back to the managers of the receiving desk.
- Send the notification
Tells those recipients a report exists and asks them to review and reassign the responsibilities in it.
A single ticket, raised before the last day, listing everything the departing employee owns - so reassignment happens while they are still available to ask.
Capabilities
- Fires ahead of the end date - Triggers on the termination event relative to the departure, two weeks before by default, so there is time to hand over.
- Full ownership footprint - Covers owned applications, assigned tickets, pending approvals, desk membership, and agent references in one pass.
- Pending approvals surfaced - Approvals waiting on the departing employee are named, so requests do not stall behind an account nobody is using.
- One ticket per departure - The report arrives as a single actionable ticket rather than five separate discoveries over the following month.
- Assignee with desk-manager fallback - Notification goes to the configured assignee, or the desk managers when none is set.
- Silent when there is nothing to transfer - No ticket and no notification when the employee owns nothing, so departures that need no handover create no noise.
Main use cases
An application owner leaving - A departing engineer is the listed owner of three applications. The report names them two weeks out, so ownership moves while the person is still around to explain what each one is for.
Approvals that would have stalled - Several access requests are waiting on the departing employee's approval. They appear in the report, get reassigned before the account is deactivated, and never become tickets about why nothing is moving.
A desk quietly losing a member - The employee belongs to a service desk with a small rota. Desk membership is part of the report, so the gap is visible before it shows up as slower response times.
Integrations
| Integration | Role in the agent flow |
|---|---|
| Your connected HRIS (HiBob, Workday, BambooHR) | Fires the termination event and supplies the end date the trigger is timed against |
| Harmony application and desk records | Source of the applications, tickets, approvals, desks, and agents the employee is attached to |
| Harmony Service Desk | Native ticketing - creates the ticket, carries the attachment, and records the outcome |
| Harmony Notifications | Delivers the alert through each recipient's preferred channel: Slack, Teams, or email |
FAQ
Offboarding takes access away: accounts, applications, devices. This report covers what the person was responsible for - owned applications, assigned tickets, pending approvals, desk membership - which needs a new owner rather than revoking. They are complementary halves of a departure.
Meet more Agents
