---
title: "Sealing Presets"
description: "Save sealing options as a named preset in the Developer Console, and reuse it in the sealing wizard or the CLI tool."
---
> For the complete documentation index, see [llms.txt](https://docs.doverunner.com/llms.txt).

A **preset** saves a set of sealing options under a name. Instead of setting every option each time, you apply the preset:

- In the sealing wizard, from the **Preset** selector on the right-hand panel after you upload a file. See [Apply DoveRunner Mobile App Security](https://docs.doverunner.com/mobile-app-security/android/android-sealing/).
- In the CLI tool, with the `sealing_preset_name` option. See [Basic Configuration](https://docs.doverunner.com/mobile-app-security/android/cicd/basic-configuration/#common-options).

Some settings — threat response message templates, Hardware Key Attestation, and Access Signals — have no CLI options. A preset is the only way to apply them when you seal through the CLI.

Open **Android → Preset**. The page title is **Manage Sealing Preset for CLI**.

## Managing Presets

The list shows the presets in your account:

| Column | Description |
| :----- | :---------- |
| **Preset Name** | The name you use to apply the preset. |
| **Created At** | When the preset was created. |
| **Description** | Optional free-text note. |
| **Action** | **View**, **Edit**, **Copy**, or **Delete** the preset. |

Use the search box to find a preset by name.

## Creating a Preset


1. Click **Create Preset**.

2. Enter the **Preset Name** and, optionally, a description. The name can contain only English letters, numbers, `.`, `_`, and `-`.

3. In **Basic Configuration**, select the app framework and the sealing version (both required), then the code protection options.

4. In **General Features**, set the Environment Detection and Tool & Package Detection options.

5. In **Advanced Features**, set the Advanced Detection options. Access Signals is a toggle in this section, rather than a separate step.

6. Click **Save**.


The options and their version requirements are the same as in the sealing wizard — for example, Monitor and Callback actions appear only when the sealing version is 3.3.0.0 or higher. See [Apply DoveRunner Mobile App Security](https://docs.doverunner.com/mobile-app-security/android/android-sealing/) for each option.

**Note:** 
Options that must be enabled for your account, such as Hardware Key Attestation, Customize Threat Response Messages, and Access Signals, are shown in a preset only when they are enabled. To use them, contact the [Help Center](https://support.doverunner.com).


Use **Copy** to create a new preset from an existing one, for example a test and a release variant of the same settings.

## Using a Preset with the CLI Tool

The bottom of the page has a **3rd Party Integration** area, where you can download the CLI tool and check your **CLI Key** (the `authkey` value).

Pass the preset name with `sealing_preset_name`:

```bash
$ java -jar sealing.jar -url https://api.appsealing.com/covault/gw -authkey 123456789ABCDE -srcapk app-release.aab -sealedapk app-release-sealed.aab -sealing_preset_name my-preset-name
```

**Caution:** 
The preset name must match exactly. If no preset with that name exists, sealing fails with exit code 140 — see [Troubleshooting](https://docs.doverunner.com/mobile-app-security/android/cicd/troubleshoot/#preset-not-found). If you pass other sealing options together with a preset, the CLI tool shows the warning `Sealing preset is not stored by using additional sealing options.`


Changing a preset does not change apps that were already sealed with it. Re-seal the app to apply the updated options.