Ending service and offboarding

To end workspace service, contact your account team and agree on record retention and endpoint cleanup before cancellation. A platform OWNER can use Cancel on customer request in Console to end access immediately and request billing cancellation while retaining tenant data. Billing-only cancellation, reversible Disable, native agent removal and permanent tenant deletion are separate operations. Self-service signup is not live, and public pricing is pending.

End access and billing on the customer's request

  1. A platform OWNER opens Customers, then the correct workspace. Confirm its identity and the customer's explicit cancellation request.
  2. Check The customer explicitly requested cancellation and choose Cancel on customer request. This action ends workspace access immediately and retains customer data. Do not select it when you only intend billing cleanup or a temporary access suspension.
  3. Read the displayed result. Billing cancellation confirmation is pending means billing is unresolved even though access has ended. The saved request retries automatically. Session cleanup is pending means physical session/token revocation still needs confirmation. Escalate persistent failures with the workspace, time and redacted error; do not assume every external operation completed.
  4. Confirm the final billing result with your account team. Existing invoices, charges, refunds and retention obligations require separate resolution. Cancellation does not uninstall endpoint agents or delete tenant data.

Complete the remaining offboarding work

  1. Confirm future recurring billing is stopped. The customer-request cancellation path reconciles recurring subscriptions and future subscription schedules. Console's separate Billing control cancels the selected whole subscription without ending workspace access. Do not substitute that billing-only control for the customer's request to end service. An unavailable provider or pending request is not cancellation confirmation. Preserve provider-account identity and historical billing links.
  2. Keep needed records. Export the records your agreement requires and verify that the export is readable and sufficient. Existing page CSV exports do not establish a complete tenant backup or tested restore. Do this before destructive deletion.
  3. Check access and session cleanup. Customer-request cancellation already ends access. Console also offers reversible Disable for a separate temporary suspension. Verify sign-in/routing denial and completed session revocation. If the App call fails, the registry flag alone is not proof that every active session was ended. Disable by itself does not stop Stripe charges, and Enable is not a substitute for resolving a recorded customer cancellation.
  4. Remove endpoint access. Revoke installer/enrollment tokens, arrange approved native uninstall on managed computers and confirm its result. Deleting a device or tenant record stops its valid check-ins; it does not uninstall the agent. Keep the customer record until any required device cleanup and export is verified.
  5. Delete only when ready. A platform OWNER opens the disabled customer's Danger zone, types the workspace slug and chooses Delete tenant (DB + site). This permanently removes its tenant database, tablespace/role and registry through the leased cleanup flow. The deployed billing guard verifies billing closure before requesting that purge and refuses unresolved provider identity, schedules, active subscriptions and unknown creation outcomes. Do not bypass a refusal by deleting registry rows or databases directly.

A purge failure preserves the deletion claim for recovery; follow the Console's displayed retry/reconciliation state. A lost subscription-creation response may mean the provider did create it. The reviewed guard retains a hold until that identity/outcome is reconciled; an empty provider list alone cannot clear it.

This guide was checked against production Console source 3ac399ac and App source 033ba4d7. Source inspection establishes the available controls and failure messages. It does not establish a completed provider cancellation, native uninstall, complete export or tested restore for your workspace.