> ## Documentation Index
> Fetch the complete documentation index at: https://docs.e6data.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Version selection and admin guide

> How workspace administrators select versions, refresh the available-version list, enable products, and grant upgrade permissions.

This guide is for workspace administrators. It covers how versions are selected, how to refresh the available-version list, how product visibility depends on feature enablement, and the permissions involved. For where each part of the platform is upgraded, see [The three upgrade surfaces](/platform/upgrades#the-three-upgrade-surfaces); for step-by-step procedures, see [Product and cluster upgrades](/platform/upgrades/product-and-cluster-upgrades).

## How versions are selected

The platform separates the **list of available versions** (published by e6data and synced to your workspace automatically) from **what you choose to run**. You select a version on a cluster, a product row, or the Platform Components section, and the platform carries out the rollout.

* **Clusters** take a version every time you create one (newest pre-selected); change it later by editing the cluster.
* **Products** already have a version by the time they appear - the Metadata Service starts on the newest available version, and optional products are created on the latest version when you enable their feature. The **Version Upgrades** tab is for *changing* that version.

## Refreshing the version list

New versions appear in the dropdowns automatically as e6data publishes them and your workspace syncs. If you've been told a new version is available and don't see it yet, force an immediate refresh:

* On the cluster **Version** field, use the **refresh** control next to the dropdown. This pulls the latest published versions immediately, then re-opens the list.

<Info>
  A refresh only updates the list of available versions. It does not change, upgrade, or restart anything that's running.
</Info>

## Feature enablement and visibility

The products shown in **Version Upgrades** depend on which features are enabled in your workspace:

* The **Metadata Service** is always available.
* Optional products appear only when their feature is enabled.

Features are turned on and off in **Settings → Feature Enablement**. A product that isn't enabled won't appear as an upgradeable row.

## Permissions

Upgrade actions are gated by access control. If a person's role doesn't grant the required access, the relevant control is unavailable to them. Every workspace has three built-in roles - **Admin**, **Manager**, and **Viewer**:

| Upgrade action | Admin | Manager | Viewer |
| - | :-: | :-: | :-: |
| View available versions (clusters, products, platform) | ✅ | ✅ | ✅ |
| Create a cluster / change a cluster's version | ✅ | ✅ | ❌ |
| View *or* upgrade products (the Version Upgrades view) | ✅ | ❌ | ❌ |
| View platform releases | ✅ | ✅ | ✅ |
| Deploy or roll back a platform release | ✅ | ❌ | ❌ |

In short:

* **Admin** - full access to every upgrade action.
* **Manager** - can create clusters and change cluster versions, and can view platform releases, but cannot deploy or roll back platform releases, and cannot see or use the product Version Upgrades view.
* **Viewer** - read-only; can see available versions and platform releases but cannot upgrade or deploy anything, and cannot see the product Version Upgrades view.

<Info>
  The product Version Upgrades view is Admin-only. Product version upgrades are read through a permission (`versions:read` / `versions:upgrade`) that no built-in role except Admin holds. The **Settings** menu and Version Upgrades area are reachable by any role, but for a non-Admin the product list there won't load - only an Admin (or a custom role granting `versions:read`) can view and use it. Platform releases in the same area *are* visible to Manager and Viewer; only *deploying* one is restricted.
</Info>

## See also

* [Product and cluster upgrades](/platform/upgrades/product-and-cluster-upgrades) - the upgrade procedures.
* [Rollbacks, failure modes, and recovery](/platform/upgrades/rollbacks-and-recovery) - what happens during a rollout.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.