Environments
Before your agreement goes live to real users, you can test it in a safe, isolated environment. Propper Click provides three environments — Development, Staging, and Production — each completely separate from the others. Deployments, sessions, evidence, and analytics recorded in one environment are never mixed with another.
Screenshot: click-env-switcher, screenshot of the environment pill in the top nav bar, open, showing DEVELOPMENT / STAGING / PRODUCTION options
Choosing the right environment
| Environment | When to use it |
|---|---|
| Development | While your team is first integrating the Click API and testing locally |
| Staging | For internal review, legal or compliance sign-off, or QA before launch |
| Production | Your live site — all real user interactions are recorded here |
You can have the same published template deployed in all three environments at once. This is useful when you want to verify a new version in Staging before promoting it to Production.
Screenshot: click-env-deployments-all, screenshot of the Deployments list showing the same template deployed in Development, Staging, and Production rows, each with its own environment badge
Typical workflow
- Deploy to Development while your team sets up the API integration.
- Deploy to Staging for internal review or compliance sign-off.
- Deploy to Production once approved and ready to go live.
Switching environments in the dashboard
Your active environment is shown as a badge in the top navigation bar. Click it to switch. All deployments, templates, evidence, and analytics will filter to whichever environment you're viewing.
Screenshot: click-env-dashboard-filtered, screenshot of the dashboard after switching to Staging, showing that the deployments list, analytics counts, and evidence records all reflect Staging data only
Matching your backend to the environment
Each deployment belongs to one environment and has its own ID. Your backend must use the ID of the deployment in the environment it is running against — a Staging build that renders a Production deployment ID records real acceptances. Keep one deployment ID per environment in your backend's configuration.
Next: Domain & Path Configuration →