Contractor & Vendor Offboarding
Contractors and vendors don't fit the standard employee offboarding mold - there's no payroll or benefits to close out, and their departure is usually driven by a contract end date rather than a resignation. PurpletGo handles this with a Worker Type field on the employee record (Employee, Contractor, or Vendor) and a dedicated checklist template, rather than a separate product.
This feature (vendor access tracking) is available on the Team and Enterprise plans.
Worker Type and contract end date
When you add or edit a person in Employees, you can set their Worker Type to Contractor or Vendor and, optionally, a Contract End Date and the vendor company they're associated with. Contractors and vendors show up with a badge on their employee record so they're easy to tell apart from regular employees at a glance.
Contract expiry auto-offboarding
Every day, PurpletGo checks for contractors and vendors whose contract end date is today. For each one without an offboarding already in progress, it automatically:
- Creates an offboarding request (separation type "contract end", status "notice period")
- Applies the Contractor / Vendor Offboarding checklist - access revocation, hardware return, SOW closeout, and NDA confirmation, with no payroll or benefits steps
- Emails your org's superadmins, admins, and HR users to let them know the workflow was started automatically
This is a built-in daily job, not a configurable automation rule - there's currently no way to change the trigger condition or delay it beyond updating the contract end date on the employee record before it comes due.
If a contract gets extended, update the Contract End Date on the employee record before it expires. If an offboarding already got auto-created, you'll need to cancel or adjust it manually - PurpletGo won't retract it just because the date changes afterward.
The Contractor / Vendor checklist
This gallery template is scoped to contractor and vendor offboardings and covers: revoking internal system, VPN, email, and vendor-portal access; archiving or transferring project files; final knowledge transfer notes; returning hardware; confirming the final invoice; closing out the SOW; obtaining a signed termination acknowledgement; confirming NDA obligations; and removing the person from the directory. You can apply this template to any offboarding, not only ones created by the contract-expiry job.
Tracking vendor and system access
Each offboarding record has a Vendor Access panel for logging third-party access that needs to be revoked - separately from your regular checklist tasks. For each one you record a vendor name, a system name, an access type (account, API key, VPN, vendor portal, database, or other), an optional contact email, and notes. When it's been cut off, mark it revoked and optionally add a note - PurpletGo stamps who revoked it and when.
Revocation here is a manual record, not an automated action. Marking an access as "revoked" doesn't call out to Okta, GitHub, Slack, or any other system on your behalf - you (or IT) still have to do the actual revocation and then log it here so there's an audit trail.
Adding, editing, or revoking a vendor access record requires the access_revocation_manage permission (superadmin, admin, manager, or HR by default); deleting a record is restricted to admins and superadmins.
Asset recovery
Assets assigned to a contractor or vendor go through the same recovery flow as any other offboarding - see Assets for how return tasks and shipping labels work.