# Beta features ### Overview The beta program gives your workspace early access to features that are actively being developed and refined. When beta features are enabled, your workspace receives access to all current beta-tier functionality as a single package — there are no per-feature toggles. Participation is optional and entirely reversible. Enabling or disabling beta features will not break your existing workspace configuration or affect your data. {% hint style="warning" %} **Beta features may change without notice.** Behavior, availability, and interfaces are subject to change at any time during the beta period. Features are not guaranteed to reach general availability in their current form. {% endhint %} *** ### Features Currently in Beta The following features are available to workspaces with beta features enabled. This list is updated alongside the release notes as features are added or promoted to GA. {% hint style="success" %} **NEW IN BETA** **Simplified Chats: Groups and DMs, now in one chat space** The sidebar now combines Groups and DMs into a unified Chat section.
**Why it matters:** This UX improvement makes messaging feel more streamlined, organized, and easier to navigate. {% endhint %} {% hint style="info" %} On rare occasions, major features may have their own individual flag rather than being included in the package — this will be noted clearly in the release notes. {% endhint %} ### Enabling Beta Features Only workspace admins can enable or disable the beta program. The setting is found in your workspace's general settings. 1. Navigate to **Workspace Settings → Advanced** 2. Toggle **Turn on beta features** to the on position 3. Confirm the prompt acknowledging that beta features may change without notice
Once enabled, beta features are available to all members of the workspace. Individual users cannot opt in or out independently — access is controlled at the workspace level. {% hint style="info" %} Changes to the beta toggle may take some time to propagate across your entire workspace. Members may not see the update simultaneously — ask your team to refresh if access appears inconsistent. {% endhint %} ### What to Expect #### Stability Beta features have cleared internal review but may still contain rough edges. They do not carry the same reliability guarantees as GA features. #### Changes without notice Because beta is a pre-release environment, we may update, replace, or remove features at any point. We won't always be able to give advance warning. If a feature is removed, your workspace will simply revert to GA behavior — no data or configuration will be lost. #### Documentation Beta features are documented in-product and noted in release notes with a `new in beta` tag. They do not receive full standalone documentation until they reach general availability. #### Support Beta features are supported on a best-effort basis. If you encounter a bug or unexpected behavior, please report it through the standard feedback channel — your reports directly influence whether a feature makes it to GA. {% hint style="success" %} Found a problem with a beta feature? Submit feedback directly in-product using the **Share feedback** option in the feature itself, or contact support with `[BETA]` in your subject line. {% endhint %} ### Release Notes When new beta features are available, they'll be noted in the release notes. There are no separate announcements — keep an eye on the release notes to stay current. Features in beta are tagged inline so they're easy to identify. Examples of how beta features appear in release notes: `New in Beta` AI-assisted table generation in documents — available to workspaces with beta features enabled `New in Beta` Inline comment threads on shared views — available to workspaces with beta features enabled `Now in GA` AI-assisted table generation — previously in beta; now available to all workspaces with full docs When a feature graduates from beta to GA, it becomes available to all workspaces automatically with full documentation and standard support. ### Opting Out You can turn off beta features at any time using the same toggle in workspace settings. When you opt out: * Beta features are immediately hidden from all workspace members * No data created or modified with beta features will be deleted * Workspace settings and permissions are unaffected * You can re-enable beta features at any time without consequence {% hint style="warning" %} If your team has been actively using a beta feature, disabling access may disrupt in-progress workflows. Communicate the change to your team before opting out. {% endhint %} ### FAQ **Can individual members opt into beta without admin action?** No. Beta access is controlled exclusively at the workspace level by workspace admins. Individual members cannot enable or disable beta independently. *** **Can I choose which beta features to enable?** Not currently. The toggle enables all current beta features as a package. Occasionally, large or high-impact features may have their own individual flag — this will be noted clearly in the release notes for that feature. *** **Will I lose data if a beta feature is removed?** No. Removing a feature from beta affects access to the UI or functionality, not the underlying data. Any content created via a beta feature is retained. *** **Is there a cost to participate in the beta program?** Beta features are included in your existing plan at no additional cost. *** **How will I know when a beta feature is promoted to GA?** Promotions are announced in the release notes with a **Now in GA** tag. Once promoted, the feature is available to all workspaces without any action needed, and full documentation is published. --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.glue.ai/release-notes/beta-features.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.