--- title: "Beta Features Policy" slug: "beta-features-policy" description: "Learn about beta features in Pigment, their development stage, expectations, and how your feedback shapes their evolution before general availability." updated: 2026-09-02T13:10:50Z published: 2026-09-02T13:10:50Z canonical: "kb.pigment.com/beta-features-policy" --- > ## Documentation Index > Fetch the complete documentation index at: https://kb.pigment.com/llms.txt > Use this file to discover all available pages before exploring further. # Beta Features Policy You'll sometimes see a feature in Pigment labeled **beta**. This page explains what that means, so you know what to expect before you rely on a beta feature. ## What does beta mean? Beta means a feature is functional and ready to try, but still under active development. It hasn’t yet gone through the same level of hardening, testing, and stabilization as a generally available (GA) feature. Beta is where we validate a feature with real customers and real use cases before launching to the general public. ## What to expect from a beta feature - **Things can break.** Bugs, rough edges, and occasional instability are expected at this stage. - **Standard support SLAs don’t apply.** Our team is actively involved and will help however we can, but response times and fixes aren’t guaranteed the way they are for GA features. Documentation may be less comprehensive than it is for GA features, and may change as the feature evolves. - **Behavior, permissions, and APIs may change, sometimes without advance notice**, as we act on what we learn during the beta period. A workflow that works today may need adjusting before general availability. - **What you build on a beta feature may not continue to work.** Beta features can change in ways that aren’t backward compatible. That means workflows, configurations, integrations, or other things you build during beta may need to be changed or rebuilt as the feature evolves. In some cases, there may not be a way to preserve or restore the previous behavior. - **You’re welcome to use beta features as they are made available.** Many customers do. However, we recommend not making a beta feature the single point of failure for anything business-critical until it reaches general availability. - **Feedback shapes what ships.** Beta is when your input has the most influence on the final feature. If something breaks, feels off, or is missing, let us know. - **Beta features are usually available at no additional cost during the beta period.** If pricing applies at general availability, we will communicate that before the feature reaches GA. ## How to get access to a beta feature Access to beta features varies. Some are enabled automatically for all customers, while others require opt-in through your account team or a workspace setting. If you see a beta feature mentioned in a release note or announcement and it is not yet available in your workspace, reach out to your account team to check eligibility and enable it. ## How to give feedback on a beta feature Some beta features will have their own community group or feedback channel, and when available, that is the fastest way to reach the team working on it directly, report issues, and see what other customers are building or running into. If there isn’t a dedicated group for a given feature, reach out to your account team and they’ll route your feedback to the right team. ## Beta vs. Early Access You may also see features described as **early access**. At Pigment, early access refers to *who can use a feature*, since it has been made available to a limited set of customers or partners ahead of a wider rollout. Beta refers to *the state of the feature itself*, meaning how stable, tested, and finalized it is. In practice, a feature is often both: available to a limited early access group, and still in beta while we refine it. A feature can also move out of early access (opened up to all customers) while still being labeled beta, if it’s stable enough for broader use but not yet finalized. ## What comes after beta When a feature is ready, it moves to **general availability (GA)**: available to all applicable customers, covered by standard support SLAs, and regular feature release and improvement cycles. Any known issues from beta are expected to be resolved, or explicitly called out as known limitations, by the time a feature reaches GA. ## What happens if a beta feature does not reach GA? In rare cases, we may decide not to bring a beta feature to general availability. If that happens, we will give advance notice and work with affected customers to transition away from the feature. We will not remove a beta feature without warning.