Tray Platform / Accounts / Workspaces / Overview

Overview

Intro to Workspaces

Tray's Workspaces feature allows you to further divide your Organization into subsections.

When your Tray account is initially created, access is granted to two default workspaces - Organization and Personal:

workspaces-dropdown-full

Every user has their own Personal workspace, accessible only to them.

While the Organization workspace contains workflows and authentications that other members have shared with the entire organization.

Additional Workspaces can be created and used to sub-divide your organization, to however suits your business needs. For example by:

  • company department (sales, marketing, HR etc.)

  • project units

  • teams

  • implementation types (Data syncing, ETL etc.)

This gives you the power to separate how and with whom you share workflows and authentications.

Creating workspaces

When in the Organization workspace, Org Owners and Admins can click on their profile, and add new workspaces as per your Org requirements:

workspace-list

Sandbox Workspaces

When you create a workspace it is possible to specify that it is a 'Sandbox':

sandbox-create-new-workspace

Sandbox workspaces can be used for test/development environments.

Any shared or org workspace can be turned into a sandbox.

You can also create unlimited sandbox workspaces.

Crucially, you will not be charged for any activity in your sandbox workspaces (according to Tray.io's acceptable use policy and subject to audit).

A complete list of your sandbox/test/production entities can be seen in the usage page.

Also note that that, for sandboxes, certain key features are limited / throttled, so sandbox workspaces will not be suitable for use with production data:

  • 72h log retention limit (all execution logs will be deleted after 72h)
  • Low concurrent execution limits
  • Additional concurrency limits are applied to our 30 most common connectors
  • Task cap of 30,000 tasks per month per workflow

Sandboxes are also used according to Tray.io's acceptable use policy and subject to audit.