For AI agents: a documentation index is available at https://docs.coverbase.com/llms.txt. This page is also available in markdown by appending .md to the URL.
This guide is part of the User Guides collection. It is for admins who test configuration in a sandbox before it reaches production. What each setting does is covered in Configuring your data model and Admin and setup.
Before you start
- Start from the sandbox. Promotion is available only in an organization whose status is Sandbox. The left navigation shows a Sandbox badge when you are in one.
- Be an Admin in both organizations. You need the Admin role in the sandbox and in the production organization you promote to. Members of the sandbox cannot promote, whatever their role in production.
- Production only. You can promote to an active production organization. Proof of concept organizations and other sandboxes cannot receive a promotion.
Promote your configuration
1
Open Promote configuration
In the sandbox, go to Configuration → Organization → Promote configuration.
2
Choose the destination
Pick the production organization in Promote to. Organizations you cannot promote to are listed with the reason, such as You need to be an admin there.
3
Review the changes
Coverbase compares the two organizations and lists every area that differs, with how many items are new and how many are updated. Expand an area to see each item. An updated item shows each changed value, with the current production value struck through and the sandbox value beside it.
4
Choose what to include
Every area with changes is included by default. Clear the checkbox on an area to leave it out of this promotion. You can promote it later.
5
Promote
Select Promote, check the summary in the confirmation, and select Promote to your production organization. Changes take effect in production straight away.
What a promotion carries
Items are matched by name, not by internal ID, because the two organizations never share IDs. An item with the same name in both is compared field by field. An item only in the sandbox is added.
Promotion never deletes anything in production. Settings production has that the sandbox lacks are kept. An updated control set archives the version it replaces.
What is not copied
- Records. Vendors, services, assessments, findings, contracts, engagements and every other record stay where they are.
- People and access. Members, user groups, roles and single sign-on are managed in each organization. With SCIM provisioning, your identity provider provisions each organization separately.
- Vendor-specific scoping on detectors. A detector limited to named vendors arrives without that list, because those vendors exist only in the sandbox. The review marks these detectors.
- Radar sources. A detector that reads from a source production does not have is marked Some of its Radar sources aren’t set up there. Set the source up in production, then promote again.
- Integrations, API keys, webhooks and secrets. Credentials never leave the organization they were created in.
If something changes while you review
The review is a snapshot. If anyone changes either organization between your review and your promote, Coverbase refuses the promotion and shows Something changed since you reviewed it. The review reloads with the current differences. Check them and promote again. Nothing is written until the review you confirm matches both organizations.Troubleshooting
Related
Configuring your data model
What each setting a promotion carries does.
Admin and setup
The full setup sequence for a new organization.
Permissions and roles
The Admin role you need in both organizations.
Identity and access
How SSO and SCIM provision people into each organization.