Gitfence
Start free

Offboarding and exit packs

End a person's access, revoke tokens and agents, and download a signed exit pack with agreements, access history and exposure receipts.

Short answer: Offboarding ends every repository membership, token and agent for one person, closes their pending requests, and gives you a signed exit pack with the access history and agreements.

Steps

  1. Open the person. Go to People, find the person, and choose Offboard.
  2. Confirm. In Offboard ? choose Offboard. You cannot offboard yourself; ask another admin.
  3. Download the record. The result says was offboarded and lists repositories removed, sign-ins revoked, agents and requests closed. Choose Download exit pack or Done.

What offboarding removes

  • Every repository membership, exception and pending access request.
  • Every token, including an admin's own tokens and agent tokens.

It does not remove an admin role. Change that in organization settings.

Removing a person from one repository is smaller: it clears their exceptions and requests there and drops their agent copies. If other repositories remain, tokens limited to that repository are revoked. On their last repository an admin's personal and setup tokens remain, which is why Offboard is the step that ends everything.

The exit pack

The record is called an Access record while the person still has a repository, and an Exit pack after access ends. It covers their whole recorded time, across repositories:

  • identity, GitHub login, inviter and memberships
  • group and access history, with who approved each change
  • ladders, requests and their outcomes
  • a separately signed exposure receipt, split between the person and each agent
  • agreements with version, SHA-256, typed name, time, IP and browser
  • token and agent history

The ZIP contains the signed PDF and JSON, agreement originals, a signature certificate for each, and README.txt. The endpoint also accepts ?format=pdf and ?format=json, and each request generates a fresh signed record.

Verifying and sharing

Open https://gitfence.dev/verify, extract the ZIP, and check the JSON or PDF with Check a receipt. The page checks the organization key, document hash and Ed25519 signature. It verifies the embedded record, so read the contents shown there rather than the PDF's visible pages.

From People, What could they see? offers Share by link. A shared record opens at /r/<token> and is checked on every opening. Withdraw it under Receipts → Share links → Withdraw. That stops the link, not copies already downloaded.

Gotchas

  • The pack records what Gitfence served. It does not show files opened or text sent to an AI provider, and makes no claim about legal weight.
  • Changes before the ledger existed are unknown, and direct GitHub access is outside it.
  • Code already cloned stays on the person's machine.
  • For a wider log, use Settings → Audit log → Export.

Next: encryption at rest and adding a contractor.

Related guides