Prepare to leave Workspace

Save the work you need before your paid period or Account access ends. An Account owner manages the Workspace subscription. Each person or Agent must also review the work and private Tasks it owns.

Canceling Workspace takes effect at the end of the paid billing cycle. It does not delete your data, cancel an external AI subscription, or stop separate Cloud charges. Account and Agent deletion have additional consequences, so complete the checks below before deleting either.

Preserve your work

Save copies in a location you control that will remain accessible after leaving this Account or deleting the Agent. Keep private material in an appropriately restricted destination.

Open your saved copies and check that they contain what you need before ending access. A downloaded file, a Flash, and an exported PDF each cover a different part of your work.

These steps do not establish a complete Account export. If the available controls do not cover something you need, contact Socra support before giving up access. Identify the product, required content and versions, and when your access is due to end. Confirm the supported recovery and retention terms for that material; cancellation does not guarantee continued editing or an unlimited retention period.

Save Cortex records

First complete the supported CLI installation and add Cortex. Confirm that socra cortex --help works before starting. A missing command or plugin is a setup prerequisite, not proof that your records are unavailable.

Use the CLI under an identity with access to the required Modules. Replace the example names and IDs below with yours. Save each result in a separate local file or document, then open it and check its content.

socra cortex module list
socra cortex module list --archived
socra cortex module get MODULE_NAME
socra cortex module version list MODULE_NAME
socra cortex module version get MODULE_NAME VERSION_NUMBER
socra cortex issue list --module MODULE_NAME
socra cortex issue get ISSUE_ID
socra cortex comment list --issue ISSUE_ID
socra cortex attachment list ISSUE_ID
socra cortex attachment download ATTACHMENT_ID ./saved-attachment.pdf

When a list prints More results, repeat that command with its printed --after cursor. Do this for Module, version, Issue, comment and attachment lists. Repeat the record reads for every required item. Save needed dependencies as their own Modules and preserve the dependency names. Use the attachment's actual filename and extension for its destination, then open the downloaded file.

Module and Issue reads do not include all related records automatically. These copies do not preserve every permission, schedule or Account setting, or provide a complete restore package. A saved Flash manifest records source-time versions; requesting its assembly rebuilds current content. Preserve needed immutable versions separately.

Save Channels messages and drafts

Open each required conversation and use Load earlier messages to reach older content. Open relevant threads explicitly through their reply summaries or Reply in thread. In a thread, use Load earlier replies while that control is available to reach older replies. Select Copy message text on each required message, wait for Copied to clipboard, then paste into a document outside Channels. Include the conversation, author and date needed to understand the text, and save and reopen the document. Copy required replies separately; copying a parent message does not copy its thread.

Save required attachment files separately and check that they open. Copying message text does not copy file contents. In Drafts, select Open conversation and preserve the text and attachments you need. If the composer says Saved on this device · waiting to sync in the desktop app, or Saved in this browser · waiting to sync in the browser app, preserve that device's or browser's local data until you have saved the needed text and files elsewhere. Review drafts and scheduled messages.

These steps preserve selected messages and files. They do not establish a complete archive of conversations, edits, reactions or deleted content. Do not use the app's cache as your backup: loss of access can remove cached content.

Save each identity's Tasks

Follow the Tasks CLI setup first and confirm that socra task --help works. Under the identity that created the Tasks, select the intended Account and run:

socra task list
socra task list --deleted

The first command includes non-deleted completed and canceled Tasks; the second lists soft-deleted Tasks. If has_more is true, repeat the same command with --after LAST_ID, using the final ID from that page. Save each page of the inventory.

Copy a required Task's ID from the inventory as TASK_ID, then read its details and occurrence history:

socra task get TASK_ID
socra task occurrence list TASK_ID

Save the Task's instructions, schedule timing and state, source link, and needed occurrence records in a document you can keep. If an occurrence list has has_more: true, repeat socra task occurrence list TASK_ID --after LAST_ID, using the final occurrence ID from that page. Save linked work separately with its own permissions. A source link is not a copy, and an occurrence record does not prove the work was completed. Check the saved documents before removing the owning identity's access. This is an owner-by-owner copy procedure, not an Account-wide export.

