Workspaces and Collections

Automation Hub uses a simple two-level organizational system to keep your automations organized and easy to find:

Workspace

The team, department, environment, or business area

Collection

A group of related automations inside that workspace

Job

One automation that performs a specific task

Simple: choose the workspace, open the right collection, then run or edit the job.

Think of it like organizing your files: Workspace is your main folder, Collections are subfolders, and Jobs are the individual documents inside.

Workspaces

A Workspace is your top-level container. It's typically for a team, department, or business area.

Use Cases for Workspaces

• By Team: Finance team, Operations team, Marketing team
• By Department: HR, Sales, Engineering, Support
• By Environment: Development, Staging, Production
• By Client: If you manage automations for multiple clients

What's in a Workspace?

• Name: Easy-to-remember name for your workspace
• Description: What this workspace is for
• Color: Optional visual identifier to distinguish workspaces
• Collections: The project folders inside this workspace
• Jobs: All the automations you've created

Creating a Workspace

When you first start, you create a workspace. Example:

• "Finance Team" workspace for the finance department
• "Operations" workspace for operational automations
• "DevOps" workspace for infrastructure tasks

Collections

A Collection is a folder within a workspace that groups related jobs together.

Use Cases for Collections

• By Function: "Monthly Reports", "Data Sync", "Alerts"
• By Process: "Employee Onboarding", "Invoice Processing", "Customer Support"
• By Schedule: "Daily Tasks", "Weekly Reports", "Monthly Archives"
• By System: "Salesforce", "SAP", "AWS", "Email"

What's in a Collection?

• Name: What this collection is for
• Description: Details about what automations are in here
• Color: Optional visual identifier
• Jobs: The automations grouped in this collection

Example Structure

Here's how a company might organize their automations:

Finance Team workspace

Finance Team

Monthly Reports

Generate P&L Report
Generate Balance Sheet
Email Reports to Executives

Data Reconciliation

Reconcile Accounts Payable
Reconcile General Ledger
Flag Discrepancies

Operations workspace

Operations

Daily Maintenance

Check System Health
Clean Up Old Logs
Database Backup

Alerts & Monitoring

High Memory Alert
Disk Space Alert
Service Down Alert

In both examples, the workspace tells you who owns the automations, the collection tells you what kind of work they belong to, and each line inside the collection is an individual job.

Organization Best Practices

Keep It Simple

• Start with one workspace if you only have one team
• Add more workspaces only when you need separation

Clear Naming

• Use names that describe the team or purpose
• Example: "Finance Team" instead of "WS-01"

Logical Grouping

• Put related automations in the same collection
• Don't mix unrelated jobs in one collection

Use Collections Wisely

• Group by function or process, not by individual jobs
• Keep the number of collections reasonable (5-10 per workspace is good)

Color Coding

• Use colors to visually distinguish important workspaces or collections
• Makes it easier to find things by sight

Quick Reference

Concept	Purpose	Example
Workspace	Top-level organization	"Finance", "Operations"
Collection	Group related jobs	"Monthly Reports", "Daily Backups"
Job	Individual automation	"Generate Invoice", "Send Alert"

Moving Forward

Once you understand workspaces and collections, you're ready to:

1. Create a workspace for your team or department
2. Create collections to group related automations
3. Create jobs inside collections to perform specific tasks
4. Run and monitor your automations