Running Agent in Different Workspaces

If you need to run agents in multiple workspaces, you do not need to install the agent again on your computer:

1) Simply create a new agent in the additional workspace:

2) Copy the key from the agent in the new workspace:

3) Paste the key from the new agent to the Key field and click Connect:

​

​

The agent will then connect to this workspace, and you can use it in your connections.

• Related Articles

• Account and Workspace Roles in Skyvia

  In Skyvia, we distinguish between account and workspace roles for seamless teamwork: 1. Account Roles The account admin, also known as the account owner, has full control over the account. They can manage subscriptions to Skyvia products, modify ...

• QuickBooks Online: Could not start QuickBooks

  The "Could not start QuickBooks" error may occur if QuickBooks and the Skyvia Agent are running with different user permissions. To avoid this, make sure both applications are launched either as a regular user or as an administrator. If this does not ...

• QuickBooks Desktop: "A modal dialog box is showing in the QuickBooks user interface. Your application cannot access QuickBooks until the user dismisses the dialog box."

  Issue Description When attempting to connect a QuickBooks Desktop company file to Skyvia using Skyvia Agent, you may encounter the following error: Connection to the company could not be established. A modal dialog box is showing in the QuickBooks ...

• How to Check if a Column Supports Native Filtering in Skyvia

  Filtering helps make your integrations and backups faster and lighter by reducing the amount of data Skyvia pulls from your source. However, not all objects and fields support native filtering. If a column doesn’t support native filters, applying a ...

• Replication: Table '...' Schema Validation Failed (Resolving 'Absent Columns' and 'Redundant Columns' Errors)

  If you encounter the following errors in an integration, it means the schema of your data source no longer matches the schema Skyvia has cached: Error: "Integration failed: Table 'TableName' schema validation failed: Absent columns: 'FieldName1', ...