Cloud V2 for Administrators
- New Features
- Searching With Coveo Cloud
- Administration Console
- Coveo Cloud Security
- Management of Security Identities and Item Permissions
- Coveo Cloud V2 SAML SSO
- Troubleshooting Querying Issues
- IPs to Whitelist
- Coveo Index Items
- Supported File Formats
- Indexing by Reference
- Leverage Many Coveo Indexes
- About Non-Production Organizations
- Interface Editor
- Application Change Control Process
About Non-Production Coveo Cloud Organizations
It is strongly advised against going live with a non-production organization, even for projects outside your main use case, such as intranets.
At Coveo, we gradually rollout features on organizations, respecting the following order based on the organization license type: trial, sandbox, and then production. We run tests on our own organizations and only rollout features on the customer trial organizations if the tests reveal no issues. We repeat that process until features are released in all customer production organizations.
A sandbox organization allows you to test new features and configuration changes before integrating them into your production organization.
Minimized Operational Risk
Limit the disruptions to your production organization, which ensures more stability to your live environment.
Developers can work around the constraints of a production organization. They do not fear to cause downtimes in production while implementing changes into the sandbox.
Index sandbox instances containing fake or test data on your sandbox organizations.
Limiting the data you retrieve from production instances on your sandbox organizations prevents unnecessary load on your production servers. Moreover, you do not have to give developers access to production data.
Depending on the number of teams working on Coveo or Coveo-related projects in your company, the number of recommended sandbox differs:
Number of team or project Number of recommended sandbox 1 1 2+ 2
Having two sandbox organizations allows a company to have three environments: development, QA/user acceptance testing (UAT), and production.
Have a development strategy involving at least one sandbox.
When you have one sandbox, your development strategy could look like the following:
- Develop features and resource configurations on the sandbox.
- Test changes.
- Schedule a release date.
- Migrate the changes in the production organization.
Determine the users granted access to the sandbox organization, i.e., developers.
- Having a sandbox organization allows you to limit the access in your production organization to only the team in charge of deployments.
- Developers should only have read-only access in production.
Non-production organizations come with:
Less powerful infrastructure
No redundancy and high availability
- Sandbox organizations and production organizations are not covered by the same service level agreements (SLAs).
- The Coveo Cloud Ops team always prioritizes production organizations during incidents.
- Performances tests are not allowed on sandboxes (see Can I Conduct a Performance Test on Coveo?).
Other Differences With Production Organizations
The following table highlights license differences between production and non-production organizations.
|Difference||Production organization||Non-production organization|
|Minimum number of indexes1||2||1|
Note 1: The number of indexes for each organization is optimized for performance and redundancy.
Note 2: Alert escalation for incidents are delayed.
Note 3: Full index backups are kept 60 days compared to 30 days for regular ones (see About Coveo Cloud V2 Organization Backups).