> For the complete documentation index, see [llms.txt](https://docs.phocassoftware.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.phocassoftware.com/other-information/feature-releases.md).

# Feature releases

Learn about how we roll out new features and what to expect when we make changes.

To help you get more value from your data, we continuously improve our product by releasing new features and enhancing existing ones. To ensure a smooth rollout and the best possible experience, we sometimes use feature gates to control the release of certain features.

## Release notes

Release notes are your go-to source for understanding what’s changed in Phocas. They summarize what’s new and improved and often include screenshots or links to the related documentation where you can get more detailed information.

We publish release notes regularly, so keep an eye on the [Release notes](https://docs.phocassoftware.com/other-information/release-notes.md) page to stay up to date with changes.

### Why you might not see a feature right away

If a new feature is mentioned in release notes or documentation but you don’t see it yet in your Phocas site, it might be behind a feature gate (explained below). In most cases, the feature will be released to your site once it’s been fully tested and is ready for broader use.

### Early access and beta features

Some features are available on a limited number of customer sites before a wider release. You might see this described as **early access** or **beta**.

Features in early access or beta have met the quality and security requirements that apply to all Phocas production products. During early access or beta, functionality might change based on feedback. A feature might also be withdrawn or never reach general release.

In some cases, you can opt in or request access. If you're interested in a specific feature, contact your Customer Success representative.

## Feature gates

A feature gate (also known as a feature flag) is a tool that allows us to control who has access to a specific feature and when. Instead of releasing a new feature to everyone all at once, we can:

* Gradually roll it out to a small group of users first (phased rollout).
* Turn a feature on or off for specific users, teams, or customer groups.
* Collect early feedback to improve a feature before making it more widely available.

This approach helps us ensure that features are stable, useful, and aligned with your needs before they are fully released.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.phocassoftware.com/other-information/feature-releases.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
