Agent-readable docs index: /llms.txt. Full docs in one file: /llms-full.txt. Download /docs.zip to grep all markdown files locally.

Workspace lifecycle

A managed customer workspace moves through creation, operation, offboarding, and archive; each stage ends with the workspace in a known, verifiable state.

Create

  1. Open Customers
    In the managing workspace, open Customers and select Add customer.
  2. Enter the customer details
    In the Add customer dialog, enter the Customer name (the customer's legal or commonly recognized company name) and the Primary domain. Optionally enter an Administrator email to invite the customer's first administrator.
  3. Review the reservation and billing notes
    The dialog notes two effects. The domain is reserved automatically: users with that email domain cannot join another workspace. And on billed managing-account subscriptions, the new active customer increases your managed-customer quantity, with standard Stripe proration charging for the rest of the current billing period.
  4. Create the workspace
    Submit the dialog, then record an internal reference (via Edit customer) only when it helps reconcile the customer with your PSA or billing system.
Before inviting users, connect only the required apps and establish a baseline group policy.

Operate

Review workspaces that need attention, have stale activity, or contain unconfigured apps. Identity synchronization is optional; its absence is not by itself a health failure.
Keep cloud permission packs and identity configuration inside the selected customer's settings. Reconfirm the workspace before opening an external authorization flow. See Operate customer workspaces.

Offboard

  1. Stop new access changes.
  2. Export required Audit records.
  3. Revoke AI clients and personal authorizations.
  4. Remove or disable users and identity provisioning.
  5. Revoke shared provider credentials.
  6. Archive the workspace according to the customer agreement.

Archive vs delete

Archiving is the supported way to end a customer relationship in the portal:
  • Archiving runs through an intermediate suspended state: access, invitations, connections, and sessions are revoked first, then the workspace is marked archived. The Customers page shows both suspended and archived workspaces as Offboarding; if an archive stops partway, the customer remains suspended until the archive is retried.
  • Archive (the Archive action on the customer) suspends access while retaining the customer's domain claims and audit history. It asks for a reason and requires typing the customer's domain to confirm. While archived, the customer's management actions are disabled. An archived customer stops counting toward the per-customer charge; following standard Stripe subscription behavior, the reduction is prorated for the current billing period rather than as a mid-cycle credit.
  • Reactivate is available on an archived customer, restoring administration. Reactivation does not prove old credentials or policies are still appropriate—review users, groups, connections, AI clients, and provider scopes before allowing new calls.
Permanent deletion is not available from the Customers page. If you need a customer workspace permanently removed, or need to understand the billing and recoverability consequences, contact support before deleting anything.
Powered byHolocron