Confirm access before the paid period ends

Subscription cancellation and app access are separate states. Access can depend on current membership, permissions and other valid grants. Cortex reads require authorized app access as well as the relevant Module permissions; this guide does not promise an export-only grace period after access ends.

Before that date, confirm with support how to recover any material you have not copied. Continued reading, export, recovery and retention after lapse are not established here for every product. Do not assume that retained data will remain accessible, or that cancellation erases it. Any retention deadline must come from the applicable product and policy terms.

Stop work that should not continue

Inspect active work before stopping it. A task or scheduled message may already have changed an external system or been delivered.

• Have each Task owner inspect pending and running work, including both one-time and recurring schedules, and pause or cancel what should stop. Follow the Tasks CLI controls, including their version prerequisite for updates. Completing one recurring occurrence leaves the series active. Read the Task again to confirm its saved status, paused state and next run; stopping scheduling cannot undo an action already executing.
• In Channels, open Scheduled and cancel pending deliveries you no longer want. Check the conversation first if the scheduled time has passed, and confirm the message is no longer pending.
• Inspect managed Agent activity before using Pause work. Refresh its detail page and confirm Paused. Pausing preserves its home and connection, but its monthly base charge continues while the subscription remains active through the paid period.

Cancel Workspace and confirm the date

1. Open Admin and confirm the intended Account.
2. Open Billing → Subscriptions.
3. Open the Workspace subscription and check Current period.
4. Select Cancel subscription.
5. Review the confirmation and select Cancel subscription again.
6. Confirm that Renewal shows Cancels and the end date.
7. Refresh and check Renewal again.

The subscription may remain Active until the paid period ends. If the cancellation date is absent or an error appears, refresh before retrying. Renew requests continued renewal before the period ends; check the resulting subscription state after any change.

Managed Agents stop being eligible to run when the Workspace subscription ends. Usage already incurred remains payable. Unused credit expires at the end of the cycle, and a future cycle's credit cannot cover that cycle's outstanding usage. Review the resulting invoices under Billing → Invoices; cancellation does not itself establish that the final amount has settled.

Keep billing records before removing access

An Account owner can retrieve invoices in Admin:

1. Confirm the selected Account's name and handle.
2. Open Billing → Invoices and use the page controls to review the available records.
3. Find each needed invoice by number, period or amount and check its status.
4. Select Open when available. It opens the PDF if one exists, otherwise the hosted invoice page, in a new tab.
5. Save the records you need and check that the saved copies open before removing the owner's access.

An invoice's presence does not prove it was paid. A row without Open has no PDF or hosted link available through that control; keep its visible details and resolve any missing record with support before removing access. No invoices yet means no records were returned for the selected Account. Check the Account and subscription if you expected a bill. An admin who is not an owner must ask an Account owner to retrieve invoices.

Review other services and access

Review your AI provider subscription and any Cloud resources separately. Keep their cancellation or cleanup confirmations. If you use Cloud credit auto-reload and want to stop future automatic purchases, follow Cloud usage credit: in Billing → Usage, under Auto-reload, select Configure, turn off Enable auto-reload, and save. If saving fails or the resulting setting is unclear, resolve it with support before treating automatic purchases as stopped. Follow the relevant Cloud service's own instructions for its resources. Work accepted while the Cloud Account was funded can finish and settle later, taking its balance below zero. An automatic-refill limit controls new automatic purchases; it does not reserve funds for accepted work or cap that work's final charge. Review Cloud activity separately from Workspace invoices before treating the remaining amount as settled.

After verifying your saved copies, decide whether you want to leave the Account or delete it for everyone. To leave, ask another Account owner to remove your membership. If you are the last owner, arrange for another eligible person to become an active owner first.

Account deletion removes everyone's access and has no undo action in Admin. It does not establish that all subscriptions or outstanding charges were canceled, or that every downstream copy was physically erased. Follow Account deletion only after preserving your work and reviewing paid services.

If you delete a managed Agent, confirm that deletion completed and that it no longer appears in Admin. A cleanup-pending result is unfinished. Review external credentials separately; Agent deletion does not revoke every credential it may have used.