Use feature flags to control which Domino functionality is available to users. Feature flags are categorized as follows:
- User-Scoped Overrides
-
Flags in this section override the values set in the Deployment Global section.
NoteYou cannot override all flags at the user level. Therefore, this section doesn’t list all feature flags. - 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. |
Feature Flag | Default Value | Category | Description | ||
---|---|---|---|---|---|
| |||||
| Deployment Global | Allow app publishing. Set to | |||
| |||||
| User-Scoped Overrides Deployment Global | Apps host web applications and dashboards. When this flag is set to | |||
| |||||
| Deployment Global | The content security policy allows Domino web apps to access specific whitelisted external resources like images and APIs. This flag is set to See Identify Resources to Whitelist for more information. | |||
| |||||
| Deployment Global | This flag is set to When set to
| |||
| |||||
| User-Scoped Overrides | When | |||
| |||||
| User-Scoped Overrides Deployment Global | 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 | |||
| |||||
| Deployment Global | 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 | |||
| |||||
| User-Scoped Overrides Deployment Global | Enable custom metrics notification API.
See | |||
| |||||
| User-Scoped Overrides Deployment Global | You can use the Domino endpoint feature to publish a model. When | |||
| |||||
| User-Scoped Overrides Deployment Global | When | |||
| |||||
| User-Scoped Overrides Deployment Global | Use Scheduled Jobs to plan jobs in advance and execute them on a regular cadence.
When | |||
| |||||
| Deployment Global | 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. | |||
| |||||
| Deployment Global | Enables the Exports page and related functionality. See Export to Sagemaker and Export to NVIDIA , Export to NVIDIA, and Use Models in Snowflake Queries for more information about exports. | |||
| |||||
| Deployment Global | Domino retrieves CPU and memory statistics from Prometheus. If something is wrong with Prometheus, the Jobs dashboard and Workspaces might run slowly. Set this flag to | |||
| |||||
| Deployment Global | Domino retrieves GPU and memory statistics from Prometheus. Metrics are populated to Prometheus from Nvidia DCGM. If something is wrong with Prometheus, the Jobs dashboard and Workspaces might run slowly. Set this flag to | |||
| |||||
| Deployment Global | When | |||
| |||||
| User-Scoped Overrides Deployment Global | 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 Understand your cluster settings. | |||
| |||||
| User-Scoped Overrides Deployment Global | Enables support for Dask clusters in workspaces. See On-demand Dask. | |||
| |||||
| User-Scoped Overrides Deployment Global | Prevents users from creating classic Domino File System (DFS) based projects. See Projects for more about DFS projects.
| |||
| |||||
| User-Scoped Overrides Deployment Global | When false, the async Domino endpoints feature is disabled so users cannot publish async Domino endpoints. See Model Publishing. | |||
| |||||
| Deployment Global | Enables cost budgets and alerts. Requires an Enterprise license. See Analyze costs for an example. | |||
| |||||
| Deployment Global | Enables multi-account storage support for datasets; see Set Up Multiple Storage Accounts for complete instructions. | |||
| |||||
| No longer supported. | ||||
| |||||
| User-Scoped Overrides Deployment Global | When | |||
| |||||
| User-Scoped Overrides | Enables the integration of External Data Volumes (EDV) with Domino.
| |||
| |||||
| User-Scoped Overrides Deployment Global | Allows users to create Git-based projects (GBP). See Git-based Projects.
| |||
| |||||
| User-Scoped Overrides Deployment Global | Allows users to search for and switch branches in their Git repositories in a workspace. When set to | |||
| |||||
| User-Scoped Overrides Deployment Global | Enables the Dataset functionality.
| |||
| |||||
| User-Scoped Overrides Deployment Global | If using GitHub or GitLab PAT, allows users to create a Git repository when creating a Git-based project. See Create a Git-based Project. | |||
| |||||
| Deployment Global | If this is set to | |||
| |||||
| Deployment Global | From the Workspaces page, the user can click History. If this flag is enabled, the user will see the Workspace History with a tab that lists commits and a tab that lists Sessions. On the Commits tab, the user can hold their mouse over a row. At the end of the row, they can click Open to create a workspace from the commit. When the new workspace is created, a new branch is also created. This is referred to as reproducing a workspace. If this is disabled, the user sees a list of Workspace Sessions. | |||
| |||||
| User-Scoped Overrides Deployment Global | Allows users to use the application to resolve merge conflicts when syncing to a Git repository. When set to | |||
| |||||
| Deployment Global | Set to | |||
| |||||
| User-Scoped Overrides Deployment Global | When | |||
| |||||
| User-Scoped Overrides Deployment Global | Allows users to select a branch, commit, tag, or custom Git reference when importing a Git repository. When set to | |||
| |||||
| Deployment Global | 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 Import Git Repositories. | |||
| |||||
| Deployment Global | 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. | |||
| |||||
| User-Scoped Overrides Deployment Global | 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 Jobs. | |||
| |||||
| User-Scoped Overrides Deployment Global | If | |||
| |||||
| User-Scoped Overrides Deployment Global | When set to | |||
| |||||
| User-Scoped Overrides Deployment Global | 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 Set your cluster settings. | |||
| |||||
| User-Scoped Overrides Deployment Global | Enables support for Ray clusters in workspaces. See On-demand Ray. | |||
| |||||
| Deployment Global | When
| |||
| |||||
| Deployment Global | ||||
| |||||
| User-Scoped Overrides Deployment Global | No longer supported. Do not change the default value. | |||
| |||||
| User-Scoped Overrides Deployment Global | 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 Understand your cluster settings. | |||
| |||||
| User-Scoped Overrides Deployment Global | Enables support for Spark clusters in workspaces. See On-demand Spark. | |||
| |||||
| Deployment Global | 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. | |||
| |||||
| Deployment Global | Enables the model deployments to AWS SageMaker feature. See REST API Reference. | |||
| |||||
| Deployment Global | Enables the new Domino Home page. When set to | |||
| |||||
| Deployment Global | Enables the use of Bearer Authentication for Domino Endpoints (formerly Model APIs), disables existing Basic Authentication, will require restarting running Domino Endpoints. |