💡 Still using the classic Drata experience? Refer to Personnel Offboarding for the original UI.

Drata requires proof that access and responsibilities were removed for former personnel. This article explains how to provide and manage offboarding evidence so former employees do not impact your compliance posture.

You can:

Upload evidence manually, or
Automatically collect evidence from Jira

What counts as offboarding evidence

Offboarding evidence shows that required actions (such as access removal) were completed for a former employee. Common examples include:

Closed Jira offboarding tickets
Access removal confirmations
IT or HR task completion records

Offboarding evidence is evaluated by the Former Personnel Offboarding compliance test.

Prerequisites

The person must have Former personnel status in Drata
To link Jira tickets:
- A Jira connection must be enabled
- Tickets must meet Drata’s acceptance rules (see below)

Jira ticket requirements (important)

Drata uses Jira ticket metadata to determine whether a ticket qualifies as valid offboarding evidence.

Closed tickets only

Only closed tickets are included in audit evidence
Closure is determined by the Resolution date field

Tickets without a resolution date

Add the DrataAccept label to the ticket
This is required for:
- Tickets without a resolution date
- Team-managed Jira projects (resolution date not exposed)

Automated ticket matching limits

JQL must specify:
- A project
- An issue type (for example, type = Task)
Custom Jira fields are not supported
Only Jira default fields can be used

View offboarding evidence status

To identify which former personnel have offboarding evidence:

Go to Governance → Personnel
Filter by Employment status → Former employee or Former contractor
Within the table, navigate to the Offboarding evidence column.

To find personnel that are do not have offboarding evidence:

Go to Governance → Personnel
Filter by Compliance → Offboarding evidence missing

Manually upload offboarding evidence

Expected outcome: Files are attached as offboarding evidence for a former employee.

Go to Governance → Personnel
Select the former employee
In the drawer, select View / Upload Evidence
Stay on the Files tab
Upload the required evidence files

Manually link Jira tickets

Expected outcome: Closed Jira tickets are linked as offboarding evidence.

Go to Governance → Personnel
Select the former employee
Scroll down to the table and search for Offboarding evidence requirement.
Select the requirement.
Select the Upload evidence button and then choose ticket.
Paste the Jira ticket URL.

You can link multiple tickets to the same person.

Note: Only tickets that meet the Jira requirements are included in audit downloads.

Automatically collect offboarding evidence from Jira

Step 1: Enable automation

Go to Settings → Personnel Compliance → Human Resources tab
Scroll to Automate Offboarding Evidence Collection
Toggle the feature on and select Configure

Step 2: Configure Jira automation rules

Enter a JQL query that returns offboarding tickets
- Example: (project = "Offboarding" AND type = "Task")
Select the Jira connection to use

Step 3:

Select the Jira fields used to match former personnel to Jira tickets. Choose at least one field.

Full name field (optional): Select the Jira field that contains the employee’s full name.
Email field (optional): Select the Jira field that contains the employee’s email address.

Step 4: Review matched tickets

Drata previews up to 5 example matches
Review results and adjust rules if needed
Select Close to activate automation

Once enabled, matching Jira tickets are automatically linked as offboarding evidence.

Important edge cases

If multiple former personnel share the same name, matching tickets may be linked to multiple records
Tickets without resolution dates must use the DrataAccept label
Only closed or accepted tickets appear in audit evidence