Overview
Sharing Step Runners across Torq workspaces allows organizations to reuse existing runner infrastructure across multiple environments. Instead of deploying and maintaining separate runners for each workspace, teams can share runners from a central workspace while keeping configuration and management centralized.
Shared runners enable workflows in destination workspaces to execute steps on the same infrastructure as the source workspace. This approach simplifies runner management, reduces infrastructure duplication, and allows teams to scale automation more efficiently.
Runner ownership and management
When a Step Runner is shared, the source workspace retains ownership and full administrative control over the runner configuration.
Destination workspaces can use the runner to execute workflow steps, but they cannot modify the runner settings. This ensures that runner configuration remains centrally managed while still allowing multiple workspaces to consume the same execution environment.
Resource utilization considerations
Workflows running on shared Step Runners consume the resources of the original runner instance in the source workspace. Because multiple workspaces may execute workloads on the same runner, resource usage can increase significantly.
If too many workflows run concurrently across shared environments, runner resources may become exhausted. This can impact execution performance and may cause workflow steps to fail. Organizations should plan runner capacity accordingly when enabling cross-workspace sharing.
Audit and visibility
When a Step Runner is shared with another workspace, the event is recorded in the Audit Logs of the source workspace.
Prerequisites
Before sharing Step Runners across workspaces, ensure the following requirements are met:
Cross-workspace collaboration enabled: Contact Torq Support to enable cross-workspace sharing and review the applicable licensing options.
Required roles: Users must have the Workspace Owner or Workflow Builder role.
Required permission: The role must include the
resource.sharescope.Automatic approval condition: If the user sharing the runner is also an Owner in the destination workspace, the share request is accepted automatically.
Manual approval condition: Otherwise, the destination workspace owners receive an email requesting that they review and approve the shared runner.
How to use
The following sections explain how to share Step Runners, review share requests, and remove shared runners.
Share a Step Runner
Perform the following steps in the source workspace. You can also automate this process using the Create Share Request step.
Open runners: In Torq, navigate to Integrations > Runner in the source workspace.
Locate the runner: Find the Step Runner you want to share.
Open options: Click the three-dot (...) menu for the runner.
Share the runner: Select Share.
Select destination workspace: Choose the workspace you want to share the runner with.
Confirm sharing: Click OK to submit the share request.
Accept a share request
When a Step Runner is shared with your workspace, the workspace owners receive an email notification.
Open the request: In the email notification, click Review Step Runner. This opens the Step Runners page in Torq.
Review the runner: Examine the runner details and confirm it is appropriate for your workspace.
Approve or deny: Decide whether to accept or deny the shared runner.
Confirm availability: Once accepted, the Step Runner becomes immediately available for workflow execution in the destination workspace.
(Optional) Automate decisions: Use the Accept Share Request or Deny Share Request steps to automatically process share requests.
Remove shared Step Runners
You can remove a shared Step Runner from the destination workspace if it is no longer needed.
Open runners: In Torq, go to Integrations > Runner in the destination workspace.
Locate the runner: Find the shared Step Runner you want to remove.
Open options: Click the three-dot (...) menu for the runner.
Remove the runner: Select Remove shared runner.
Notify source workspace: An email is sent to the source workspace owners informing them that the runner was removed.
To automatically revoke or remove runner sharing, use the Remove Runner Sharing step.