Production, staging, development
Every deployment is labeled development, staging, or production. The label organizes config, credentials, and analytics — it does not change runtime behavior by itself.
Environment purposes
Section titled “Environment purposes”| Label | Typical use |
|---|---|
| development | Local or internal testing, localhost allowed domains |
| staging | Pre-release QA, client UAT, load tests |
| production | Live visitor traffic |
Recommended setup
Section titled “Recommended setup”| Resource | Pattern |
|---|---|
| Assistants | Clone prod → staging for safe prompt edits |
| Credentials | Separate keys per environment — never prod keys on staging |
| Deployments | One widget + one API deployment per environment |
| Tools | Point staging tools at sandbox API base URLs |
Creating environments
Section titled “Creating environments”- Duplicate or create assistants for non-prod work.
- Create deployments with the correct Environment field.
- Use distinct deployment IDs in embed code per site.
Analytics and logs
Section titled “Analytics and logs”Filter analytics, tool logs, and audit feed by environment to avoid mixing test traffic with production metrics.
Promotion workflow
Section titled “Promotion workflow”- Test assistant + tools in staging deployment.
- Validate rich content and JWT if used.
- Publish prompt/config changes to production assistant or swap deployment assistant link.