Browse docs

App Release Workflow

Under Settings → App Release Process, you define which steps an app version must go through before reaching the Release status. Without a configured process, any user with the App Reviewer permission can release a version directly.

Creating Release Steps

A release process consists of any number of freely sortable steps. Each step supports the following settings:

  • Name and description
  • Type:
    • Standard – a regular release step.
    • Arrange release date – adds a date-arrangement step to the version (see below).
  • Responsible person or group: If none is set, the app owner is automatically responsible.
  • Enforce this step: When enabled, the version must go through this step and cannot be set to Release directly by an App Reviewer.
  • Conditions: A step can be restricted to specific apps, app types (native/store/web link), platforms, paid/free apps, specific operations (create/update), or exclusively to requested apps.

A step that already has versions assigned to it can no longer be edited.

Arrange Release Date

If the process includes a step of type Arrange release date, the uploader and the responsible person jointly propose a release date in the app’s version detail view. Only once both sides agree is the version automatically published on the agreed date.

Activating/Deactivating the Process

The entire release process can be activated or deactivated via the 3-dot menu:

  • Activate: All versions in Review status are moved into the first matching release step. If a version was already in a step before, its release history is restored. Activation is only possible once at least one step has been created.
  • Deactivate: Any user with the App Reviewer permission can release versions directly again.

See also Processing App Requests → for reviewing requested apps afterward.