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

> ## Agent Instructions
> Cognite Data Fusion (CDF) is an industrial DataOps platform. Prefer English docs unless the user asks for another locale.
> Follow /_llms/ index links recursively until you reach page URLs ending in .md. Fetch those Markdown twins instead of HTML.
> For REST APIs, default to calendar version 20230101 (stable). Use 20230101-beta or 20230101-alpha only if the user is on a preview API. Cite paths under /api-reference/concepts/<version>/ and the Cdf-Version header. Prefer the Python SDK (cognite-sdk) unless the user is in JavaScript/TypeScript.
> Start here by task: platform overview /cdf/index.md; data modeling /cdf/dm/index.md; data integration /cdf/integration/index.md; access /cdf/access/index.md; CDF Toolkit /cdf/deploy/cdf_toolkit/index.md; REST quickstart /dev/quickstart.md; Python SDK https://cognite-sdk-python.readthedocs-hosted.com/en/stable/; Atlas AI /cdf/atlas_ai/index.md; plan an Atlas AI agent /cdf/atlas_ai/concepts/atlas_ai_agent_planning.md; Flows apps /cdf/flows/index.md; MCP and IDE setup /dev/guides/ide_ai_integration.md.
> For implementation work, also load /skill.md.

# About Flows custom app management

> Learn about App management in Cognite Data Fusion (CDF), where you see all versions of your Flows custom apps, publish and activate versions, and check their vulnerabilities.

