Skip to content

Archive a collaborative Workspace when you need to stop its operation while keeping its identity and data. Account → Workspaces shows active and archived Workspaces and the available actions for your role. A personal Workspace follows its account lifecycle.

Archive

An authorized Owner must cancel a paid subscription before archiving; the action remains unavailable while cancellation is required. Archiving stops published apps, agents, and automations. It retains data, membership, and the Workspace UUID. A scheduled subscription cancellation still follows its paid period; archiving does not issue a refund or waive outstanding charges.

Reactivate

Reactivation restores access and resources archived by the Workspace action. Resources archived earlier on their own remain archived. Apps, agents, and automations stay stopped until explicitly resumed. Reactivation does not restart a subscription or grant new introductory credits. Review archived resources in Workspace settings and restore individual items when appropriate.

Delete

Permanent deletion is a separate Owner action with consequences for Project data, other resources, active work, production, domains, and retained financial history. Read the confirmation for the selected Workspace before proceeding. The Account → Workspaces list retains lifecycle progress and failed operations for review or retry. See Site operations for production resources.

Example: pause a completed engagement

Before archiving a collaborative Workspace, review subscriptions, operating Sites, Agents, and schedules. Complete the required subscription cancellation and inspect the action’s consequences for the selected Workspace.

When reactivating later, check which resources need explicit restoration or resumption. Do not assume the archive action and previously independent resource archives have the same recovery behavior. See Schedules and Site operations.

Review completion

Follow the lifecycle status for the selected Workspace. A submitted archive, restore, or deletion request is not evidence that all resource work has settled. If an operation fails, inspect the displayed progress and recovery action before repeating it.

For an engagement that may resume, document which Sites and recurring tasks were intentionally stopped. On return, review their configuration and funding before resuming them.