Select your experience
The interface steps depend on your Drata version. Select your version to skip to the instructions tailored for you.
Customers who joined Drata on or after Feb 24, 2026, are automatically on the New Experience.
Instructions for the New Experience
Follow these steps if you are using the New Experience UI.
Prerequisites
Role: You must have a Drata Admin role.
Status: Evidence can only be linked to individuals with a Former personnel status.
Jira Connection: To use Jira-based evidence, a Jira connection must be enabled in Drata.
Important rules for Jira evidence
Drata uses specific data to verify if a Jira ticket is valid proof of offboarding.
Closed tickets only: Only closed tickets are included in audits. Drata determines a ticket is "closed" based on the Resolution date field.
When a former employee is selected for review during an audit, only closed tickets in Jira, which is determined by the resolution date Jira field, are included in the evidence download, even if the overall status of the ticket is Closed or Completed.
The DrataAccept label: If your Jira project is Team-managed (which does not expose the resolution date) or if the ticket lacks a resolution date, you must add the label
DrataAcceptto the ticket in Jira.Automation limits: Automated Jira searches (JQL) must specify exactly one project and one issue type (e.g.,
type = story).
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
Learn more about offerboarding checklist.
Supported file uploads
If you provide evidence manually, use screenshots, exported reports, or PDFs that document the removal of access. Common examples include:
Identity Provider (IdP) records: A screenshot or export from Okta, Entra ID, or a similar provider showing the account is disabled or deleted.
HRIS records: A screenshot from your HR system showing the person marked as terminated with a visible effective date.
Internal checklists: A PDF or image of a completed offboarding checklist that lists specific systems and confirms the date access was removed.
Valid Jira tickets
A Jira ticket serves as valid evidence when it documents the specific actions taken to secure your environment. To pass an audit, the ticket must meet the following criteria:
Documented actions: The ticket description or comments should list the systems where access was removed (for example, "Okta account disabled" or "Google Workspace access revoked").
Resolved status: The ticket must be in a "Done" or "Resolved" state.
Validated metadata: For company-managed projects, the ticket must have a Resolution date. If the ticket does not have a resolution date (or is in a team-managed project), it must include the
DrataAcceptlabel.
View offboarding status
Where to find it: Go to Governance > Personnel.
Action: Filter by Employment status > Former employee.
Impact: View the Offboarding evidence column to identify who has evidence linked and who is missing it. You can also filter by Compliance > Offboarding evidence missing to see a list of incomplete records.
Provide evidence manually
Use this method for screenshots from your Identity Provider (IdP) or HRIS, or for individual Jira tickets.
Go to Governance > Personnel.
Select the former employee.
Scroll down to the Requirements table and select the Offboarding evidence requirement.
Tip: If you only need to upload a file, you can select the ellipses (...) next to the requirement and choose Upload for faster access.
Choose your evidence type:
To upload a file: Select Upload file and choose your screenshot, PDF, or report.
To link a Jira ticket: Select Upload ticket and paste the Jira ticket URL.
Manage exclusions: If this requirement does not apply to this specific person, you can select Create an exclusion within this same view.
Automate evidence collection
Go to Settings > Personnel Compliance > Human Resources tab.
Toggle Automate offboarding evidence collection to On and select Configure.
Configuration Setup (JQL): Enter your search string (e.g.,
project = "Offboarding" AND type = "Task").Matching Logic: Choose to match by Full name or Email and map them to the corresponding Jira fields.
Review: Check the 5 sample matches for accuracy before selecting Finish.
Instructions for the Classic Experience
Prerequisites
Personnel must have a former personnel status to have offboarding evidence linked to them.
To link Jira tickets or automate ticket collection as evidence, ensure you have Jira connection enabled.
Linking tickets: When a former employee is selected for review during an audit, only closed tickets in Jira, which is determined by the resolution date Jira field, are included in the evidence download, even if the overall status of the ticket is Closed or Completed.
Tickets without resolution date: Apply the
DrataAcceptlabel to tickets that do not have a resolution date to ensure the tickets are accepted as valid evidence when off-boarding.Team-managed projects do not have the resolution date field exposed on tickets, therefore must have the
DrataAcceptlabel in order to be considered as valid evidence.
Automated ticket: For automated ticket matching using JQL, you need to specify a project and an issue type (such as, type: story). Currently, we do not support custom fields for automated ticket matching; only Jira default fields are supported.
View personnel's offboarding evidence status
Go to Personnel page and select the settings icon and then select Detailed view for the table.
View the Offboarding Evidence column to view who has offboarding evidence and not.
Manually upload offboarding evidence for a former personnel
Select the personnel you want to upload evidence for.
On the drawer, select View / Upload Evidence.
Ensure you are on the File tab and upload file(s) for that personnel.
Manually Link Jira Tickets for offboarding evidence
Note: Only closed tickets will show up as evidence in the audit package
Select the personnel you want to upload evidence for.
On the drawer, select View / Upload Evidence.
Ensure you are on the Ticket tab and paste the URL of the Jira ticket into the Ticket UR field and then, select on the link icon ().
Multiple tickets can be linked to the same personnel. All linked tickets will be shown underneath the Ticket URL field.
To unlink a Jira ticket from offboarding evidence for a personnel, select on the Unlink button on that ticket.
Automatic Evidence Collection with Jira
Note: We use the resolution date to confirm the ticket has been closed. If there is no resolution date on the ticket, this will not be considered as passing evidence.
You can configure Drata to automatically search and identify offboarding Jira tickets that will be linked to their respective personnel in Drata on the Human Resource page.
Navigate to the Settings page. To go to settings, select your username and then Settings.
On the Settings page, select Human Resources.
On the Human Resources page, scroll down to Automate Offboarding Evidence Collection section and toggle this on. Then select Configure to enter the automation rules. By default it is toggled off.
After you select configure, you can enter the JQL from Jira that provides the list of all offboarding related tickets (past and ongoing).
JQL specifications:
Must specify project and type (such as issue: story).
Do not support custom fields (only Jira default fields are supported).
Ex:
(project = "Offboarding" AND type = "Task")
Multiple Jira connection:
Select which connection you want to collect the evidence from. Automatic collection is supported in a single connection.
You will be prompted to select one or both personnel criteria to match tickets from that JQL search in the previous step. Selecting both means the ticket must contain the personnel’s name and the personnel’s email.
When you select a criteria, select which field in the jira ticket we should look for to find that information.
For example, if you select Personnel Full Name and you select Title for that field, Drata will first run the JQL search to obtain all the offboarding tickets. It will then parse those tickets to find a match for a former personnel’s name in the title of those tickets. Any ticket(s) with a match will get linked in the offboarding evidence section of Drata’s personnel page.
Note: If multiple former personnel with the same exact first name and last name are found, all the matched evidence will be linked for all.
Once you select Next, Drata will search through the Jira tickets using the JQL search and use the matching criteria to provide up to 5 examples of Jira tickets that would be linked to a former personnel record in Drata.
Verify the matched the tickets and if satisfied, select Close. If you are not satisfied with the matched tickets, you can go back to previous steps to modify the matching criteria or the JQL in the previous steps and try to obtain a more accurate result. Once ready, select Close.
A Jira ticket is mapped as offboarding evidence for former personnel. The Former Personnel Offboarding test validates that required offboarding evidence is present for all former personnel.