Configuration bundle reference
This page lists what a configuration file (bundle) carries when you export the configuration of an installation or of one project, and what it never carries.
This page is generated from the product code; do not edit by hand.
What the file carries
Section titled “What the file carries”The file holds one part per kind, in the order an import creates them: each kind refers only to kinds above it.
| Kind | File part | What it holds |
|---|---|---|
| System policies | system.json |
Appearance policy; Sign-in policy (authenticator rule); Station policy; AI settings; AI providers; Email settings |
| Customers | customers.json |
Customers |
| People | people.json |
People: name, email, system role, account expiry and profile |
| Teams | teams.json |
Teams; Team members; Project roles of teams |
| Projects | projects.json |
Projects; Quality settings of each project |
| Environments | environments.json |
Environments |
| Workloads | workloads.json |
Workloads (repositories); Which workloads run on which environments; Test accounts that workloads need |
| Variables | variables.json |
Variables (the current version) |
| Profile overrides | profile-overrides.json |
Profile overrides (the current version) |
| Test accounts | test-accounts.json |
Test accounts |
| Secrets | secrets.json |
Secrets: names always, values only on request |
| Run grants | run-grants.json |
Run grants on restricted environments |
| Gate policies | gates.json |
Gate policies; Gate rules |
| Checklist templates | checklist-templates.json |
Release checklist templates |
| Integrations | integrations.json |
Integration credentials (Jira, Teams); Jira settings; Teams channels; Notification rules |
| Report schedules | report-schedules.json |
Report schedules |
What the file never carries
Section titled “What the file never carries”What happened (history) never moves with the configuration:
- AI diagnoses and summaries
- Assistant conversations
- Daily figures
- Data resets
- Environment health and incidents
- Environment locks and test account leases
- Error signatures and failure groups
- Gate evaluations and readiness assessments
- Investigations
- Jira issue links
- Notifications
- Quarantine entries and proposals
- Records of purged runs
- Releases, cycles, decisions, approvals, checklists and evidence
- Report snapshots and share links
- Requirements (they have their own CSV import)
- Risks
- Run files (reports, traces, videos, screenshots)
- Runs
- Test debt history
- Test results and attempts
- The audit log
- The test catalog
- Triage labels
- Usage figures
- Workload revisions (they come back from the repository)
What belongs to one installation stays there:
- AI usage records
- Announcements
- Delivery log of integrations
- Personal settings and notification preferences
- Saved views
- Sign-in sessions
- Sites
- Station enrolment codes and requests
- Stations
- Visit counters of share links
- Secret values are in the file only when you tick Include secret values. They are encrypted with a passphrase of at least 16 characters. Without it, the file carries the names only.
- A project export leaves out the system policies; they move only with the whole installation.
- A file is at most 10 MB. The download link works for 60 minutes, and the Console keeps an export or an uploaded file for 10 hours.
- How to export and import: Move or copy the configuration.