> For the complete documentation index, see [llms.txt](https://docs.harmony.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.harmony.io/ai-agents/employee-lifecycle/employee-offboarding.md). # Employee Offboarding The Employee Offboarding Agent helps you automate and manage the full offboarding process when an employee leaves your organization. Rather than coordinating tasks manually across teams, the agent creates a structured set of tickets, surfaces relevant employee data in context, and triggers notifications automatically - so nothing gets missed and your team can move quickly from the moment a departure is confirmed. ### How the Offboarding Agent Works When an employee is being offboarded, the agent creates a parent ticket that is automatically linked to all related child tickets covering every step of the offboarding workflow. Child tickets are created as non-optional items under the parent, ensuring no steps are skipped during the process. The offboarding workflow can be triggered in two ways: * **Automatically** - based on a configurable number of days before or after an employee's termination date, so the process kicks off at exactly the right time without manual intervention. * **Manually** - you can trigger the offboarding workflow directly for a specific employee when needed. When the workflow runs, it coordinates offboarding tasks and sends notifications to the relevant teams via Slack, Teams, and email, keeping everyone informed without requiring you to chase individual stakeholders. ### Providing an End Date You can supply an employee's end date when triggering the offboarding workflow. This gives the agent the context it needs to handle time-sensitive tasks accurately and ensures that offboarding actions are triggered at the right moment. The workflow includes end date filtering, so employees are surfaced and processed based on their actual departure date rather than requiring manual identification. ### Filtering Employees by End Date You can filter employees by their end date directly in the employee list. This makes it straightforward to identify employees who are leaving within a specific timeframe, so your team can prioritize and act on offboarding tasks without manually searching through records. The end date filter works alongside the Employee Offboarding Agent to help you automate offboarding at the right time for each departing employee. ### Assets and Applications Surfaced in Offboarding Tickets To help your team take action quickly, relevant employee data is surfaced in context directly within the offboarding tickets: * **Return Company Assets ticket** - displays all company-owned assets assigned to the departing employee, making it easier to track and action hardware or equipment returns. * **Account Termination ticket** - displays all applications the employee has access to, so nothing is missed during the deprovisioning process. This information is also visible on the parent offboarding ticket, giving you a complete picture of what needs to be addressed in one place. ### IDP Account Status Checks The offboarding agent can automatically check a departing employee's identity provider (IDP) account status during the offboarding process. The agent detects whether an account is active, locked, or suspended, and takes appropriate action based on the result. This reduces the risk of accounts remaining active after an employee has left and removes the need for manual verification steps. ### Setting an End Date for the Offboarding Run You can specify an end date for the offboarding run itself, giving you precise control over when offboarding actions are triggered and how long the workflow remains active for a given employee. This is particularly useful when offboarding needs to align with specific HR or IT timelines. ### Next Steps * Configure the Employee Offboarding Agent in your Harmony workspace to match your organization's offboarding process. * Set the trigger timing - days before or after termination date - to align with your team's workflow. * Review the child tickets generated for each offboarding run to confirm all required steps are covered. * Use the end date filter in the employee list to stay on top of upcoming departures. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.harmony.io/ai-agents/employee-lifecycle/employee-offboarding.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.