Deactivate a workspace

Deactivate a workspace to take it completely offline but retain the option to reactivate with all data. You'll have to reconfigure some resources when you reactivate a workspace.

This capability serves as a complement to the functionality for provisioning workspaces programmatically. 

Before you start

Here's a checklist of important information before deactivating a workspace.

• The Torq integration used to run the Deactivate a workspace step must have an API key generated by a user with the Owner role (the relevant scope is organizations.write).
• Full deactivation can take up to an hour, but some workspace features are deactivated immediately.
  • The workspace is not accessible in Torq.
  • All workflows are disabled (executions in progress are stopped).
  • OAuth integrations are unusable (they stop refreshing).
  • API keys are revoked.
  • Shared resources are revoked.
• To reactivate a workspace, contact your Torq contact person.
  • The reactivation process can take about an hour to complete.
  • After reactivation, all triggers are disabled (so you can manually verify that the workflow runs as expected).
  • OAuth integrations need to be reconfigured
  • API keys need to be reissued
  • Resources shared with other workspaces need to be shared again.

How to deactivate a workspace

1. Generate a Torq API key. You can skip this step if you already have an API key created with the Owner role. Use theClient ID and Client secret you copied to create a Torq integration.
2. Use the Deactivate a workspace step.
   1. Add the Deactivate a workspace step to your workflow.
   2. Enter the workspace ID of the workspace to deactivate.
   3. Select the Torq integration you created earlier.