> For the complete documentation index, see [llms.txt](https://docs.jentis.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.jentis.com/jentis-dcp-elements/account-settings/account-types-beta-and-stable.md).

# Account Types: Beta & Stable

At JENTIS, accounts can be either **BETA** or **STABLE**, depending on whether you prefer early access to new features or a fully production-ready experience. This page explains each account type, how it impacts your experience, and how to request a change.

## BETA Accounts <a href="#beta-accounts" id="beta-accounts"></a>

Accounts on **BETA** have **early access to new features** before they are released to all customers. This allows you to explore the latest capabilities and innovations as soon as they become available.

Features typically appear in BETA accounts around two weeks before they are released to all STABLE accounts. However, in some cases, certain features might remain in BETA for longer before being fully rolled out to all customers on STABLE.

The most reliable source to track the availability of features for each account type is the [JENTIS Changelog](/support-resources-and-product-updates/release-notes-and-changelog.md).

## STABLE Accounts <a href="#stable-accounts" id="stable-accounts"></a>

Accounts on **STABLE** have access only to fully tested features with **general availability**. This option is recommended if you prefer a more stable setup with thoroughly tested features.

## How to Identify Your Account Type <a href="#how-to-identify-your-account-type" id="how-to-identify-your-account-type"></a>

We’ve made it easier to understand which version of the JENTIS DCP you’re working with. Your account’s channel — such as Beta or Stable — is clearly shown inside the platform on the top left corner.&#x20;

<figure><img src="https://2315305008-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fy15ncufYr341K5U8q6Of%2Fuploads%2FXrBQyjfYQaWlO46IJk7v%2Fimage.png?alt=media&amp;token=9e93e6d1-7265-42a3-adf1-b681f6f3c00d" alt=""><figcaption></figcaption></figure>

### How to Change Your Account Type <a href="#how-to-change-your-account-type" id="how-to-change-your-account-type"></a>

If you'd like to switch between BETA and STABLE, contact our team via the [Helpdesk](https://jentis.atlassian.net/servicedesk/customer/portal/1/group/-1).

Our team will review your request and help you change your account type.


---

# 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.jentis.com/jentis-dcp-elements/account-settings/account-types-beta-and-stable.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.