> ## 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.

# Feature flags

Use feature flags to control which Domino functionality is available to users.

You can change feature flags in the Admin Portal by choosing **Platform Settings** > **Feature Flags**.

Feature flags are categorized as follows:

* **User-Scoped Overrides**\
  Flags in this section override the values set in the Deployment Global section.

  <Note>
    You cannot override all flags at the user level. Therefore, this section doesn’t list all feature flags.
  </Note>

* **Deployment Global**\
  Flags in this section override Domino’s system default value.

* **Default**\
  If no value is set for the flag in the Deployment Global section, then Domino uses a system default value.

<Tip>
  When you change the value of a feature flag, you do not have to restart the server.
</Tip>

<table>
  <thead>
    <tr>
      <th>Feature Flag</th>
      <th>Default Value</th>
      <th>Category</th>
      <th>Description</th>
    </tr>
  </thead>

  <tbody>
    <tr>
      <td colSpan="4"><p><code>AppPublishingEnabled</code></p></td>
    </tr>

    <tr>
      <td />

      <td><p><code>true</code></p></td>
      <td><p>Deployment Global</p></td>
      <td><p>Allow app publishing. Set to <code>false</code> to disable the <strong>Anyone, including anonymous users</strong> and <strong>Anyone with an account access permissions</strong>. See <a href="/6.3/platform-capabilities/core-concepts/products/apps#Domino-App-features">Grant Access to Domino Apps</a> for more information about these permissions.</p></td>
    </tr>

    <tr>
      <td colSpan="4"><p><code>EnableApps</code></p></td>
    </tr>

    <tr>
      <td />

      <td><p><code>true</code></p></td>
      <td><p>User-Scoped Overrides</p> <p>Deployment Global</p></td>
      <td><p>Apps host web applications and dashboards. When this flag is set to <code>true</code>, users can publish apps from inside a project, view a list of globally discoverable apps, view apps to which they have access, and view apps in the Assets dashboard. When this flag is set to <code>false</code>, users cannot publish, access, or run any apps (including Apps shared with them) though apps remain visible (but unopenable) in the Assets dashboard. See <a href="/6.3/platform-capabilities/core-concepts/products/apps#Publish-an-app">Publish a Domino App</a>.</p></td>
    </tr>

    <tr>
      <td colSpan="4"><p><code>EnableContentSecurityPolicyForApps</code></p></td>
    </tr>

    <tr>
      <td />

      <td><p><code>false</code></p></td>
      <td><p>Deployment Global</p></td>
      <td><p>The content security policy allows Domino web apps to access specific whitelisted external resources like images and APIs.</p> <p>This flag is set to <code>false</code> by default which allows all requests to all resources. Set this flag to <code>true</code> to block requests to resources that are not whitelisted and allow requests to whitelisted resources.</p> <p>See <a href="/6.3/platform-capabilities/core-concepts/products/apps/authentication-and-identity/whitelist-resources">Identify Resources to Whitelist</a> for more information.</p></td>
    </tr>

    <tr>
      <td colSpan="4"><p><code>EnabledNewEndpointsView</code></p></td>
    </tr>

    <tr>
      <td />

      <td><p><code>true</code></p></td>
      <td><p>Deployment Global</p></td>
      <td><p>Enable new consolidated endpoints view (combining regular ML models and Gen AI models).</p></td>
    </tr>

    <tr>
      <td colSpan="4"><p><code>EnableDownloadingSupportBundle</code></p></td>
    </tr>

    <tr>
      <td />

      <td><p><code>true</code></p></td>
      <td><p>Deployment Global</p></td>
      <td><p>This flag is set to <code>true</code> by default which allows non-admins to download <a href="/6.3/help/support-bundle">Support Bundles</a> if they are the owner of the Project.</p> <p>When set to <code>false</code>, the following changes take place:</p> <ul> <li><p>Disables the support button in Workspace detail’s <strong>Support Tab</strong>.</p></li> <li><p>Hides the support bundle row in the Job details.</p></li> <li><p>Hides the support bundle row in the App details.</p></li> </ul></td>
    </tr>

    <tr>
      <a id="enableInWorkspaceBranchSelection" />

      <td colSpan="4"><p><code>enableInWorkspaceBranchSelection</code></p></td>
    </tr>

    <tr>
      <td />

      <td><p><code>false</code></p></td>
      <td><p>User-Scoped Overrides</p></td>
      <td><p>Enable branch selection within workspaces for Git code repositories. When <code>true</code>, users can select which files to commit in Git-based projects. By default, this is turned off and Domino commits all changes to the project. See <a href="/6.3/platform-capabilities/core-concepts/workspaces/use-git-in-your-workspace">Use Git in your Workspace</a>.</p></td>
    </tr>

    <tr>
      <td colSpan="4"><p><code>EnableLaunchers</code></p></td>
    </tr>

    <tr>
      <td />

      <td><p><code>true</code></p></td>
      <td><p>User-Scoped Overrides</p> <p>Deployment Global</p></td>
      <td><p>Launchers are simple web forms that allow you to run templatized scripts. By default, from inside a project, users can publish a Launcher, view and use Launchers to which they have, and can view apps in the Assets dashboard. When <code>false</code>, users cannot publish a Launcher from inside the project. See <a href="/6.3/platform-capabilities/features/launchers">Launchers</a>.</p></td>
    </tr>

    <tr>
      <a id="enablelegacyjwt" />

      <td colSpan="4"><p><code>EnableLegacyJwtTooling</code></p></td>
    </tr>

    <tr>
      <td />

      <td><p><code>false</code></p></td>
      <td><p>Deployment Global</p></td>
      <td><p>Indicates whether to use the API Proxy or expose a (legacy) JWT access token in the container to authenticate users to the Domino API. If <code>true</code>, Domino starts the periodic refresh process and delays the run start until the first token is acquired and propagated. The token is mounted as a file into the run container. The API Proxy process is also running. If <code>false</code>, only the API Proxy process is running, the token is not refreshed periodically, and it’s not mounted into the run. <strong>This legacy JWT tooling behavior will be deprecated in upcoming Domino versions.</strong></p></td>
    </tr>

    <tr>
      <td colSpan="4"><p><code>EnableMetricAlertsApi</code></p></td>
    </tr>

    <tr>
      <td />

      <td><p><code>true</code></p></td>
      <td><p>User-Scoped Overrides</p> <p>Deployment Global</p></td>
      <td><p>Enable custom metrics notification API. See <code>/api/metricAlerts/v1</code> in the <a href="/6.3/reference/api/domino-open-api#_sendMetricAlert">Domino Platform API reference</a> for more information.</p></td>
    </tr>

    <tr>
      <td colSpan="4"><p><code>EnableModelAPIs</code></p></td>
    </tr>

    <tr>
      <td />

      <td><p><code>true</code></p></td>
      <td><p>User-Scoped Overrides</p> <p>Deployment Global</p></td>
      <td><p>You can use the Domino endpoint feature to publish a model. When <code>false</code>, the Domino endpoints feature is disabled so the user cannot publish Domino endpoints. See <a href="/6.3/platform-capabilities/features/model-deployment">Model Publishing</a>.</p></td>
    </tr>

    <tr>
      <td colSpan="4"><p><code>EnableModelMonitoringForModelAPIs</code></p></td>
    </tr>

    <tr>
      <td />

      <td><p><code>true</code></p></td>
      <td><p>User-Scoped Overrides</p> <p>Deployment Global</p></td>
      <td><p>When <code>false</code>, this hides the Monitoring tab in the Domino endpoint. When <code>true</code>, the user can monitor their Domino endpoint. See <a href="/6.3/platform-capabilities/features/monitoring/5-use-monitoring/index">Use Monitoring</a>.</p></td>
    </tr>

    <tr>
      <td colSpan="4"><p><code>EnableNetAppVolumesAsDatasources</code></p></td>
    </tr>

    <tr>
      <td />

      <td><p><code>true</code></p></td>
      <td><p>Deployment Global</p></td>
      <td><p>Enables access to Domino NetApp Volumes as Data Sources. See <a href="/6.3/platform-capabilities/core-concepts/data/netapp-volumes">Work with NetApp Volumes</a>.</p></td>
    </tr>

    <tr>
      <td colSpan="4"><p><code>EnableScheduledJobs</code></p></td>
    </tr>

    <tr>
      <td />

      <td><p><code>true</code></p></td>
      <td><p>User-Scoped Overrides</p> <p>Deployment Global</p></td>
      <td><p>Use Scheduled Jobs to plan jobs in advance and execute them on a regular cadence. When <code>false</code>, the Scheduled Jobs feature is disabled so users cannot use this feature in a project. However, they can still see Scheduled Jobs from the Assets Portfolio. See <a href="/6.3/platform-capabilities/core-concepts/jobs/schedule-a-job">Scheduled Jobs</a> and <a href="/6.3/platform-capabilities/core-concepts/projects/work-with-project-assets">See the Assets for Your Project</a>.</p></td>
    </tr>

    <tr>
      <td colSpan="4"><p><code>enableSelectFileSync</code></p></td>
    </tr>

    <tr>
      <td />

      <td><p><code>true</code></p></td>
      <td><p>Deployment Global</p></td>
      <td><p>When a user is in a workspace and has made changes to multiple files, this flag activates the Select and Sync button so users can select the files that they want to commit and Sync to Git. This only happens when workspace comes from a project created as a Git project, not a Domino File System (DFS) project.</p></td>
    </tr>

    <tr>
      <td colSpan="4"><p><code>ExportsWorkflowEnabled</code></p></td>
    </tr>

    <tr>
      <td />

      <td><p><code>true</code></p></td>
      <td><p>Deployment Global</p></td>
      <td><p>Enables the Exports page and related functionality. See <a href="/6.3/platform-capabilities/core-concepts/products/models/deploy-sagemaker">Export to Sagemaker</a> and <a href="/6.3/platform-capabilities/core-concepts/products/models/export-nvidia">Export to NVIDIA</a> , <a href="/6.3/platform-capabilities/core-concepts/products/models/export-nvidia">Export to NVIDIA</a>, and <a href="/6.3/platform-capabilities/core-concepts/products/models/snowflake-queries">Use Models in Snowflake Queries</a> for more information about exports.</p></td>
    </tr>

    <tr>
      <td colSpan="4"><p><code>KubernetesContainerMetricsEnabled</code></p></td>
    </tr>

    <tr>
      <td />

      <td><p><code>true</code></p></td>
      <td><p>Deployment Global</p></td>
      <td><p>Domino retrieves CPU and memory statistics from Prometheus. If something is wrong with Prometheus, the <a href="/6.3/platform-capabilities/core-concepts/jobs/monitor-jobs">Jobs dashboard</a> and <a href="/6.3/platform-capabilities/core-concepts/workspaces/launch-a-workspace">Workspaces</a> might run slowly. Set this flag to <code>false</code> to stop retrieving data from Prometheus. The user will see blank values in tables and CPU and memory graphs will not be shown.</p></td>
    </tr>

    <tr>
      <td colSpan="4"><p><code>GpuMetricsEnabled</code></p></td>
    </tr>

    <tr>
      <td />

      <td><p><code>true</code></p></td>
      <td><p>Deployment Global</p></td>
      <td><p>Domino retrieves GPU and memory statistics from Prometheus. Metrics are populated to Prometheus from Nvidia DCGM. If something is wrong with Prometheus, the <a href="/6.3/platform-capabilities/core-concepts/jobs/monitor-jobs">Jobs dashboard</a> and <a href="/6.3/platform-capabilities/core-concepts/workspaces/launch-a-workspace">Workspaces</a> might run slowly. Set this flag to <code>false</code> to stop retrieving data from Prometheus. GPU and GPU memory graphs will not be shown.</p></td>
    </tr>

    <tr>
      <td colSpan="4"><p><code>SecureIdentityPropagationToAppsEnabled</code></p></td>
    </tr>

    <tr>
      <td />

      <td><p><code>true</code></p></td>
      <td><p>Deployment Global</p></td>
      <td><p>When <code>true</code>, Domino Apps receive a token as part of their incoming requests that can be used to identify the requesting Domino user.</p></td>
    </tr>

    <tr>
      <td colSpan="4"><p><code>ShortLived.DaskAutoscalingEnabled</code></p></td>
    </tr>

    <tr>
      <td />

      <td><p><code>true</code></p></td>
      <td><p>User-Scoped Overrides</p> <p>Deployment Global</p></td>
      <td><p>This enables the autoscale features on the Launch New Workspace page so users can set the Auto-scale workers check box and then set a minimum and maximum number of workers. See <a href="/6.3/platform-capabilities/features/compute-clusters-hpc/dask/work-with-your-cluster#dask_cluster_settings">Understand your cluster settings.</a></p></td>
    </tr>

    <tr>
      <td colSpan="4"><p><code>ShortLived.DaskClustersEnabled</code></p></td>
    </tr>

    <tr>
      <td />

      <td><p><code>true</code></p></td>
      <td><p>User-Scoped Overrides</p> <p>Deployment Global</p></td>
      <td><p>Enables support for Dask clusters in workspaces. See <a href="/6.3/platform-capabilities/features/compute-clusters-hpc/dask">On-demand Dask</a>.</p></td>
    </tr>

    <tr>
      <td colSpan="4"><p><code>ShortLived.DisableDFSBasedProjects</code></p></td>
    </tr>

    <tr>
      <td />

      <td><p><code>false</code></p></td>
      <td><p>User-Scoped Overrides</p> <p>Deployment Global</p></td>
      <td><p>Prevents users from creating classic Domino File System (DFS) based projects. See <a href="/6.3/platform-capabilities/core-concepts/projects">Projects</a> for more about DFS projects.</p>&#x20;
      &#x20;<p>If this is set to <code>true</code>, but ShortLived.EnableGitBasedProjects is set to <code>false</code>, new projects cannot be created.</p></td>
    </tr>

    <tr>
      <td colSpan="4"><p><code>ShortLived.EnableAsyncModels</code></p></td>
    </tr>

    <tr>
      <td />

      <td><p><code>true</code></p></td>
      <td><p>User-Scoped Overrides</p> <p>Deployment Global</p></td>
      <td><p>When false, the async Domino endpoints feature is disabled so users cannot publish async Domino endpoints. See <a href="/6.3/platform-capabilities/features/model-deployment/index">Model Publishing</a>.</p></td>
    </tr>

    <tr>
      <td colSpan="4"><p><code>ShortLived.EnableCostBudgetsAndAlerts</code></p></td>
    </tr>

    <tr>
      <td />

      <td><p><code>false</code></p></td>
      <td><p>Deployment Global</p></td>
      <td><p>Enables cost budgets and alerts. Requires an Enterprise license. See <a href="/6.3/admin/operations/finops/3-analyze-costs-API">Analyze costs</a> for an example.</p></td>
    </tr>

    <tr>
      <td colSpan="4"><p><code>ShortLived.EnableCreateSFASnowflakeDataSource</code></p></td>
    </tr>

    <tr>
      <td />

      <td><p><code>false</code></p></td>
      <td><p>Data - Datasource</p></td>
      <td><p>When <code>true</code>, this allows users and admins to create single factor authentication (user/password) data sources. This is an authentication type that Snowflake is deprecating and the feature flag will default to <code>false</code>. You may need to momentarily re-enable SFA data sources for Snowflake as you migrate to the new <code>KeyPair</code> authentication type.</p></td>
    </tr>

    <tr>
      <td colSpan="4"><p><code>ShortLived.EnableDatasetMultiStorageSupport</code></p></td>
    </tr>

    <tr>
      <td />

      <td><p><code>true</code></p></td>
      <td><p>Deployment Global</p></td>
      <td><p>Enables multi-account storage support for datasets; see <a href="/6.3/admin/data-administration/datasets#set-up-multiple-storage-accounts">Set Up Multiple Storage Accounts</a> for complete instructions.</p></td>
    </tr>

    <tr>
      <td colSpan="4"><p><code>ShortLived.EnableDataSources</code></p></td>
    </tr>

    <tr>
      <td />

      <td><p><code>true</code></p></td>

      <td />

      <td><p>No longer supported.</p></td>
    </tr>

    <tr>
      <td colSpan="4"><p><code>ShortLived.EnableDiskUsageVolumeCheck</code></p></td>
    </tr>

    <tr>
      <td />

      <td><p><code>true</code></p></td>
      <td><p>User-Scoped Overrides</p> <p>Deployment Global</p></td>
      <td><p>When <code>true</code>, Domino measures disk usage and makes volume size recommendations when users create new workspaces and jobs.</p></td>
    </tr>

    <tr>
      <td colSpan="4"><p><code>ShortLived.EnableDominoNetAppSnapshotsOnExecutionCompletion</code></p></td>
    </tr>

    <tr>
      <td />

      <td><p><code>false</code></p></td>
      <td><p>Data - NetApp</p></td>
      <td><p>When <code>true</code>, this allows users to programmatically snapshot all the NetApp Volumes that are mounted on a job when that job completes.</p></td>
    </tr>

    <tr>
      <td colSpan="4"><p><code>ShortLived.EnableExternalDataVolumes</code></p></td>
    </tr>

    <tr>
      <td />

      <td><p><code>true</code></p></td>
      <td><p>User-Scoped Overrides</p></td>
      <td><p>Enables the integration of External Data Volumes (EDV) with Domino.</p>&#x20;
      &#x20;<p>Do not set this to <code>false</code> as you will disable functionality.</p></td>
    </tr>

    <tr>
      <td colSpan="4"><p><code>ShortLived.EnableGitBasedProjects</code></p></td>
    </tr>

    <tr>
      <td />

      <td><p><code>true</code></p></td>
      <td><p>User-Scoped Overrides</p> <p>Deployment Global</p></td>
      <td><p>Allows users to create Git-based projects (GBP). See <a href="/6.3/platform-capabilities/core-concepts/projects/manage-git-projects">Git-based Projects</a>.</p>&#x20;
      &#x20;<p>If this is set to <code>false</code> but ShortLived.DisableDFSBasedProjects is set to <code>true</code>, new projects cannot be created.</p></td>
    </tr>

    <tr>
      <td colSpan="4"><p><code>ShortLived.EnableInWorkspaceBranchSelection</code></p></td>
    </tr>

    <tr>
      <td />

      <td><p><code>true</code></p></td>
      <td><p>User-Scoped Overrides</p> <p>Deployment Global</p></td>
      <td><p>Allows users to search for and switch branches in their Git repositories in a workspace. When set to <code>false</code>, users can see the branch name but cannot interact with it. See <a href="/6.3/platform-capabilities/core-concepts/workspaces/use-git-in-your-workspace">Using Git in Your Workspace</a>.</p></td>
    </tr>

    <tr>
      <td colSpan="4"><p><code>ShortLived.EnableReadWriteDatasets</code></p></td>
    </tr>

    <tr>
      <td />

      <td><p><code>true</code></p></td>
      <td><p>User-Scoped Overrides</p> <p>Deployment Global</p></td>
      <td><p>Enables the Dataset functionality.</p>&#x20;
      &#x20;<p>If set to <code>false</code>, all Dataset functionality will be disabled: the Datasets section will be removed from the Data tab, and Datasets cannot be created, accessed, or mounted to executions such as Workspaces and Jobs.</p></td>
    </tr>

    <tr>
      <td colSpan="4"><p><code>ShortLived.EnableRepoCreationInNewProjectModal</code></p></td>
    </tr>

    <tr>
      <td />

      <td><p><code>true</code></p></td>
      <td><p>User-Scoped Overrides</p> <p>Deployment Global</p></td>
      <td><p>If using GitHub or GitLab PAT, allows users to create a Git repository when creating a Git-based project. See <a href="/6.3/platform-capabilities/core-concepts/projects/manage-git-projects/create-a-git-based-project">Create a Git-based Project</a>.</p></td>
    </tr>

    <tr>
      <td colSpan="4"><p><code>ShortLived.EnableUserNotifications</code></p></td>
    </tr>

    <tr>
      <td />

      <td><p><code>true</code></p></td>
      <td><p>Deployment Global</p></td>
      <td><p>If this is set to <code>false</code>, Notifications are hidden from users.</p></td>
    </tr>

    <tr>
      <td colSpan="4"><p><code>ShortLived.EnableWorkspaceReproduction</code></p></td>
    </tr>

    <tr>
      <td />

      <td><p><code>true</code></p></td>
      <td><p>Deployment Global</p></td>
      <td><p>From the Workspaces page, the user can click <strong>History</strong>. If this flag is enabled, the user will see the Workspace History with a tab that lists commits and a tab that lists <strong>Sessions</strong>. On the <strong>Commits</strong> tab, the user can hold their mouse over a row. At the end of the row, they can click <strong>Open</strong> to create a workspace from the commit. When the new workspace is created, a new branch is also created. This is referred to as <a href="/6.3/platform-capabilities/features/monitoring/6-remediation/2-remediate-a-domino-endpoint#reproduce-the-environment">reproducing a workspace</a>. If this is disabled, the user sees a list of Workspace Sessions.</p></td>
    </tr>

    <tr>
      <td colSpan="4"><p><code>ShortLived.EnhancedMergeConflictsEnabled</code></p></td>
    </tr>

    <tr>
      <td />

      <td><p><code>true</code></p></td>
      <td><p>User-Scoped Overrides</p> <p>Deployment Global</p></td>
      <td><p>Allows users to use the application to resolve merge conflicts when syncing to a Git repository.</p> <p>When set to <code>false</code>, a merge conflict with remote will create a new branch with the user’s changes. The user must manually merge the changes onto their original branch. See <a href="/6.3/platform-capabilities/core-concepts/workspaces/use-git-in-your-workspace">Resolve Merge Conflicts</a>.</p></td>
    </tr>

    <tr>
      <td colSpan="4"><p><code>ShortLived.ExternalDataVolumes</code></p></td>
    </tr>

    <tr>
      <td />

      <td><p><code>true</code></p></td>
      <td><p>Deployment Global</p></td>
      <td><p>Set to <code>true</code> so your users can use external data sources (such as hard drives and flash drives). When <code>true</code>, the user can open a project and click Data in the navigation pane. Then, they can click the External Data Volumes tab to add external data volumes to their project and retrieve data from that source. See <a href="/6.3/platform-capabilities/core-concepts/data/external-volumes/use-a-mounted-volume">External Data Volumes</a>.</p></td>
    </tr>

    <tr>
      <a id="ExternalDataVolumesFullCensor" />

      <td colSpan="4"><p><code>ShortLived.ExternalDataVolumesFullCensor</code></p></td>
    </tr>

    <tr>
      <td />

      <td><p><code>false</code></p></td>
      <td><p>User-Scoped Overrides</p> <p>Deployment Global</p></td>
      <td><p>When <code>true</code>, the External Data Volumes section on the Data page shows only those external data volumes that are available to the user. Additional volumes might have been mounted, but will not be listed. If this is set to <code>false</code>, this is considered partial volume censorship and all volumes mounted to the project are listed, but some might be grayed out to refuse a user’s access. See <a href="/6.3/admin/data-administration/external-data/external-data-volumes/configure-censorship">Configure Censorship</a>.</p></td>
    </tr>

    <tr>
      <td colSpan="4"><p><code>ShortLived.GenAI.AiSystemEnablePerformanceTab</code></p></td>
    </tr>

    <tr>
      <td />

      <td><p><code>true</code></p></td>
      <td><p>Deployment Global</p></td>
      <td><p>Enable 'Performance' tab for Agents</p></td>
    </tr>

    <tr>
      <td colSpan="4"><p><code>ShortLived.GenAI.AiSystemEnablePublish</code></p></td>
    </tr>

    <tr>
      <td />

      <td><p><code>true</code></p></td>
      <td><p>Deployment Global</p></td>
      <td><p>Enable Agent Publishing</p></td>
    </tr>

    <tr>
      <td colSpan="4"><p><code>ShortLived.GenAI.EnableEndpointsList</code></p></td>
    </tr>

    <tr>
      <td />

      <td><p><code>true</code></p></td>
      <td><p>Deployment Global</p></td>
      <td><p>Enable Gen AI consolidated endpoints list showing all model types together</p></td>
    </tr>

    <tr>
      <td colSpan="4"><p><code>ShortLived.GenAI.EnableEndpointsListGenAI</code></p></td>
    </tr>

    <tr>
      <td />

      <td><p><code>true</code></p></td>
      <td><p>Deployment Global</p></td>
      <td><p>Enable Gen AI endpoints in the consolidated Gen AI endpoints list</p></td>
    </tr>

    <tr>
      <td colSpan="4"><p><code>ShortLived.GenAI.EnableExperimentRunDropdown</code></p></td>
    </tr>

    <tr>
      <td />

      <td><p><code>true</code></p></td>
      <td><p>Deployment Global</p></td>
      <td><p>Enable Gen AI Experiment Run Actions Dropdown</p></td>
    </tr>

    <tr>
      <td colSpan="4"><p><code>ShortLived.GenAI.EnableExperimentRunDropdownArchive</code></p></td>
    </tr>

    <tr>
      <td />

      <td><p><code>true</code></p></td>
      <td><p>Deployment Global</p></td>
      <td><p>Enable Gen AI Experiment Run 'Archive' option in the Actions Dropdown</p></td>
    </tr>

    <tr>
      <td colSpan="4"><p><code>ShortLived.GenAI.EnableExperimentRunDropdownOpenInWorkspace</code></p></td>
    </tr>

    <tr>
      <td />

      <td><p><code>true</code></p></td>
      <td><p>Deployment Global</p></td>
      <td><p>Enable Gen AI Experiment Run 'Open in Workspace' option in the Actions Dropdown</p></td>
    </tr>

    <tr>
      <td colSpan="4"><p><code>ShortLived.GenAI.EnableTraceAnnotation</code></p></td>
    </tr>

    <tr>
      <td />

      <td><p><code>true</code></p></td>
      <td><p>Deployment Global</p></td>
      <td><p>Enable Gen AI capabilities to do CRUD operations on evaluations</p></td>
    </tr>

    <tr>
      <td colSpan="4"><p><code>ShortLived.GenAI.EnableTraceComparison</code></p></td>
    </tr>

    <tr>
      <td />

      <td><p><code>true</code></p></td>
      <td><p>Deployment Global</p></td>
      <td><p>Enable Gen AI trace comparison</p></td>
    </tr>

    <tr>
      <td colSpan="4"><p><code>ShortLived.GenAI.EnableTraceList</code></p></td>
    </tr>

    <tr>
      <td />

      <td><p><code>true</code></p></td>
      <td><p>Deployment Global</p></td>
      <td><p>Enable Gen AI trace list</p></td>
    </tr>

    <tr>
      <td colSpan="4"><p><code>ShortLived.GenAI.RegisterModelGenAI</code></p></td>
    </tr>

    <tr>
      <td />

      <td><p><code>true</code></p></td>
      <td><p>Deployment Global</p></td>
      <td><p>Enable Gen AI Model Registration</p></td>
    </tr>

    <tr>
      <td colSpan="4"><p><code>ShortLived.GitReferencesCustomizableEnabled</code></p></td>
    </tr>

    <tr>
      <td />

      <td><p><code>true</code></p></td>
      <td><p>User-Scoped Overrides</p> <p>Deployment Global</p></td>
      <td><p>Allows users to select a branch, commit, tag, or custom Git reference when importing a Git repository.</p> <p>When set to <code>false</code>, imported repositories default to the default branch. See <a href="/6.3/platform-capabilities/core-concepts/projects/manage-dfs-projects/import-git-repositories#add-a-repo">Add a repository to a project</a>.</p></td>
    </tr>

    <tr>
      <td colSpan="4"><p><code>ShortLived.GitRepoValidationEnabled</code></p></td>
    </tr>

    <tr>
      <td />

      <td><p><code>true</code></p></td>
      <td><p>Deployment Global</p></td>
      <td><p>Allows automated user validation to Git repositories when a Git-based project is created, imported, or a job or workspace is started. This validation prevents workspaces from failing due to invalid credentials to clone a Git repository. See <a href="/6.3/platform-capabilities/core-concepts/projects/manage-dfs-projects/import-git-repositories">Import Git Repositories</a>.</p></td>
    </tr>

    <tr>
      <td colSpan="4"><p><code>ShortLived.HardwareTierCapacityFetchingEnabled</code></p></td>
    </tr>

    <tr>
      <td />

      <td><p><code>true</code></p></td>
      <td><p>Deployment Global</p></td>
      <td><p>This flag controls whether the time estimate (such as \<1 min and \<7 min) is shown for the Hardware tier on the Project settings page.</p></td>
    </tr>

    <tr>
      <td colSpan="4"><p><code>ShortLived.JobsListAutoUpdateDisabled</code></p></td>
    </tr>

    <tr>
      <td />

      <td><p><code>false</code></p></td>
      <td><p>User-Scoped Overrides</p> <p>Deployment Global</p></td>
      <td><p>Use this flag to turn off auto-update on the Job page to improve job performance. If this is turned off, the user must click the refresh button on the Jobs page to get updates on the information in the Jobs Timeline such as CPU (%), Memory, Duration, Status, and Comments. See <a href="/6.3/platform-capabilities/core-concepts/jobs/monitor-jobs">Jobs</a>.</p></td>
    </tr>

    <tr>
      <td colSpan="4"><p><code>ShortLived.LauncherFileUploadPathEnabled</code></p></td>
    </tr>

    <tr>
      <td />

      <td><p><code>false</code></p></td>
      <td><p>User-Scoped Overrides</p> <p>Deployment Global</p></td>
      <td><p>If <code>true</code>, shows the <strong>Upload file to field</strong> on the New Launcher page when the <strong>Launcher Type</strong> is set to <strong>Upload file(s)</strong>. This lets users set an upload path for the launcher. See <a href="/6.3/platform-capabilities/features/launchers">Launchers</a>.</p></td>
    </tr>

    <tr>
      <td colSpan="4"><p><code>ShortLived.ModelRegistry</code></p></td>
    </tr>

    <tr>
      <td />

      <td><p><code>true</code></p></td>
      <td><p>User-Scoped Overrides</p> <p>Deployment Global</p></td>
      <td><p>When set to <code>false</code>, the Model Registry feature is disabled so users cannot <a href="/6.3/platform-capabilities/core-concepts/products/models/register-and-govern">register and govern their models</a> in the model registry.</p></td>
    </tr>

    <tr>
      <td colSpan="4"><p><code>ShortLived.RayAutoscalingEnabled</code></p></td>
    </tr>

    <tr>
      <td />

      <td><p><code>true</code></p></td>
      <td><p>User-Scoped Overrides</p> <p>Deployment Global</p></td>
      <td><p>This enables the autoscale features on the Launch New Workspace page so users can set the Auto-scale workers check box and then set a minimum and maximum number of workers. See <a href="/6.3/platform-capabilities/features/compute-clusters-hpc/ray/work-with-your-cluster#ray_cluster_settings">Set your cluster settings</a>.</p></td>
    </tr>

    <tr>
      <td colSpan="4"><p><code>ShortLived.RayClustersEnabled</code></p></td>
    </tr>

    <tr>
      <td />

      <td><p><code>true</code></p></td>
      <td><p>User-Scoped Overrides</p> <p>Deployment Global</p></td>
      <td><p>Enables support for Ray clusters in workspaces. See <a href="/6.3/platform-capabilities/features/compute-clusters-hpc/ray">On-demand Ray</a>.</p></td>
    </tr>

    <tr>
      <td colSpan="4"><p><code>ShortLived.RepoclonerImageBuilds</code></p></td>
    </tr>

    <tr>
      <td />

      <td><p><code>true</code></p></td>
      <td><p>Deployment Global</p></td>
      <td><p>When <code>true</code>, the ImageBuilder uses the Repocloner binary to download Domino projects and Git repositories on the build context. Set it to <code>false</code> to use Replicator instead. If <code>true</code>, Replicator access is not required.</p>&#x20;
      &#x20;<p>If your deployment uses Istio, this flag must be set to <code>false</code>; Repocloner is incompatible with Istio.</p></td>
    </tr>

    <tr>
      <td colSpan="4"><p><code>ShortLived.ShowFeatureStore</code></p></td>
    </tr>

    <tr>
      <td />

      <td><p><code>false</code></p></td>
      <td><p>Deployment Global</p></td>

      <td />
    </tr>

    <tr>
      <td colSpan="4"><p><code>ShortLived.ShowV1DataProjects</code></p></td>
    </tr>

    <tr>
      <td />

      <td><p><code>false</code></p></td>
      <td><p>User-Scoped Overrides</p> <p>Deployment Global</p></td>
      <td><p>No longer supported. Do not change the default value.</p></td>
    </tr>

    <tr>
      <td colSpan="4"><p><code>ShortLived.SparkAutoscalingEnabled</code></p></td>
    </tr>

    <tr>
      <td />

      <td><p><code>true</code></p></td>
      <td><p>User-Scoped Overrides</p> <p>Deployment Global</p></td>
      <td><p>This enables the autoscale features on the Launch New Workspace page so users can set the Auto-scale workers check box and then set a minimum and maximum number of workers. See <a href="/6.3/platform-capabilities/features/compute-clusters-hpc/spark/on-demand-spark/work-with-your-cluster">Understand your cluster settings</a>.</p></td>
    </tr>

    <tr>
      <td colSpan="4"><p><code>ShortLived.SparkClustersEnabled</code></p></td>
    </tr>

    <tr>
      <td />

      <td><p><code>true</code></p></td>
      <td><p>User-Scoped Overrides</p> <p>Deployment Global</p></td>
      <td><p>Enables support for Spark clusters in workspaces. See <a href="/6.3/platform-capabilities/features/compute-clusters-hpc/spark/on-demand-spark">On-demand Spark</a>.</p></td>
    </tr>

    <tr>
      <td colSpan="4"><p><code>ShortLived.iFrameRequired</code></p></td>
    </tr>

    <tr>
      <td />

      <td><p><code>true</code></p></td>
      <td><p>Deployment Global</p></td>
      <td><p>Limits external access to Domino Apps via iFrame to decrease the risk of attacks from malicious apps. Changes to this setting apply only to Apps published afterwards.</p></td>
    </tr>

    <tr>
      <td colSpan="4"><p><code>ShortLived.EnableModelDeploymentsApi</code></p></td>
    </tr>

    <tr>
      <td />

      <td><p><code>true</code></p></td>
      <td><p>Deployment Global</p></td>
      <td><p>Enables the model deployments to AWS SageMaker feature. See <a href="/6.3/reference/api/domino-open-api">Domino Platform API reference</a>.</p></td>
    </tr>

    <tr>
      <td colSpan="4"><p><code>ShortLived.DominoHome</code></p></td>
    </tr>

    <tr>
      <td />

      <td><p><code>true</code></p></td>
      <td><p>Deployment Global</p></td>
      <td><p>Enables the new Domino Home page. When set to <code>false</code>, the user sees the Projects page instead of the Domino Home page when they log in.</p></td>
    </tr>

    <tr>
      <td colSpan="4"><p><code>ShortLived.EnableBearerAuthenticationForDominoEndpoints</code></p></td>
    </tr>

    <tr>
      <td />

      <td><p><code>false</code></p></td>
      <td><p>Deployment Global</p></td>
      <td><p>Enables the use of Bearer Authentication for Domino Endpoints (formerly Model APIs), disables existing Basic Authentication, will require restarting running Domino Endpoints.</p></td>
    </tr>

    <tr>
      <td colSpan="4"><p><code>ShortLived.HybridSuppressHelm</code></p></td>
    </tr>

    <tr>
      <td />

      <td><p><code>false</code></p></td>
      <td><p>Deployment Global</p></td>
      <td><p>Suppresses generation of Helm command for Nexus deployment, effectively switching to generate the bootstrap token needed for the new way of installing and registering Data Planes.</p></td>
    </tr>
  </tbody>
</table>
