Agency workspaces

Workspaces are available on the Agency plan only. The Solo plan provides a single workspace; the Free plan provides a single workspace; the Agency plan provides unlimited workspaces. See limits reference for the per-plan matrix.

A workspace is the permission boundary. Each workspace has its own:

• Forms (zero shared between workspaces).
• Slack webhook URLs (stored encrypted, scoped to the workspace).
• Routing rules (per form, per workspace).
• Delivery log (queryable only by workspace members).
• Failure-alert configuration and recipient list.
• Teammate list (one teammate can be in multiple workspaces).

Three roles, scoped per workspace.

• Admin. Full read-write on the workspace. Can edit forms, rules, webhooks, recipients, and add/remove teammates. The user who creates the workspace is the initial admin.
• Editor. Read-write on forms, rules, and templates. Cannot add or remove teammates, rotate webhooks, or change billing-scope settings.
• Viewer. Read-only. Can see forms, the delivery log, and alert configuration. Cannot edit anything. Useful for inviting clients into their own workspace without giving them admin control.

Billing is at the account level, not the workspace level. The Agency plan's flat monthly fee covers the entire account regardless of workspace count or response volume across them.

• One Agency subscription per account.
• Workspaces don't have per-workspace billing surfaces, the client doesn't see invoicing in their workspace.
• For per-client invoicing, run your own billing system; RouteForms doesn't mediate it.

The canonical setup, for an agency adding a new client:

1. Create a workspace named after the client.
2. Add the client's Slack webhook URL (or create a new one in their workspace and paste it).
3. Add the client's Google Form; install the Apps Script.
4. Configure routing rules per the client's playbook.
5. Optionally invite the client as a Viewer so they can see their own delivery log.
6. Set the failure-alert recipients to include both an agency teammate and the client's ops contact.

A workspace can be archived rather than deleted. Archived workspaces stop processing incoming submissions (the form's Apps Script continues to fire, it lives in the client's Google account — but RouteForms ignores the inbound). Delivery log history is retained for the plan's retention window.

Un-archiving restores the workspace with no reconfiguration required. Deletion is permanent and removes all forms, rules, and log history; use deletion only when the client relationship is definitively over.

• Google Forms → Slack integration
• Failure alerts, recipient resolution inside workspaces
• Security, workspace isolation in the threat model
• Limits, per-plan workspace count and Agency caps