Deploying Agreements
Once you have a published template, you deploy it to make it live on your website. A deployment connects your agreement to a domain, path and environment, and controls when your backend can render and accept it.
Screenshot: click-deployment-activate, screenshot of the Active toggle being switched on for a deployment in the list, with the status changing from inactive to active
The deployment workflow
Every deployment follows the same steps:
- Create — Choose a published template, record the domain and path it is used for, and select an environment. The deployment is saved but not yet live.
- Activate — Turn the deployment on. Your backend can render and accept it immediately.
- Monitor — Views, acceptances, and declines are tracked automatically. No setup required.
- Update — Swap the template, change settings, or deactivate at any time without touching your code.
Only one deployment can be active for the same domain, path, and environment at a time. If you activate a new deployment where one already exists, the previous one is automatically deactivated.
In this section
| Page | What you'll learn |
|---|---|
| Environments | How to use Production, Staging, and Development safely |
| Domain & Path Configuration | What the domain and path on a deployment mean |
| A/B Testing | Testing two versions of an agreement side by side |
| Scheduled Deployments | Automatically going live or expiring at a set time |
Troubleshooting
Activating a new deployment deactivated my previous one. This is expected. Only one deployment can be active per domain, path, and environment combination. Activating a new deployment at the same location automatically deactivates the previous one. If you need both to run simultaneously, use different paths — or use A/B Testing to run two variants of the same agreement side by side.
Start here: Environments →