> [!WARNING]
>
> The features described in this article are in [public preview](https://docs.cognite.com/cdf/product_feature_status.md#public-preview) and may change.

Use App management to control which version of each Cognite Flows custom app users open in the Cognite Data Fusion (CDF) project. You see every version, choose which version to publish and which to activate, and review certification and vulnerabilities. Users then open the version you selected.

Certification decides whether you can publish a version. You review vulnerabilities before you activate, and you ask the builder to fix serious ones. See [Respond to vulnerabilities](#respond-to-vulnerabilities). For how builders create and deploy an app, see [Building Flows custom applications](https://docs.cognite.com/cdf/flows.md).

> [!NOTE]
>
> Each app has only one active version at a time, and that is the version users see in Custom apps.

## Before you start

To use App management, you need the [capabilities to manage Flows custom apps](https://docs.cognite.com/cdf/access/guides/capabilities.md#flows-app-management).

## Open App management

You open App management from the Custom apps page.

**1. Open the Flows workspace**

Sign in to CDF > Flows workspace > Custom apps.

**2. Open App management**

In the top right, select the Manage apps button. If you don't see it, your group doesn't include the [capabilities](https://docs.cognite.com/cdf/access/guides/capabilities.md#flows-app-management) to manage apps.

## Check apps and their versions

On the App management page, you see an overview of all apps in the current project.

| Column name | What it shows |
| - | - |
| Application | The app name and description. |
| Active version | The version users see in Custom apps. |
| Vulnerabilities | Number of vulnerabilities in the active version, by [severity](#severity-levels). |
| Certification | The [certification status](#certification-status) of the active version. |
| Published | The date the active version was published. |

Select Needs attention to view only apps that need action, for example, because of vulnerabilities or a lack of certification.

Select an app to see all of its versions. For each version, you see:

* **Status.** Whether the version is a draft, published, active, deprecated, or archived. See [How version statuses connect](#version-status-flow).
* **Certification status.** Which signatures the version has. See [Certification status](#certification-status).
* **Vulnerabilities.** The packages with vulnerabilities, their severity, whether each package is a runtime dependency or a dev dependency, and the patched package version when one is listed. A runtime dependency is a package the running app needs. A dev dependency is a package used to build the app.
* **Builder signature.** Whether the signature is valid, when it was created, and who created it.

## Manage app versions

Every version has a status, such as draft or active. You change a version's status with version actions. For how builders create, sign, and deploy versions, see [About the Flows custom app lifecycle](https://docs.cognite.com/cdf/flows/concepts/app-lifecycle.md).

### How version statuses connect

The diagram shows how a version moves from one status to another, and which action moves it.

```mermaid theme={"languages":{"custom":["/_languages/kuiper.json"]}}
flowchart LR
    deploy([Builder deploys]) --> draft[Draft]
    draft -- Publish --> published[Published]
    published -- Activate --> active[Active]
    active -- "Deactivate, or another<br/>version is activated" --> published
    published -- Deprecate --> deprecated[Deprecated]
    draft -- Archive --> archived[Archived]
    deprecated -- Archive --> archived
```

A typical version moves through these statuses:

1. **Draft.** A builder deploys a new version. Users don't see it in Custom apps.
2. **Published.** You publish the draft, and the files are locked. Publish a **Certified** version. In a project with [Dev status](https://docs.cognite.com/cdf/flows/guides/dev-status.md), you can publish a **Builder certified** version. Users still don't see the version in Custom apps.
3. **Active.** You activate the published version. It replaces the previous active version, which goes back to **Published**. Users now see this version in Custom apps.
4. **Deprecated.** Deprecate a published version when you no longer want anyone to activate it. If that version is active, deactivate it first.  Deprecating is permanent.
5. **Archived.** Archive a draft or deprecated version to keep it for audits. You can't activate an archived version.

> [!TIP]
>
> To try an app yourself, select Open app to run the active version, or Open version to open a specific version. Opening a version doesn't change what users see.

## Publish and activate a version

After a builder deploys a new version, it arrives as a draft. Users keep the current active version until you activate the new one.

**1. Find the app**

On App management, search for the app. A new app shows **No active version** until you activate one.

**2. Check the draft**

Select the app, then select the draft. Check its [certification status](#certification-status) and [vulnerabilities](#vulnerabilities).

**3. Publish the version**

Select Publish.

**4. Activate the version**

Select Activate to replace the current active version for all users.

**5. Confirm the result**

In the list on App management, check that the active version is the one you activated.

To roll back, activate an earlier published version. In production, that version is Cognite-certified. In a project with [Dev status](https://docs.cognite.com/cdf/flows/guides/dev-status.md), it can be builder-signed. Leave the version as it was published. See [Roll back to a published version](https://docs.cognite.com/cdf/flows/guides/deploying.md#roll-back-to-a-published-version).

## Certification status

The certification status shows which signatures a version has, and that status decides where you can publish it. For how a builder gets the signatures, see [Certifying a Flows custom app for production](https://docs.cognite.com/cdf/flows/guides/application-certification.md).

| Certification status | [Signing state](https://docs.cognite.com/cdf/flows/concepts/app-lifecycle.md#version-states) | What it means for you |
| - | - | - |
| Not certified | Unsigned | The version has no signatures yet. You can't publish it. |
| Builder certified | Builder-signed | The version has the builder's signature. |
| Certified | Cognite-certified | The version has the builder's signature and Cognite's signature. |

You can publish a **Builder certified** version only in a project with [Dev status](https://docs.cognite.com/cdf/flows/guides/dev-status.md). In every other project, including production, you publish a **Certified** version. Until Cognite certifies a builder-signed version, users see a 14-day warning, except in projects with Dev status.

You can publish a **Certified** version in the project that the signatures cover, including production.

You activate a version only after you publish it. The builder adds a signature to a **Not certified** version before you can publish it. See [About the Flows custom app lifecycle](https://docs.cognite.com/cdf/flows/concepts/app-lifecycle.md).

## Check vulnerabilities

In the app list, vulnerability counts apply only to the active version. To check another version, select it.

### Severity levels

Each vulnerability has a severity that shows how much harm it could cause if someone exploited it. The severity comes from a score from 0 to 10 in the [Common Vulnerability Scoring System (CVSS) v3](https://www.first.org/cvss/v3.1/specification-document), an industry standard for rating vulnerabilities.

| Severity | CVSS score |
| - | - |
| Critical | 9.0–10.0 |
| High | 7.0–8.9 |
| Medium | 4.0–6.9 |
| Low | 0.1–3.9 |

Severity doesn't tell you whether a vulnerability is easy to exploit, or whether attackers already exploit it. Look first at vulnerabilities that are known to be exploited.

### Respond to vulnerabilities

* **Before you activate a version,** check its vulnerabilities. If it has critical or high vulnerabilities in runtime dependencies, ask the builder to fix them first.
* **If the active version has critical vulnerabilities,** activate a newer published version that fixes them. If there isn't one, contact the builder. If a patched package version is listed, ask the builder to update that package and deploy a new version that you then publish and activate.
* **If you need to stop users from opening an app right away,** deactivate the active version. Users can't open the app until you activate another version.

## Further reading

* [Custom apps](https://docs.cognite.com/cdf/explore/custom_apps.md) — Where users open the active version.
* [Building Flows custom applications](https://docs.cognite.com/cdf/flows.md) — How builders create and deploy an app.
* [About the Flows custom app lifecycle](https://docs.cognite.com/cdf/flows/concepts/app-lifecycle.md) — Draft, published, signing, and rollback.
* [Deploying Flows custom apps](https://docs.cognite.com/cdf/flows/guides/deploying.md) — Deploy a version to a CDF project.
* [App management capabilities](https://docs.cognite.com/cdf/access/guides/capabilities.md#flows-app-management) — Capabilities you need to manage Flows custom apps.
* [Certifying a Flows custom app for production](https://docs.cognite.com/cdf/flows/guides/application-certification.md) — Certify a version before production publish.
