Feature release stages
Atomic releases some features ahead of general availability so that customers can use them early and help shape them. These features are labeled beta or preview in the documentation and in the Workbench.
Both labels indicate that a feature is still evolving. They differ in who can access the feature: a beta feature is available to everyone, while a preview feature is enabled on request.
Beta
A beta feature is available to all Workbench users, but is still subject to change and may not be ready for production use.
Key characteristics:
- Generally available access: every organization can use the feature without any additional configuration by Atomic.
- Subject to change: behavior, configuration options, and interfaces may change before the feature reaches general availability.
- Production readiness: if you have any concerns about depending on a beta feature in production, check with Atomic before you do so.
Beta features are a good fit when you want to adopt new functionality early and are comfortable adjusting to changes as the feature matures.
Preview
A preview feature has the same characteristics as a beta feature, and may not be available to all organizations. It is an early access stage that comes before beta.
Key characteristics:
- Limited access: the feature is enabled per organization, so it may not be visible in your Workbench. Contact us to have it enabled.
- Subject to change: as with beta, behavior, configuration options, and interfaces may change.
- Production readiness: as with beta, check with Atomic first if you have concerns about using the feature in production.
Preview features are the earliest stage at which a feature is documented, and the point at which your feedback has the most influence on its direction.
Comparing release stages
| Preview | Beta | General availability | |
|---|---|---|---|
| Available to all organizations | Enabled on request | Yes | Yes |
| Subject to change | Yes | Yes | - |
| Check with Atomic before production use | Yes | Yes | - |
| Documented | Yes | Yes | Yes |
Identifying beta and preview features
Where a feature or a section of a feature is in beta or preview, the documentation shows a banner at the top of the relevant section naming the feature and its stage. Some features are also marked in the Workbench itself.
A feature may carry more than one label. For example, a feature can be both premium and beta, meaning it is part of a paid plan and still subject to change.
Giving feedback
Feedback during these stages directly shapes what a feature looks like when it reaches general availability. Contact us to provide feedback on a beta or preview feature, to ask whether a particular feature is ready for your production use case, or to request access to a preview feature.