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

# App Settings Overview

> Let merchants configure your app from the Dodo Payments dashboard. Declare settings fields in a manifest, and read the saved values with the API or the app.settings.updated webhook.

> [!WARNING]
>
> App settings are in development. They are not yet available in production, and details can change before release.

## What app settings are

App settings let a merchant configure your app inside Dodo Payments. You describe the fields in a JSON manifest. Dodo Payments shows a **Configure** tab for each installation of your app, checks the values, and stores them for that installation.

Your app does not need its own settings screen. It reads the saved values with its installation token and gets a webhook after each change.

> [!NOTE]
>
> App settings are part of the [App Marketplace](https://docs.dodopayments.com/developer-resources/build-an-app.md). They are available to businesses that have the `app_marketplace` feature enabled.

## How it works

**1. Upload a manifest**

You upload a manifest for your app. See the [manifest reference](https://docs.dodopayments.com/developer-resources/apps/app-settings/manifest-reference.md).

**2. Review, when needed**

Most changes go live at once. Some changes need review, for example a new required field. See [which changes need review](https://docs.dodopayments.com/developer-resources/apps/app-settings/manifest-reference.md#changes-that-need-review).

**3. The merchant fills the Configure tab**

The merchant opens the installation and saves the values. Only an owner or an admin can save. Members can read the values, but never the secrets.

**4. Your app reads the settings**

Dodo Payments sends the [`app.settings.updated` webhook](https://docs.dodopayments.com/developer-resources/apps/app-settings/settings-webhook). Your app then calls the [settings API](https://docs.dodopayments.com/developer-resources/apps/app-settings/read-settings.md) to read the current values and secrets.

## Key facts

* Settings belong to one installation. A live installation and a test installation have separate values.
* A merchant can install your app before they fill the settings. Missing required values do not block the installation. The app page shows **Action needed** instead.
* Secret fields are encrypted. The merchant can write them, but the dashboard never shows them again.
* The API is read only. Your app cannot write settings.

## Pages in this section

> [card] [Manifest reference](https://docs.dodopayments.com/developer-resources/apps/app-settings/manifest-reference.md)
>
> Field types, limits, versions, and review.

> [card] [Read settings](https://docs.dodopayments.com/developer-resources/apps/app-settings/read-settings.md)
>
> Call the API with an app access token.

> [card] [Settings webhook](https://docs.dodopayments.com/developer-resources/apps/app-settings/settings-webhook.md)
>
> Handle the app.settings.updated event.

> [card] [Dynamic options](https://docs.dodopayments.com/developer-resources/apps/app-settings/dynamic-options.md)
>
> Fill a select field from your own server.


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