The Deployment Page
Deployment is your workspace’s central command center for packaging, versioning, and distributing automations. From a single unified ledger, you choose whether a workflow runs as an editable Step template or a standalone Form interface, create semantic snapshots, and deploy versions to the public Marketplace or managed client workspaces.
Navigate to Team Assets → Deployment in the left sidebar to manage all published automations across your workspace.
Deploying to Clients? If you manage multi-tenant clients as a consultancy or MSP, Choose a Deployment Method compares this versioned deployment route with the one-client direct Admin Push flow.
Understanding the Deployment Table
The Deployment table lists every publishable workflow in your workspace alongside its active interface type and distribution status:
| Column | What it tells you | Operational Actions |
|---|---|---|
| Interface | How the workflow is consumed: Step or Form. | Click the dropdown to switch interfaces or configure form fields. |
| Automations | The workflow name and internal identifier. | Click the workflow title to open the visual canvas. |
| Author | The workspace member who authored the automation. | Identifies team ownership and maintainers. |
| Last edited | Relative timestamp of the most recent change. | 2h ago, yesterday, 3d ago. |
| Deployed to | Where the workflow is actively published. | Shows Deploy (unpublished), Marketplace badge, or client tenant logos. |
Audit Unpublished Workflows: Read down the Deployed to column to identify completed automations displaying a blue Deploy link. These are workflows that have been built but not yet distributed to users or clients.
Selecting an Interface: Step vs. Form
The Interface control defines how end-users interact with your workflow:
The workflow is distributed as a modular building block. Users fork the full canvas to customize logic or call it as a child Subflow.
Step Interface (Default)The workflow is packaged as a standalone web form. Users input parameters and click Run without seeing canvas steps or credentials.
Form InterfaceSwitch Interface Mode
Click the Interface chip in the table row and select Form or Step.
Configure Form Fields (Form Mode)
If selecting Form on a workflow without configured inputs, click the yellow Settings (⚙️) icon. The form builder drawer opens beside the table, allowing you to select canvas fields, set custom labels, and define validation rules without leaving the Deployment page.
The Versioned Deployment Flow
Clicking Deploy on any workflow row (or selecting Share → Deploy on the visual canvas) opens the two-step deployment modal:
1. Basic Info & Interface Selection
Verify the workflow title and category. Click ✦ Generate descriptions to have Glow analyze your canvas steps and automatically draft a summary using your Glow AI token allowance. Confirm whether the workflow deploys as a Step or Form interface.
2. Version & Target Destination
Select an existing version snapshot or click + New version to create an immutable version tag (e.g. v1.2.0) with release notes. Choose your destination: publish publicly to the Marketplace or push independent draft copies to up to 50 client workspaces.
Credential Isolation During Deployment
Glow’s multi-tenant architecture strictly enforces zero-trust credential boundaries during all deployment operations:
Zero-Trust Credential Isolation: - Zero credential leakage: Host templates never export third-party API tokens, passwords, or OAuth secrets. - Client-owned execution: Target client workspaces receive independent unconfigured steps that execute using the client’s own credentials. - Safe account rebinding: Automatic connection binding happens only when exactly one healthy matching account exists in the target workspace. - Pre-activation review: Workflows arrive in Draft mode so client Admins can review connections before going Live.
- No Credential Leakage: API keys, OAuth tokens, and workspace secrets configured in your agency workspace are stripped automatically during packaging.
- Client Account Binding: When a client workspace activates a deployed workflow, steps automatically bind to existing client connections if exactly one healthy account exists for that service; otherwise, the client Admin selects the appropriate connected account.
What’s Next?
- 👉 Form Templates →: Customize input fields, validation, and pre-filled default values.
- Step Templates: Publish editable canvas blueprints to the Marketplace.
- Choose a Deployment Method: Compare workspace version deployment with direct MSP Admin Push.