Public Guide

What Happens to Your Data When You Leave BlackShield

Understand how offboarding works in BlackShield: open `/tenant-rights`, confirm the workspace snapshot, collect any needed audit or report exports, then run the tenant deletion flow with a typed confirmation phrase. Audience: Compliance, legal, procurement, and platform operations teams. Typical setup time: 15 minutes.

trust

Use this if

Understand how offboarding works in BlackShield: open `/tenant-rights`, confirm the workspace snapshot, collect any needed audit or report exports, then run the tenant deletion flow with a typed confirmation phrase.

Audience: Compliance, legal, procurement, and platform operations teamsTypical time: 15 minutes

Before You Begin

  • Have `/tenant-rights`, `/audit`, and any needed reporting screens available for the offboarding review.
  • Choose which audit or report exports must be captured before deletion.
  • Document the offboarding runbook including revoke, export, and delete sequencing.

Guide walkthrough

1

Step 1

Open the workspace snapshot before you delete anything

Review the active workspace snapshot directly in the console screen where tenant deletion is initiated.

  • Open `/tenant-rights` and confirm the tenant slug, user roster, and data summary counts for the workspace being offboarded.
  • Use the snapshot to confirm which BlackShield record categories currently exist for that tenant.
  • Get the legal or business approval you need before moving to the delete step.

What success looks like

Get the legal or business approval you need before moving to the delete step.

2

Step 2

Capture the exports you need before the delete flow

BlackShield gives you tenant deletion in `/tenant-rights`; evidence and reporting exports come from the relevant product surfaces before deletion.

  • Use `/audit` if you need CSV or JSON evidence for activity history.
  • Use `/reports` and `/compliance` if you need findings, executive, or control-coverage exports before exit.
  • Do not start tenant deletion until those exports are captured and stored where your process expects them.

What success looks like

Do not start tenant deletion until those exports are captured and stored where your process expects them.

3

Step 3

Run the BlackShield delete flow and keep the returned summary

The offboarding workflow is concrete and product-driven, not a manual checklist outside the platform.

  • Type the confirmation phrase shown in `/tenant-rights` and acknowledge the action is irreversible.
  • BlackShield deletes the current workspace's users, findings, API keys, alert-sync records, audit logs, ingestion jobs, external assets, and company record.
  • Save the deleted-record summary and sign out of the current session after deletion completes.

What success looks like

Save the deleted-record summary and sign out of the current session after deletion completes.

What success looks like

  • Your team can walk another reviewer through the exact BlackShield offboarding flow without inventing missing steps.
  • Offboarding confirmations include the deleted-record summary and any remaining caveats.
What Happens to Your Data When You Leave BlackShield | BlackShield Docs