> ## Documentation Index > Fetch the complete documentation index at: https://docs.domino.ai/llms.txt > Use this file to discover all available pages before exploring further. # Configuration for Apps > The feature flags and configuration records that control App identity propagation, Dataset mounting, per-Project limits, and routing. These feature flags and configuration records control identity propagation, Dataset access, and limits for every App in the deployment. An administrator changes them for the whole deployment. | Setting | Type | Purpose | | :- | :- | :- | | `SecureIdentityPropagationToAppsEnabled` | Feature flag | Sends a limited-scope JSON Web Token (JWT) with each request so the App can verify the viewer. Required for deep linking, session affinity, and [extended identity propagation](https://docs.domino.ai/cloud/platform-capabilities/core-concepts/apps/identity.md#extended-identity). Also changes the URL path Apps are served under, so Apps must read their base path from `DOMINO_RUN_HOST_PATH`. | | `com.cerebro.domino.apps.extendedIdentityPropagationToAppsEnabled` | Configuration record | Lets Apps that opt in receive a full-scope token and [act as the viewer](https://docs.domino.ai/cloud/platform-capabilities/core-concepts/apps/identity.md#extended-identity). Requires `SecureIdentityPropagationToAppsEnabled`. Enabled by default. | | `com.cerebro.domino.dataset.mountingEnabledInApps` | Configuration record | Whether Datasets mount inside App containers or are reachable only through the Dataset API. | | `com.cerebro.domino.apps.maxAppsPerProject` | Configuration record | How many Apps a Project can hold. The default is `10` and administrators can raise it. | | `com.cerebro.domino.apps.maxActiveAppRunsPerProject` | Configuration record | How many App instances can run at once per Project. The default is `4` and administrators can raise it. This counts running App instances, not viewers. Preview instances don't count. | | `com.cerebro.domino.apps.autoscaledExecutionPvcName` and `com.cerebro.domino.apps.autoscaledExecutionPvcNamesForRemoteDataPlanes` | Configuration records | The shared volume autoscaled App pods use for temporary storage and Project files, on the local Data Plane and per remote Data Plane. An administrator sets the remote map before autoscaled Apps run there. | | `com.cerebro.domino.apps.autoscaledExecutionPvcName` and `com.cerebro.domino.apps.autoscaledExecutionPvcNamesForRemoteDataPlanes` | Configuration records | The shared volume autoscaled App pods use for temporary storage and Project files, on the local Data Plane and per remote Data Plane. An administrator sets the remote map before autoscaled Apps run there. | | `com.cerebro.domino.apps.autoscaledExecutionPvcName` and `com.cerebro.domino.apps.autoscaledExecutionPvcNamesForRemoteDataPlanes` | Configuration records | The shared volume autoscaled App pods use for temporary storage and Project files, on the local Data Plane and per remote Data Plane. An administrator sets the remote map before autoscaled Apps run there. | | `com.cerebro.domino.apps.autoscaledExecutionPvcName` and `com.cerebro.domino.apps.autoscaledExecutionPvcNamesForRemoteDataPlanes` | Configuration records | The shared volume autoscaled App pods use for temporary storage and Project files, on the local Data Plane and per remote Data Plane. An administrator sets the remote map before autoscaled Apps run there. | | `EnableAppsSDLC` | Feature flag | Separates creating, publishing, and deploying an App, and enables Draft Apps, App Preview, and versions. On by default. When off, **Publish App** creates and deploys in one step. | ## Routing and `SecureIdentityPropagationToAppsEnabled` When the flag is `true`, Domino hosts Apps at `https:///apps//` instead of a path built from the Project owner, Project name, and run ID. Defaults by version: | Domino version | Default | Notes | | :- | :- | :- | | Cloud Release 90 and later | `true` | All Apps should use `DOMINO_RUN_HOST_PATH`. | | 6.3.0 and later (self-managed) | `true` | All Apps should use `DOMINO_RUN_HOST_PATH`. | | Earlier releases | `false` | Migrate to `DOMINO_RUN_HOST_PATH` before enabling the flag. | An App that builds its own path keeps running until its next restart, then fails. [Migrate an App that builds its own path](https://docs.domino.ai/cloud/platform-capabilities/core-concepts/apps/develop-and-test#migrate-an-app-that-builds-its-own-path) has the fix. ## Related * [Identity](https://docs.domino.ai/cloud/platform-capabilities/core-concepts/apps/identity.md): What each identity level gives your code. * [Who the App runs as](https://docs.domino.ai/cloud/platform-capabilities/core-concepts/apps#who-the-app-runs-as): Why an App acts as its publisher by default. ## Related topics - [Audit Trail Data Glossary](https://docs.domino.ai/cloud/platform-capabilities/features/governance/audit-trail/audit-trail-glossary.md) - [Apps](https://docs.domino.ai/cloud/platform-capabilities/core-concepts/apps/index.md) - [Identity for Apps](https://docs.domino.ai/cloud/platform-capabilities/core-concepts/apps/identity.md) - [Configuration records](https://docs.domino.ai/cloud/admin/architecture-and-deployment/deployment-configuration/configuration-records.md)