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

The Configuration record is where all global settings for a Domino installation are listed.

1. Go to the *Admin* portal.

2. Click **Platform settings > Configuration records**.

3. On the **Configuration records** page, you can:

   * Click an existing record to edit its attributes.

   * Click **Add Record** to create a new setting. If no record is created in the application, the system uses the default value.

     You must [restart the Domino services](#restart-services) for changes to take effect.

     <Warning>
       Any configuration that is designated as a secret will have its corresponding value obfuscated. A placeholder text `********` will be displayed instead of the actual value to enhance security and prevent inadvertent exposure.
     </Warning>

## Restart services

Configuration records are read by Domino services at process startup time. So, for configuration record changes to take affect, you must restart the Domino services. One way to do this is by clicking the **restart services** link in the Configuration records page.

You can also use a CLI tool like `kubectl` instead of the Domino UI to restart services. When doing so, ensure that you restart:

1. Every `nucleus-*` deployment.

2. Each `data-plane-agent` in the local and (if applicable) remote data planes.

## Apps

### Multiple apps per Project

The following configuration options allow administrators to set limits on creating and running multiple apps per Project.

<table>
  <thead>
    <tr>
      <th>Key</th>
      <th>Default</th>
      <th>Description</th>
    </tr>
  </thead>

  <tbody>
    <tr>
      <td colSpan="3"><p>`com.cerebro.domino.apps.maxAppsPerProject`</p></td>
    </tr>

    <tr>
      <td />

      <td><p>`10`</p></td>
      <td><p>The maximum number of apps that can be created in a Project. Users cannot create a new app in the Project once this limit is reached.</p></td>
    </tr>

    <tr>
      <td colSpan="3"><p>`com.cerebro.domino.apps.maxActiveAppRunsPerProject`</p></td>
    </tr>

    <tr>
      <td />

      <td><p>`4`</p></td>
      <td><p>The maximum number of active app runs allowed in a Project. Users cannot start an app in the Project once this limit is reached.</p></td>
    </tr>
  </tbody>
</table>

### App Autoscaling

The following configuration options control aspects of how Apps with the autoscaling feature enabled are managed and deployed.

<table>
  <thead>
    <tr>
      <th>Key</th>
      <th>Default</th>
      <th>Description</th>
    </tr>
  </thead>

  <tbody>
    <tr>
      <td colSpan="3"><p>`com.cerebro.domino.apps.autoscaledExecutionPvcName`</p></td>
    </tr>

    <tr>
      <td />

      <td><p>The value of `com.cerebro.domino.filecache.pvc.name`, which itself defaults to `shared-$stage-compute`, where `$stage` is the value of `com.cerebro.domino.stage`</p></td>
      <td><p>The name of the PVC used for temporary storage and project code and files for an autoscaled App running in the local data plane.</p></td>
    </tr>

    <tr>
      <td colSpan="3"><p>`com.cerebro.domino.apps.autoscaledExecutionPvcNamesForRemoteDataPlanes`</p></td>
    </tr>

    <tr>
      <td />

      <td><p>`{}`</p></td>
      <td><p>A JSON object map like `{"[dp-host-name]": "[pvc-name]"}`; containing the names of the PVCs used for temporary storage and project code and files in remote data planes. The key/value pair `"dp-host-one": "host-one-pvc"` means that autoscaled Apps in the data plane with host name `dp-host-one` will use the PVC named `host-one-pvc`.</p></td>
    </tr>

    <tr>
      <td colSpan="3"><p>`com.cerebro.domino.computegrid.kubernetes.volume.monitorExecutorStaleFileHandle`</p></td>
    </tr>

    <tr>
      <td />

      <td><p>`true`</p></td>
      <td><p>When `true`, the `executor` container in an autoscaled App monitors its project code mount point for "stale file handle" errors. When such an error is detected, the pod is eventually killed and replaced.</p></td>
    </tr>

    <tr>
      <td colSpan="3"><p>`com.cerebro.domino.computegrid.kubernetes.volume.monitorRunStdErrStaleFileHandle`</p></td>
    </tr>

    <tr>
      <td />

      <td><p>`true`</p></td>
      <td><p>When `true`, the `executor` container in an autoscaled App monitors the `run` container’s (user code’s) standard error file for "stale file handle" errors. When such an error is detected, the pod is eventually killed and replaced.</p></td>
    </tr>

    <tr>
      <td colSpan="3"><p>`com.cerebro.domino.computegrid.kubernetes.volume.monitorRunStaleFileHandle`</p></td>
    </tr>

    <tr>
      <td />

      <td><p>`true`</p></td>
      <td><p>When `true`, the `run` container in an autoscaled App monitors its project code mount point for "stale file handle" errors. When such an error is detected, the pod is eventually killed and replaced.</p></td>
    </tr>
  </tbody>
</table>

<Warning>
  The autoscaling feature for Apps will not work "out of the box" for remote data planes. To enable this feature in a remote data plane, set the `com.cerebro.domino.apps.autoscaledExecutionPvcNamesForRemoteDataPlanes` configuration record with the name of the PVC to use in that remote data plane. The PVC must correspond to an NFS volume. For example, if you are using Domino Datasets in a remote data plane, that same PVC will work with autoscaled Apps. If not, you must first create an NFS PVC/PV that labels and annotations that allow it to be recognized by the Domino system. By default, autoscaled Apps in the local data plane use the same PVC that Domino Datasets use, but that deployment option can be configured via the `com.cerebro.domino.apps.autoscaledExecutionPvcName` configuration record.
</Warning>

## Authentication

### Idle Timeout configuration

These options relate to automatic session management through the Idle Timeout functionality. When users remain inactive across all Domino tabs for a specified period, the system will automatically log them out of their entire session for enhanced security. This intelligent timeout mechanism monitors actual user interaction rather than just session duration, providing better security without disrupting active work.

<table>
  <thead>
    <tr>
      <th>Key</th>
      <th>Default</th>
      <th>Description</th>
    </tr>
  </thead>

  <tbody>
    <tr>
      <td colSpan="3"><p>`com.cerebro.domino.frontend.idleTimeoutValueInMinutes`</p></td>
    </tr>

    <tr>
      <td />

      <td><p>`0`</p></td>
      <td><p>This is the total inactivity time in minutes after which the user will be automatically logged out. The default value of `0` means that this functionality is turned off.</p></td>
    </tr>

    <tr>
      <td colSpan="3"><p>`com.cerebro.domino.frontend.idleTimeoutPromptValueInMinutes`</p></td>
    </tr>

    <tr>
      <td />

      <td><p>`0`</p></td>
      <td><p>This is the amount of time before the idle timeout when a user will receive an inactivity notice. With the default value of `0`, users will be notified 3 minutes before being logged out unless this value is changed. This setting must be less than the value of `com.cerebro.domino.frontend.idleTimeoutValueInMinutes`.</p></td>
    </tr>
  </tbody>
</table>

### Organization membership

This option relates to the [Keycloak authentication service](/6.3/admin/identity-and-access/authentication/keycloak-set-up). They are available in namespace `common` and must be recorded with no `name`.

<table>
  <thead>
    <tr>
      <th>Key</th>
      <th>Default</th>
      <th>Description</th>
    </tr>
  </thead>

  <tbody>
    <tr>
      <td colSpan="3"><p>`authentication.oidc.externalOrgsEnabled`</p></td>
    </tr>

    <tr>
      <td />

      <td><p>`false`</p></td>
      <td><p>Enables Domino organization membership to synchronize with SAML identity provider attributes so that membership can be managed by the identity provider.</p></td>
    </tr>
  </tbody>
</table>

## Authorization

These options relate to authorization and user roles.

<table>
  <thead>
    <tr>
      <th>Key</th>
      <th>Default</th>
      <th>Description</th>
    </tr>
  </thead>

  <tbody>
    <tr>
      <td colSpan="3"><p>`com.cerebro.domino.auth.refreshTokenInRun.proxyPort`</p></td>
    </tr>

    <tr>
      <td />

      <td><p>`8899`</p></td>
      <td><p>The port on which the API proxy operates. Do not change this value.</p><p>WARNING: Contact a Customer Success Manager if you want to change this value.</p></td>
    </tr>

    <tr>
      <td colSpan="3"><p>`com.cerebro.domino.restrictPublishing`</p></td>
    </tr>

    <tr>
      <td />

      <td><p>`false`</p></td>
      <td><p>If `true`, only SupportStaff and SysAdmins can create launchers, schedule runs, or publish apps and Domino endpoints.</p></td>
    </tr>

    <tr>
      <td colSpan="3"><p>`com.cerebro.domino.authorization.restrictManageCollaborators`</p></td>
    </tr>

    <tr>
      <td />

      <td><p>`false`</p></td>
      <td><p>If `true`, Project Owners can manage project collaborators. However, the <strong>Invite</strong> button in the <em>Collaborators and permissions</em> section on the <strong>Access & Sharing</strong> tab in <strong>Project Settings</strong> is not available for other users, even if they are collaborators. See <a href="/6.3/platform-capabilities/core-concepts/projects/collaborate-on-projects/invite-collaborators">Invite collaborators</a>.</p></td>
    </tr>

    <tr>
      <td colSpan="3"><p>`com.cerebro.domino.frontend.restrictCollaboratorsToOrganizations`</p></td>
    </tr>

    <tr>
      <td />

      <td><p>`false`</p></td>
      <td><p>Collaborators on a project are able to invite more collaborators to a project. If this flag is set to `true`, the only eligible additions will be those from the inviting user’s organizations. This only affects invitations to projects, therefore it prevents unauthorized viewing of any data scoped to the project like its datasets, the Domino File System (DFS) storage, and project environment variables. It does not affect any data external to a project like an External Data Volume (EDV), data source, or model endpoint.</p></td>
    </tr>

    <tr>
      <td colSpan="3"><p>`com.cerebro.domino.authorization.limitProjectSharing`</p></td>
    </tr>

    <tr>
      <td />

      <td><p>`false`</p></td>
      <td><p>If `true`, then only users with the Project Manager Domino user role or administrators can manage project permissions. See <a href="/6.3/platform-capabilities/core-concepts/projects/collaborate-on-projects/collaborator-permissions">Settings permissions</a>.</p></td>
    </tr>
  </tbody>
</table>

## Blob storage

Domino can store long-term, unstructured data in blob storage buckets.

<table>
  <thead>
    <tr>
      <th>Key</th>
      <th>Default</th>
      <th>Description</th>
    </tr>
  </thead>

  <tbody>
    <tr>
      <td colSpan="3"><p>`com.cerebro.domino.blobStorageMedium`</p></td>
    </tr>

    <tr>
      <td />

      <td><p>""</p></td>
      <td><p>Determines the DFS storage host for the deployment. For example if set to `S3` or `AzureBlob`, the deployment uses the corresponding object store.</p></td>
    </tr>
  </tbody>
</table>

### S3 storage options

These options relate to Domino File System support for AWS S3 storage. This is available for [AWS deployments](/6.3/admin/installation/manage-deployments/aws) only.

<table>
  <thead>
    <tr>
      <th>Key</th>
      <th>Default</th>
      <th>Description</th>
    </tr>
  </thead>

  <tbody>
    <tr>
      <td colSpan="3"><p>`com.cerebro.domino.blobs.s3.connectionManagerTimeoutDuration`</p></td>
    </tr>

    <tr>
      <td />

      <td><p>`60s`</p></td>
      <td><p>The timeout duration for a connection from the connection manager.</p></td>
    </tr>

    <tr>
      <td colSpan="3"><p>`com.cerebro.domino.blobs.s3.connectionTimeoutDuration`</p></td>
    </tr>

    <tr>
      <td />

      <td><p>`60s`</p></td>
      <td><p>The timeout duration for the connection to S3 storage.</p></td>
    </tr>

    <tr>
      <td colSpan="3"><p>`com.cerebro.domino.blobs.s3.bucketInPath`</p></td>
    </tr>

    <tr>
      <td />

      <td><p>`false`</p></td>
      <td><p>Configures the S3 client to use path-style access for all requests.</p></td>
    </tr>

    <tr>
      <td colSpan="3"><p>`com.cerebro.domino.blobs.s3.bucket`</p></td>
    </tr>

    <tr>
      <td />

      <td><p>""</p></td>
      <td><p>Required: Name of the S3 bucket in which you want to store blobs.</p></td>
    </tr>

    <tr>
      <td colSpan="3"><p>`com.cerebro.domino.blobs.s3.defaultS3BucketPrefix`</p></td>
    </tr>

    <tr>
      <td />

      <td><p>""</p></td>
      <td><p>Prefix that is added to the container name. The user can set this, but this prefix must also be on the container in S3.</p></td>
    </tr>

    <tr>
      <td colSpan="3"><p>`com.cerebro.domino.blobs.s3.defaultS3BucketSuffix`</p></td>
    </tr>

    <tr>
      <td />

      <td><p>""</p></td>
      <td><p>Suffix that is added to the container name. The user can set this, but this suffix must also be on the container in S3.</p></td>
    </tr>

    <tr>
      <td colSpan="3"><p>`com.cerebro.domino.blobs.s3.endpointUrl`</p></td>
    </tr>

    <tr>
      <td />

      <td><p>""</p></td>
      <td><p>Overrides the S3 client endpoint.</p></td>
    </tr>

    <tr>
      <td colSpan="3"><p>`com.cerebro.domino.blobs.s3.maxConnections`</p></td>
    </tr>

    <tr>
      <td />

      <td><p>`100`</p></td>
      <td><p>Determines the pool size of max blobs to transfer concurrently.</p></td>
    </tr>

    <tr>
      <td colSpan="3"><p>`com.cerebro.domino.blobs.s3.path`</p></td>
    </tr>

    <tr>
      <td />

      <td><p>""</p></td>
      <td><p>Carried over from the S3 settings.</p></td>
    </tr>

    <tr>
      <td colSpan="3"><p>`com.cerebro.domino.blobs.s3.region`</p></td>
    </tr>

    <tr>
      <td />

      <td><p>""</p></td>
      <td><p>The region of the S3 account.</p></td>
    </tr>

    <tr>
      <td colSpan="3"><p>`com.cerebro.domino.blobs.s3.signedUrlTimeoutDuration`</p></td>
    </tr>

    <tr>
      <td />

      <td><p>`5 minutes`</p></td>
      <td><p>The timeout duration to access the S3 blob store through a signed URL. This pertains to the CLI only.</p></td>
    </tr>

    <tr>
      <td colSpan="3"><p>`com.cerebro.domino.blobs.s3.socketTimeoutDuration`</p></td>
    </tr>

    <tr>
      <td />

      <td><p>`60s`</p></td>
      <td><p>The timeout duration for packets to reach the server.</p></td>
    </tr>

    <tr>
      <td colSpan="3"><p>`com.cerebro.domino.blobs.s3.sseKmsKeyId`</p></td>
    </tr>

    <tr>
      <td />

      <td><p>""</p></td>
      <td><p>The KMS key ID for use with server-side encryption.</p></td>
    </tr>
  </tbody>
</table>

### Azure blob storage

Domino can store long-term, unstructured data in blob storage buckets.

These options relate Domino File System (DFS) support for Azure blob storage. This is available for new [Azure deployments](/6.3/admin/installation/manage-deployments/azure) only.

<Note>
  If you have DFS project files stored in Azure File Storage, you can contact Domino’s Customer Success team for assistance migrating that data to an Azure Blob Storage deployment.
</Note>

<table>
  <thead>
    <tr>
      <th>Key</th>
      <th>Default</th>
      <th>Description</th>
    </tr>
  </thead>

  <tbody>
    <tr>
      <td colSpan="3"><p>`com.cerebro.domino.azureblob.accountKey`</p></td>
    </tr>

    <tr>
      <td />

      <td><p>""</p></td>
      <td><p>Required: The account key of the Azure blob storage account for the user. Without this, projects won’t load. You can find this information on the Azure Portal Storage Account page under Access Keys.</p></td>
    </tr>

    <tr>
      <td colSpan="3"><p>`com.cerebro.domino.azureblob.accountName`</p></td>
    </tr>

    <tr>
      <td />

      <td><p>""</p></td>
      <td><p>Required: The account name of the Azure blob storage account for the user. Without setting this, files from projects won’t load. You can find this information on the Azure Portal Storage Account page under Access Keys.</p></td>
    </tr>

    <tr>
      <td colSpan="3"><p>`com.cerebro.domino.azureblob.blobStorageMedium`</p></td>
    </tr>

    <tr>
      <td />

      <td><p>""</p></td>
      <td><p>Determines the DFS storage host for the deployment. For example if set to `Azure`, the deployment uses the Azure blob store for DFS.</p></td>
    </tr>

    <tr>
      <td colSpan="3"><p>`com.cerebro.domino.azureblob.connectionManagerTimeoutDuration`</p></td>
    </tr>

    <tr>
      <td />

      <td><p>`60s`</p></td>
      <td><p>The timeout duration for a connection from the connection manager.</p></td>
    </tr>

    <tr>
      <td colSpan="3"><p>`com.cerebro.domino.azureblob.connectionTimeoutDuration`</p></td>
    </tr>

    <tr>
      <td />

      <td><p>`60s`</p></td>
      <td><p>The timeout duration for the connection to Azure blob storage.</p></td>
    </tr>

    <tr>
      <td colSpan="3"><p>`com.cerebro.domino.azureblob.containerName`</p></td>
    </tr>

    <tr>
      <td />

      <td><p>""</p></td>
      <td><p>Required: Container name of the blob container in which you want to store blobs.</p></td>
    </tr>

    <tr>
      <td colSpan="3"><p>`com.cerebro.domino.azureblob.defaultAzureBlobContainerPrefix`</p></td>
    </tr>

    <tr>
      <td />

      <td><p>""</p></td>
      <td><p>Prefix that is added to the container name. The user can set this, but this prefix must also be on the container in Azure.</p></td>
    </tr>

    <tr>
      <td colSpan="3"><p>`com.cerebro.domino.azureblob.defaultAzureBlobContainerSuffix`</p></td>
    </tr>

    <tr>
      <td />

      <td><p>""</p></td>
      <td><p>Suffix that is added to the container name. The user can set this, but this suffix must also be on the container in Azure.</p></td>
    </tr>

    <tr>
      <td colSpan="3"><p>`com.cerebro.domino.azureblob.defaultEndpointsProtocol`</p></td>
    </tr>

    <tr>
      <td />

      <td><p>`https`</p></td>
      <td><p>The protocol to use to hit Azure endpoints. Do not change this value.</p></td>
    </tr>

    <tr>
      <td colSpan="3"><p>`com.cerebro.domino.azureblob.endpointSuffix`</p></td>
    </tr>

    <tr>
      <td />

      <td><p>`core.windows.net`</p></td>
      <td><p>The common endpoint suffix for all Azure endpoints. All Azure endpoints end with `core.windows.net`.</p></td>
    </tr>

    <tr>
      <td colSpan="3"><p>`com.cerebro.domino.azureblob.maxConnections`</p></td>
    </tr>

    <tr>
      <td />

      <td><p>`100`</p></td>
      <td><p>Determines the pool size of max blobs to transfer concurrently. Not required for Azure blob storage.</p></td>
    </tr>

    <tr>
      <td colSpan="3"><p>`com.cerebro.domino.azureblob.socketTimeoutDuration`</p></td>
    </tr>

    <tr>
      <td />

      <td><p>`60s`</p></td>
      <td><p>The timeout duration for packets to reach the server.</p></td>
    </tr>
  </tbody>
</table>

## Caching

<table>
  <thead>
    <tr>
      <th>Key</th>
      <th>Default</th>
      <th>Description</th>
    </tr>
  </thead>

  <tbody>
    <tr>
      <td colSpan="3"><p>`com.cerebro.domino.caching.featureFlagOverridesCacheTimeMs`</p></td>
    </tr>

    <tr>
      <td />

      <td><p>`10000`</p></td>
      <td><p>The length of time from which the feature flag information is requested to the next time they will be retrieved from the server.</p></td>
    </tr>
  </tbody>
</table>

## Compute Cluster auto-scaling

These settings are related to the ability to enable auto-scaling of Spark, Ray, and Dask on-demand clusters. They are available in namespace `common` and must be recorded with no `name`.

<table>
  <thead>
    <tr>
      <th>Key</th>
      <th>Default</th>
      <th>Description</th>
    </tr>
  </thead>

  <tbody>
    <tr>
      <td colSpan="3"><p>`com.cerebro.domino.computegrid.computeCluster.autoscaling.targetCpuUtilizationPercent`</p></td>
    </tr>

    <tr>
      <td />

      <td><p>None</p></td>
      <td><p>Target CPU utilization percentage when scale up of clusters should trigger. If not set, the Kubernetes default of 80% is used.</p></td>
    </tr>

    <tr>
      <td colSpan="3"><p>`com.cerebro.domino.computegrid.computeCluster.autoscaling.targetMemoryUtilizationPercent`</p></td>
    </tr>

    <tr>
      <td />

      <td><p>None</p></td>
      <td><p>Target memory utilization percentage when scale up of clusters should trigger.</p></td>
    </tr>

    <tr>
      <td colSpan="3"><p>`com.cerebro.domino.computegrid.computeCluster.autoscaling.scaleDownStabilizationWindowSeconds`</p></td>
    </tr>

    <tr>
      <td />

      <td><p>None</p></td>
      <td><p>Scale down stabilization window. On lower versions, 300 seconds will apply.</p></td>
    </tr>
  </tbody>
</table>

The following table describes the interaction of the auto-scaling settings.

| targetCpuUtilizationPercent | targetMemoryUtilizationPercent | behavior                                                                           |
| --------------------------- | ------------------------------ | ---------------------------------------------------------------------------------- |
| Not set                     | Not set                        | The default Kubernetes setting of 80% CPU utilization applies.                     |
| `X`                         | Not set                        | `X%` CPU utilization threshold applies. Memory utilization is not considered.      |
| Not set                     | `Y`                            | CPU utilization is not considered. `Y%` Memory utilization threshold applies.      |
| `X`                         | `Y`                            | Scaling will trigger based on reaching either `X%` CPU OR `Y%` memory utilization. |

For more information on compute cluster auto-scaling, you can see the [Kubernetes HPA documentation](https://kubernetes.io/docs/tasks/run-application/horizontal-pod-autoscale/).

## Compute grid

These options relate to the [compute grid](/6.3/admin/infrastructure-and-compute/manage-compute-resources). They are available in namespace `common` and must be recorded with no `name`.

<table>
  <thead>
    <tr>
      <th>Key</th>
      <th>Default</th>
      <th>Description</th>
    </tr>
  </thead>

  <tbody>
    <tr>
      <td colSpan="3"><p>`com.cerebro.domino.computegrid.eventHistory.executions.allowVpn`</p></td>
    </tr>

    <tr>
      <td />

      <td><p>`false`</p></td>
      <td><p>Must be true to support runs using environments configured to use a VPN. Adds the `NET_RAW` capability to the run container when using a VPN, which has security drawbacks.</p></td>
    </tr>

    <tr>
      <td colSpan="3"><p>`com.cerebro.domino.computegrid.eventHistory.garbageCollection.isEnabled`</p></td>
    </tr>

    <tr>
      <td />

      <td><p>`true`</p></td>
      <td><p>If `true`, the garbage collector will run periodically to manage the size of the memory of event history in MongoDB.</p></td>
    </tr>

    <tr>
      <td colSpan="3"><p>`com.cerebro.domino.computegrid.eventHistory.garbageCollection.periodicity`</p></td>
    </tr>

    <tr>
      <td />

      <td><p>`1 hour`</p></td>
      <td><p>How often the garbage collector runs to manage the size of the memory for the event history in MongoDB.</p></td>
    </tr>

    <tr>
      <td colSpan="3"><p>`com.cerebro.domino.computegrid.kubernetes.apps.nginx.clientBodyMaxSizeMiB`</p></td>
    </tr>

    <tr>
      <td />

      <td><p>`25MiB`</p></td>
      <td><p>Sets the <a href="http://nginx.org/en/docs/http/ngx_http_core_module.html#client_max_body_size">client\_body\_max\_size</a> property for the nginx reverse proxy in workspace pods.</p><p>NOTE: If a file upload to a workspace (such as Jupyter or RStudio) fails with a 413 HTTP code, it might be because the file is larger than this limit. If necessary, increase this limit.</p></td>
    </tr>

    <tr>
      <td colSpan="3"><p>`com.cerebro.domino.computegrid.kubernetes.apps.nginx.connectTimeout`</p></td>
    </tr>

    <tr>
      <td />

      <td><p>`300s` if the key is not configured upon deployment.</p></td>
      <td><p>The timeout for waiting to connect to the Nginx proxy server running in the run pod. You must use finite duration syntax to configure the time. For example, 30s for 30 seconds, 5m for 5 minutes, and 1h for 1 hour. See <a href="/6.3/admin/architecture-and-deployment/architecture">the Architecture documentation</a> for application services.</p></td>
    </tr>

    <tr>
      <td colSpan="3"><p>`com.cerebro.domino.computegrid.kubernetes.apps.nginx.readTimeout`</p></td>
    </tr>

    <tr>
      <td />

      <td><p>`300s` if the key is not configured upon deployment.</p></td>
      <td><p>The timeout for waiting to read data from the Nginx proxy server running in the run pod. You must use finite duration syntax to configure the time. For example, 30s for 30 seconds, 5m for 5 minutes, and 1h for 1 hour. See <a href="/6.3/admin/architecture-and-deployment/architecture">the Architecture documentation</a> for application services.</p></td>
    </tr>

    <tr>
      <td colSpan="3"><p>`com.cerebro.domino.computegrid.kubernetes.volume.gcFrequency`</p></td>
    </tr>

    <tr>
      <td />

      <td><p>`10min`</p></td>
      <td><p>Controls how often the <a href="/6.3/admin/infrastructure-and-compute/manage-compute-resources/manage-persistent-volumes/garbage-collection">garbage collector</a> runs to delete old or excess <a href="/6.3/admin/infrastructure-and-compute/manage-compute-resources/manage-persistent-volumes">persistent volumes</a>.</p></td>
    </tr>

    <tr>
      <td colSpan="3"><p>`com.cerebro.domino.computegrid.kubernetes.volume.maxAge`</p></td>
    </tr>

    <tr>
      <td />

      <td><p>`7 days`</p></td>
      <td><p>Setting a value here will cause <a href="/6.3/admin/infrastructure-and-compute/manage-compute-resources/manage-persistent-volumes">persistent volumes</a> older than that to be automatically deleted by the <a href="/6.3/admin/infrastructure-and-compute/manage-compute-resources/manage-persistent-volumes/garbage-collection">garbage collector</a>.</p></td>
    </tr>

    <tr>
      <td colSpan="3"><p>`com.cerebro.domino.computegrid.kubernetes.volume.maxIdle`</p></td>
    </tr>

    <tr>
      <td />

      <td><p>`32`</p></td>
      <td><p>Maximum number of idle <a href="/6.3/admin/infrastructure-and-compute/manage-compute-resources/manage-persistent-volumes">persistent volumes</a> to keep. Idle volumes in excess of this number will be deleted by the <a href="/6.3/admin/infrastructure-and-compute/manage-compute-resources/manage-persistent-volumes/garbage-collection">garbage collector</a>.</p></td>
    </tr>

    <tr>
      <td colSpan="3"><p>`com.cerebro.domino.computegrid.kubernetes.volume.storageClass`</p></td>
    </tr>

    <tr>
      <td />

      <td><p>`dominodisk`</p></td>
      <td><p><a href="https://kubernetes.io/docs/concepts/storage/storage-classes/">Kubernetes storage class</a> that will be used to dynamically provision <a href="/6.3/admin/infrastructure-and-compute/manage-compute-resources/manage-persistent-volumes">persistent volumes</a>. This is set initially to the value of `storage_classes.block.name` in the <a href="/6.3/admin/configuration/installer-configuration#storage-classes">installer storage classes configuration</a>.</p></td>
    </tr>

    <tr>
      <td colSpan="3"><p>`com.cerebro.domino.computegrid.kubernetes.volume.volumesSizeInGB`</p></td>
    </tr>

    <tr>
      <td />

      <td><p>`15`</p></td>
      <td><p>Size in GB of compute grid <a href="/6.3/admin/infrastructure-and-compute/manage-compute-resources/manage-persistent-volumes">persistent volumes</a>. This is the total amount of disk space available to users in runs and workspaces.</p></td>
    </tr>

    <tr>
      <td colSpan="3"><p>`com.cerebro.domino.computegrid.kubernetes.nonRootExecutions.enabled`</p></td>
    </tr>

    <tr>
      <td />

      <td><p>`false`</p></td>
      <td><p>If `true`, user code within executions (the "run" container) never runs as root. If `false`, the user code bootstrap process runs as root, then switches to non-root when the bootstrap process is complete. Note that non-user execution processes (for example, the "executor" container) always run as non-root regardless of whether this setting is `true` or `false`.</p></td>
    </tr>

    <tr>
      <td colSpan="3"><p>`com.cerebro.domino.computegrid.kubernetes.networkPolicy.namespaceLabel`</p></td>
    </tr>

    <tr>
      <td />

      <td><p>`domino-platform`</p></td>
      <td><p>Allows domino to update the namespace in the network policy to a custom value if a custom value is being used.</p></td>
    </tr>

    <tr>
      <td colSpan="3"><p>`com.cerebro.domino.computegrid.timeouts.sagaStateTimeouts.deployingStateTimeoutSeconds`</p></td>
    </tr>

    <tr>
      <td />

      <td><p>`60 * 60` (1 hour)</p></td>
      <td><p>The number of seconds an execution pod in a deploying state will wait before timing out.</p></td>
    </tr>

    <tr>
      <td colSpan="3"><p>`com.cerebro.domino.computegrid.timeouts.sagaStateTimeouts.executionsOverQuotaStateTimeoutSeconds`</p></td>
    </tr>

    <tr>
      <td />

      <td><p>`24 * 60 * 60` (24 hours)</p></td>
      <td><p>The number of seconds an execution pod that cannot be assigned due to execution quota limitations will wait for resources to become available before timing out.</p></td>
    </tr>

    <tr>
      <td colSpan="3"><p>`com.cerebro.domino.computegrid.timeouts.sagaStateTimeouts.preparingStateTimeoutSeconds`</p></td>
    </tr>

    <tr>
      <td />

      <td><p>`60 * 60` (1 hour)</p></td>
      <td><p>The number of seconds an execution pod in a preparing state will wait before timing out.</p></td>
    </tr>

    <tr>
      <td colSpan="3"><p>`com.cerebro.domino.computegrid.userExecutionsQuota.maximumExecutionsPerUser`</p></td>
    </tr>

    <tr>
      <td />

      <td><p>`25`</p></td>
      <td><p>This is the maximum number of executions each user will be allowed to run concurrently. If a user attempts to start additional executions in excess of this those executions will be queued until some of the user’s other executions finish.</p></td>
    </tr>

    <tr>
      <td colSpan="3"><p>`com.cerebro.domino.computegrid.userExecutionsQuota.userExecutionQueueLimit`</p></td>
    </tr>

    <tr>
      <td />

      <td><p>`100`</p></td>
      <td><p>The maximum number of executions that can be queued per user. If a user tries to queue more than this, the excess executions will fail.</p></td>
    </tr>

    <tr>
      <td colSpan="3"><p>`com.cerebro.domino.computegrid.userExecutionsQuota.globalExecutionQueueLimit`</p></td>
    </tr>

    <tr>
      <td />

      <td><p>`1000`</p></td>
      <td><p>The maximum total number of executions that can be queued across all users. If users try to queue more than this, the excess executions will fail.</p></td>
    </tr>
  </tbody>
</table>

## Control Center

The following configuration settings are used for caching.

<table>
  <thead>
    <tr>
      <th>Key</th>
      <th>Default</th>
      <th>Description</th>
    </tr>
  </thead>

  <tbody>
    <tr>
      <td colSpan="3"><p>`com.cerebro.domino.controlCenter.cacheMaxLoadPeriodInMonths`</p></td>
    </tr>

    <tr>
      <td />

      <td><p>`12`</p></td>
      <td><p>Use this key to modify the period (in months) of historical data that the <a href="/6.3/admin/operations/control-center">Control Center</a> uses. You might have to change this value to less than `12` to prevent timeout issues when loading data into the application. Do not set `cacheMaxLoadPeriodInMonths` to greater than `12` months or the chart cannot be used. The report options remain the same: Current Month, Previous Month, Last 3 months, Last 6 months, and Custom. This might improve performance.</p><p>WARNING: Contact a Customer Success Manager if you want to change this value.</p></td>
    </tr>

    <tr>
      <td colSpan="3"><p>`com.cerebro.domino.controlCenter.cacheTimeToLiveInMinutes`</p></td>
    </tr>

    <tr>
      <td />

      <td><p>`30`</p></td>
      <td><p>Specifies how often the cache is refreshed in minutes. This cache is used in the Control Center and improves performance. However, if the cache is refreshed every 30 minutes some recent data will not be included in the reports.</p></td>
    </tr>
  </tbody>
</table>

## Custom HTML banner

Use these options to display a custom banner on every page in the Domino application.

<table>
  <thead>
    <tr>
      <th>Key</th>
      <th>Default</th>
      <th>Description</th>
    </tr>
  </thead>

  <tbody>
    <tr>
      <td colSpan="3"><p>`com.cerebro.domino.frontend.globalBanner.content`</p></td>
    </tr>

    <tr>
      <td />

      <td><p>N/A</p></td>
      <td><p>Required: HTML markup specifying your banner’s content and style. Example: `<div style="background-color: blue; font-size: 50px;">Global Banner</div>`</p></td>
    </tr>

    <tr>
      <td colSpan="3"><p>`com.cerebro.domino.frontend.globalBanner.isClosable`</p></td>
    </tr>

    <tr>
      <td />

      <td><p>`false`</p></td>
      <td><p>If `true`, lets users close the banner.</p></td>
    </tr>

    <tr>
      <td colSpan="3"><p>`com.cerebro.domino.frontend.globalBanner.reappearTimeAfterCloseInSec`</p></td>
    </tr>

    <tr>
      <td />

      <td><p>N/A</p></td>
      <td><p>Optional: Time, in seconds, until the banner reappears after closing the banner. The banner reappears when a page is refreshed or loaded. If not set, the closed banner will stay closed. Clearing hide-global-banner in the local storage will make the banner reappear.</p></td>
    </tr>
  </tbody>
</table>

## Data planes

<table>
  <thead>
    <tr>
      <th>Key</th>
      <th>Default</th>
      <th>Description</th>
    </tr>
  </thead>

  <tbody>
    <tr>
      <td colSpan="3"><p>`com.cerebro.domino.hybrid.internalRegistryExternal.host`</p></td>
    </tr>

    <tr>
      <td />

      <td><p>`123456789012.dkr.ecr.us-west-2.amazonaws.com`</p></td>
      <td><p>Docker registry host name. Auto populated for hybrid-enabled control planes deployed with version 5.4 and later.</p></td>
    </tr>

    <tr>
      <td colSpan="3"><p>`com.cerebro.domino.computegrid.kubernetes.executor.rabbitMqExternal.host`</p></td>
    </tr>

    <tr>
      <td />

      <td><p>`acme-rabbitmq.sandbox.domino.tech`</p></td>
      <td><p>RabbitMQ host name. Used in the data plane install command. Auto populated for hybrid-enabled control planes deployed with version 5.4 and later.</p></td>
    </tr>

    <tr>
      <td colSpan="3"><p>`com.cerebro.domino.computegrid.kubernetes.executor.rabbitMqExternal.port`</p></td>
    </tr>

    <tr>
      <td />

      <td><p>`5672`</p></td>
      <td><p>Optional: RabbitMQ port.</p></td>
    </tr>

    <tr>
      <td colSpan="3"><p>`com.cerebro.domino.hybrid.vaultExternal.host`</p></td>
    </tr>

    <tr>
      <td />

      <td><p>`acme-vault.sandbox.domino.tech`</p></td>
      <td><p>Vault host name. Used in the data plane install command. Auto populated for hybrid-enabled control planes deployed with version 5.4 and later.</p></td>
    </tr>
  </tbody>
</table>

## Data Source authentication

See [Configure Data Source Authentication](/6.3/admin/data-administration/external-data/configure-ds-auth) for details about how to use these options. They are available in namespace `common` and must be recorded with no `name`.

<table>
  <thead>
    <tr>
      <th>Key</th>
      <th>Default</th>
      <th>Description</th>
    </tr>
  </thead>

  <tbody>
    <tr>
      <td colSpan="3"><p>`com.cerebro.domino.datasource.ADLSConfig.enabledAuthTypes`</p></td>
    </tr>

    <tr>
      <td />

      <td><p>`Basic`</p></td>
      <td><p>A comma-separated string specifying the enabled authentication types for <a href="/6.3/platform-capabilities/core-concepts/data/data-source-connectors/connect-to-azure-data-lake-storage">ADLS data sources</a>; only `Basic` is supported.</p></td>
    </tr>

    <tr>
      <td colSpan="3"><p>`com.cerebro.domino.datasource.GCSConfig.enabledAuthTypes`</p></td>
    </tr>

    <tr>
      <td />

      <td><p>`Basic`</p></td>
      <td><p>A comma-separated string specifying the enabled authentication types for <a href="/6.3/platform-capabilities/core-concepts/data/data-source-connectors/connect-to-gcs">GCS data sources</a>; only `Basic` is supported.</p></td>
    </tr>

    <tr>
      <td colSpan="3"><p>`com.cerebro.domino.datasource.GenericS3Config.enabledAuthTypes`</p></td>
    </tr>

    <tr>
      <td />

      <td><p>`Basic`</p></td>
      <td><p>A comma-separated string specifying the enabled authentication types for <em>generic</em> S3 data sources; only `Basic` is supported. For Amazon S3 data source authentication, see `com.cerebro.domino.datasource.S3Config.enabledAuthTypes`.</p></td>
    </tr>

    <tr>
      <td colSpan="3"><p>`com.cerebro.domino.datasource.MySQLConfig.enabledAuthTypes`</p></td>
    </tr>

    <tr>
      <td />

      <td><p>`Basic`</p></td>
      <td><p>A comma-separated string specifying the enabled authentication types for <a href="/6.3/platform-capabilities/core-concepts/data/data-source-connectors/connect-to-mysql">MySQL data sources</a>; `Basic` and `AWSIAMRole` are supported.</p></td>
    </tr>

    <tr>
      <td colSpan="3"><p>`com.cerebro.domino.datasource.OracleConfig.enabledAuthTypes`</p></td>
    </tr>

    <tr>
      <td />

      <td><p>`Basic`</p></td>
      <td><p>A comma-separated string specifying the enabled authentication types for <a href="/6.3/platform-capabilities/core-concepts/data/data-source-connectors/connect-to-oracle">Oracle data sources</a>; only `Basic` and `CertAuth` is supported.</p></td>
    </tr>

    <tr>
      <td colSpan="3"><p>`com.cerebro.domino.datasource.PostgreSQLConfig.enabledAuthTypes`</p></td>
    </tr>

    <tr>
      <td />

      <td><p>`Basic`</p></td>
      <td><p>A comma-separated string specifying the enabled authentication types for <a href="/6.3/platform-capabilities/core-concepts/data/data-source-connectors/connect-to-postgres">PostgreSQL data sources</a>; `Basic`, `AWSIAMRole` and `CertAuth` are supported.</p></td>
    </tr>

    <tr>
      <td colSpan="3"><p>`com.cerebro.domino.datasource.RedshiftConfig.enabledAuthTypes`</p></td>
    </tr>

    <tr>
      <td />

      <td><p>`Basic`</p></td>
      <td><p>A comma-separated string specifying the enabled authentication types for <a href="/6.3/platform-capabilities/core-concepts/data/data-source-connectors/connect-to-redshift">Redshift data sources</a>; `Basic` and `AWSIAMRole` are supported.</p></td>
    </tr>

    <tr>
      <td colSpan="3"><p>`com.cerebro.domino.datasource.S3Config.enabledAuthTypes`</p></td>
    </tr>

    <tr>
      <td />

      <td><p>`Basic`</p></td>
      <td><p>A comma-separated string specifying the enabled authentication types for <a href="/6.3/platform-capabilities/core-concepts/data/data-source-connectors/connect-to-generic-s3">Amazon S3 data sources</a>; `Basic` and `AWSIAMRole` are supported.</p></td>
    </tr>

    <tr>
      <td colSpan="3"><p>`com.cerebro.domino.datasource.SnowflakeConfig.enabledAuthTypes`</p></td>
    </tr>

    <tr>
      <td />

      <td><p>`Basic`</p></td>
      <td><p>A comma-separated string specifying the enabled authentication types for <a href="/6.3/platform-capabilities/core-concepts/data/data-source-connectors/connect-to-snowflake">Snowflake data sources</a>; `Basic` and `OAuth` are supported. See <a href="/6.3/admin/data-administration/external-data/configure-ds-auth/set-up-oauth-for-snowflake">Snowflake OAuth</a> for instructions about setting up Keycloak integration between Domino and Snowflake.</p></td>
    </tr>

    <tr>
      <td colSpan="3"><p>`com.cerebro.domino.datasource.SQLServerConfig.enabledAuthTypes`</p></td>
    </tr>

    <tr>
      <td />

      <td><p>`Basic`</p></td>
      <td><p>A comma-separated string that identifies the enabled authentication types for <a href="/6.3/platform-capabilities/core-concepts/data/data-source-connectors/connect-to-mssql">SQLServer data sources</a>; only `Basic` is supported.</p></td>
    </tr>

    <tr>
      <td colSpan="3"><p>`com.cerebro.domino.datasource.DB2NativeConfig.enabledAuthTypes`</p></td>
    </tr>

    <tr>
      <td />

      <td><p>`Basic`</p></td>
      <td><p>A comma-separated string that identifies the enabled authentication types for <a href="/6.3/platform-capabilities/core-concepts/data/data-source-connectors/connect-to-ibm-db2">DB2 native data sources</a>; only `Basic` is supported.</p></td>
    </tr>
  </tbody>
</table>

## Database

These options customize MongoDB connections.

<table>
  <thead>
    <tr>
      <th>Key</th>
      <th>Default</th>
      <th>Description</th>
    </tr>
  </thead>

  <tbody>
    <tr>
      <td colSpan="3"><p>`com.cerebro.domino.caching.userPersisterCacheTimeMs`</p></td>
    </tr>

    <tr>
      <td />

      <td><p>`10000`</p></td>
      <td><p>Domino recommends consulting your Domino representative before changing this key. Sets the time (in milliseconds) after which the user object is retrieved from the MongoDB rather than from the cache.</p></td>
    </tr>

    <tr>
      <td colSpan="3"><p>`com.cerebro.domino.centralConfig.isEnabled`</p></td>
    </tr>

    <tr>
      <td />

      <td><p>`true`</p></td>
      <td><p>Deprecated. Set to `false` to use an external MongoDB specified by the URI in `centralConfig.mongoURI`.</p></td>
    </tr>

    <tr>
      <td colSpan="3"><p>`com.cerebro.domino.centralConfig.mongoCollection`</p></td>
    </tr>

    <tr>
      <td />

      <td><p>`config`</p></td>
      <td><p><em>Do not change the value of this key</em>. The name of the MongoDB collection that stores configuration record data set at initial deployment.</p></td>
    </tr>

    <tr>
      <td colSpan="3"><p>`com.cerebro.domino.centralConfig.mongoURI`</p></td>
    </tr>

    <tr>
      <td />

      <td><p>Empty</p></td>
      <td><p>Deprecated. The URI for an external MongoDB used to store Domino metadata.</p></td>
    </tr>

    <tr>
      <td colSpan="3"><p>`com.cerebro.domino.database.retry.initialBackoffDuration`</p></td>
    </tr>

    <tr>
      <td />

      <td><p>`1 second`</p></td>
      <td><p>Sets the initial backoff duration for any database operation retries that use an exponential backoff algorithm with the MongoDB.</p></td>
    </tr>

    <tr>
      <td colSpan="3"><p>`com.cerebro.domino.database.retry.maxAttempts`</p></td>
    </tr>

    <tr>
      <td />

      <td><p>`8`</p></td>
      <td><p>Sets the maximum attempts for MongoDB operation retries with exponential backoff.</p></td>
    </tr>

    <tr>
      <td colSpan="3"><p>`com.cerebro.domino.database.retry.policy`</p></td>
    </tr>

    <tr>
      <td />

      <td><p>`Exponential`</p></td>
      <td><p>Indicates whether MongoDB operations will be retried with exponential backoff or not. Values are `Exponential` or `None`.</p></td>
    </tr>

    <tr>
      <td colSpan="3"><p>`com.cerebro.domino.organizations.cache.enable`</p></td>
    </tr>

    <tr>
      <td />

      <td><p>`true`</p></td>
      <td><p>Specifies whether the enter organization’s Mongo collection is cached in memory to improve performance in the Domino application.</p></td>
    </tr>

    <tr>
      <td colSpan="3"><p>`com.cerebro.domino.organizations.cache.ttlMs`</p></td>
    </tr>

    <tr>
      <td />

      <td><p>`500`</p></td>
      <td><p>Specifies the cache lifetime (in milliseconds) for `organizations.cache.enable`.</p></td>
    </tr>
  </tbody>
</table>

## Domino API options

These options relate to [Domino API](/6.3/reference/api).

<table>
  <thead>
    <tr>
      <th>Key</th>
      <th>Default</th>
      <th>Description</th>
    </tr>
  </thead>

  <tbody>
    <tr>
      <td colSpan="3"><p>`com.cerebro.domino.api.isEnabled`</p></td>
    </tr>

    <tr>
      <td />

      <td><p>`true`</p></td>
      <td><p>When `false`, users cannot generate API keys and existing API keys cannot be used as an authentication method for the Domino API.</p></td>
    </tr>

    <tr>
      <td colSpan="3"><p>`com.cerebro.domino.superuser.apiKey`</p></td>
    </tr>

    <tr>
      <td />

      <td><p>N/A</p></td>
      <td><p>Typically set at deployment, the Superuser’s API key is used for interactions between Domino components. Contact your Domino representative if you need assistance.</p></td>
    </tr>

    <tr>
      <td colSpan="3"><p>`com.cerebro.domino.superuser.username`</p></td>
    </tr>

    <tr>
      <td />

      <td><p>N/A</p></td>
      <td><p>Typically set at deployment, the Superuser’s username is used for interactions between Domino components. Contact your Domino representative if you need assistance.</p></td>
    </tr>

    <tr>
      <td colSpan="3"><p>`com.cerebro.domino.public.api.enabled`</p></td>
    </tr>

    <tr>
      <td />

      <td><p>`true`</p></td>
      <td><p>When `false`, the Domino Public API is disabled.</p></td>
    </tr>

    <tr>
      <td colSpan="3"><p>`com.cerebro.domino.publicAPI.maxFetchLimit`</p></td>
    </tr>

    <tr>
      <td />

      <td><p>`1000`</p></td>
      <td><p>Sets the upper bound for number of objects accessible at once.</p></td>
    </tr>
  </tbody>
</table>

## Domino Command-Line Interface (CLI)

These options relate to [Domino CLI](/6.3/reference/cli).

<table>
  <thead>
    <tr>
      <th>Key</th>
      <th>Default</th>
      <th>Description</th>
    </tr>
  </thead>

  <tbody>
    <tr>
      <td colSpan="3"><p>`com.cerebro.domino.frontend.clientBlobModeOverride`</p></td>
    </tr>

    <tr>
      <td />

      <td><p>N/A</p></td>
      <td><p>Identifies what will handle requests to S3. If set to S3, then the Domino CLI will interact directly with S3. If set to API, then the CLI will interact with the Domino instance, and Domino will then interact with S3.</p></td>
    </tr>

    <tr>
      <td colSpan="3"><p>`com.cerebro.domino.frontend.cliInstallerLocation`</p></td>
    </tr>

    <tr>
      <td />

      <td><p>`$UserHost/assets/cli/default`</p></td>
      <td><p>Used to separately host the Domino Command Line Interface (CLI). An example of when this might be used is when a critical fix is needed before the next Domino upgrade.</p></td>
    </tr>
  </tbody>
</table>

## Domino endpoints

These options relate to [Domino endpoints](/6.3/platform-capabilities/features/model-deployment). They are available in namespace `common` and must be recorded with no `name`.

<table>
  <thead>
    <tr>
      <th>Key</th>
      <th>Default</th>
      <th>Description</th>
    </tr>
  </thead>

  <tbody>
    <tr>
      <td colSpan="3"><p>`com.cerebro.domino.modelmanager.instances.defaultNumber`</p></td>
    </tr>

    <tr>
      <td />

      <td><p>`2`</p></td>
      <td><p>Default number of instances per Domino endpoint used for <a href="/6.3/admin/platform-configuration/manage-model-deployments/scale-domino-endpoint">scaling</a>.</p></td>
    </tr>

    <tr>
      <td colSpan="3"><p>`com.cerebro.domino.modelmanager.instances.maximumNumber`</p></td>
    </tr>

    <tr>
      <td />

      <td><p>`32`</p></td>
      <td><p>Maximum number of instances per Domino endpoint used for <a href="/6.3/platform-capabilities/features/model-deployment#Scale-the-deployment">scaling</a>.</p></td>
    </tr>

    <tr>
      <td colSpan="3"><p>`com.cerebro.domino.modelManager.nodeSelectorLabelKey`</p></td>
    </tr>

    <tr>
      <td />

      <td><p>`dominodatalab.com/node-pool`</p></td>
      <td><p>Key used in <a href="https://kubernetes.io/docs/concepts/overview/working-with-objects/labels">Kubernetes label</a> node selector for Domino endpoint pods.</p></td>
    </tr>

    <tr>
      <td colSpan="3"><p>`com.cerebro.domino.modelManager.nodeSelectorLabelValue`</p></td>
    </tr>

    <tr>
      <td />

      <td><p>`default`</p></td>
      <td><p>Value used in <a href="https://kubernetes.io/docs/concepts/overview/working-with-objects/labels">Kubernetes label</a> node selector for Domino endpoint pods.</p></td>
    </tr>

    <tr>
      <td colSpan="3"><p>`com.cerebro.domino.modelmanager.uWsgi.workerCount`</p></td>
    </tr>

    <tr>
      <td />

      <td><p>`1`</p></td>
      <td><p>The uWSGI worker count. This <a href="/6.3/admin/platform-configuration/manage-model-deployments/scale-domino-endpoint">scales all Python Domino endpoints</a> by setting the degree of parallelism.</p></td>
    </tr>

    <tr>
      <td colSpan="3"><p>`com.cerebro.domino.modelmanager.harnessProxy.maxBodyLogLengthInBytes`</p></td>
    </tr>

    <tr>
      <td />

      <td><p>`1024`</p></td>
      <td><p>The maximum size, after truncation, of the JSON representation of Domino endpoint requests and responses that are written to stdout.</p></td>
    </tr>

    <tr>
      <td colSpan="3"><p>`com.cerebro.domino.modelmanager.harnessProxy.clientMaxBodySizeMiB`</p></td>
    </tr>

    <tr>
      <td />

      <td><p>`10`</p></td>
      <td><p>Sets the <a href="http://nginx.org/en/docs/http/ngx_http_core_module.html#client_max_body_size">client\_max\_body\_size</a> property for the Nginx reverse proxy in Domino endpoint pods.</p></td>
    </tr>
  </tbody>
</table>

## Domino Volumes for NetApp ONTAP

These options relate to [NetApp Volumes](/6.3/admin/data-administration/netapp-volumes).

<table>
  <thead>
    <tr>
      <th>Key</th>
      <th>Default</th>
      <th>Description</th>
    </tr>
  </thead>

  <tbody>
    <tr>
      <td colSpan="3"><p>`com.cerebro.domino.netApp.canUserDelete`</p></td>
    </tr>

    <tr>
      <td />

      <td><p>`false`</p></td>
      <td><p>Determines whether non-admin users can fully delete a NetApp Volume or only mark it for deletion.</p></td>
    </tr>

    <tr>
      <td colSpan="3"><p>`com.cerebro.domino.netApp.maxVolumesPerUser`</p></td>
    </tr>

    <tr>
      <td />

      <td><p>`5`</p></td>
      <td><p>The maximum number of NetApp Volumes a user can create.</p></td>
    </tr>
  </tbody>
</table>

## Email notifications

These options relate to [email notifications from Domino](/6.3/platform-capabilities/core-concepts/jobs/customize-job-results). They are available in namespace `common` and must be recorded with no `name`.

<table>
  <thead>
    <tr>
      <th>Key</th>
      <th>Default</th>
      <th>Description</th>
    </tr>
  </thead>

  <tbody>
    <tr>
      <td colSpan="3"><p>`com.cerebro.domino.email.notificationFromAddress`</p></td>
    </tr>

    <tr>
      <td />

      <td><p>N/A</p></td>
      <td><p>Deprecated. Set this value in Domino’s administrator application. To configure the email address from which to get notifications, go to <strong>Admin > Platform settings > Email</strong> and complete the <strong>Notifications FROM Address</strong> field.</p></td>
    </tr>

    <tr>
      <td colSpan="3"><p>`com.cerebro.domino.email.shouldSendWelcomeEmail`</p></td>
    </tr>

    <tr>
      <td />

      <td><p>`true`</p></td>
      <td><p>When `true`, new users receive a welcome email from Domino. Email settings must be configured in <strong>Admin > Platform settings > Email</strong>.</p></td>
    </tr>

    <tr>
      <td colSpan="3"><p>`com.cerebro.domino.email.smtp.emptyPassword`</p></td>
    </tr>

    <tr>
      <td />

      <td><p>`false`</p></td>
      <td><p>Deprecated. If you want to set SMTP to bypass password authentication, go to <strong>Admin > Platform settings > Email</strong> and select <strong>SMTP</strong>. Then, select the <strong>No Password</strong> check box.</p></td>
    </tr>

    <tr>
      <td colSpan="3"><p>`com.cerebro.domino.email.smtp.emptyUser`</p></td>
    </tr>

    <tr>
      <td />

      <td><p>`false`</p></td>
      <td><p>Deprecated. If you want to set SMTP to bypass user authentication, go to <strong>Admin > Platform settings > Email</strong> and select <strong>SMTP</strong>. Then, select the <strong>No Username</strong> check box.</p></td>
    </tr>

    <tr>
      <td colSpan="3"><p>`com.cerebro.domino.email.smtp.transportType`</p></td>
    </tr>

    <tr>
      <td />

      <td><p>N/A</p></td>
      <td><p>Deprecated. Go to <strong>Admin > Platform settings > Email</strong> and select the transport type as <strong>SES</strong>, <strong>SMTP</strong>, or <strong>Logging</strong>.</p></td>
    </tr>

    <tr>
      <td colSpan="3"><p>`com.cerebro.domino.supportAlerter.enableEmailSupportAlert`</p></td>
    </tr>

    <tr>
      <td />

      <td><p>`false`</p></td>
      <td><p>Enable email notifications for the runs which resulted in errors or warnings.</p></td>
    </tr>

    <tr>
      <td colSpan="3"><p>`com.cerebro.domino.email.smtp.host`</p></td>
    </tr>

    <tr>
      <td />

      <td><p>None</p></td>
      <td><p>Hostname of SMTP relay to use for sending emails from Domino.</p></td>
    </tr>

    <tr>
      <td colSpan="3"><p>`com.cerebro.domino.email.smtp.user`</p></td>
    </tr>

    <tr>
      <td />

      <td><p>None</p></td>
      <td><p>Username to use for authenticating to the SMTP host.</p></td>
    </tr>

    <tr>
      <td colSpan="3"><p>`com.cerebro.domino.email.smtp.port`</p></td>
    </tr>

    <tr>
      <td />

      <td><p>`25`</p></td>
      <td><p>Port to use for connecting to SMTP host.</p></td>
    </tr>

    <tr>
      <td colSpan="3"><p>`com.cerebro.domino.email.smtp.ssl`</p></td>
    </tr>

    <tr>
      <td />

      <td><p>`false`</p></td>
      <td><p>Whether the SMTP host uses SSL.</p></td>
    </tr>

    <tr>
      <td colSpan="3"><p>`com.cerebro.domino.supportAlerter.errorRecipients`</p></td>
    </tr>

    <tr>
      <td />

      <td><p>None</p></td>
      <td><p>Comma-separated list of email recipients who should get the error notifications. Needs to be explicitly set if `enableEmailSupportAlert` is set to `true`.</p></td>
    </tr>

    <tr>
      <td colSpan="3"><p>`com.cerebro.domino.supportAlerter.warningRecipients`</p></td>
    </tr>

    <tr>
      <td />

      <td><p>None</p></td>
      <td><p>Comma-separated list of email recipients who should get the warning notifications. Needs to be explicitly set if `enableEmailSupportAlert` is set to `true`.</p></td>
    </tr>
  </tbody>
</table>

## Environments

These options relate to [Domino Environments](/6.3/platform-capabilities/core-concepts/compute-environments/manage-compute-environments). They are available in namespace `common` and must be recorded with no `name`.

<table>
  <thead>
    <tr>
      <th>Key</th>
      <th>Default</th>
      <th>Description</th>
    </tr>
  </thead>

  <tbody>
    <tr>
      <td colSpan="3"><p>`com.cerebro.domino.environments.canNonSysAdminsCreateEnvironments`</p></td>
    </tr>

    <tr>
      <td />

      <td><p>`true`</p></td>
      <td><p>If set to `false` only system administrators can edit environments.</p></td>
    </tr>

    <tr>
      <td colSpan="3"><p>`com.cerebro.domino.executableTarget.enabled`</p></td>
    </tr>

    <tr>
      <td />

      <td><p>`false`</p></td>
      <td><p>If set to `true`, allows users to create custom file handlers. Custom file handlers override built-in file handlers for supported file types.</p></td>
    </tr>

    <tr>
      <td colSpan="3"><p>`com.cerebro.domino.workbench.restrictedAssets.enabled`</p></td>
    </tr>

    <tr>
      <td />

      <td><p>`false`</p></td>
      <td><p>If set to `true`, allows users to create restricted projects and admins to <a href="/6.3/admin/platform-configuration/manage-compute-environments/restricted-environments">classify restricted environments</a>.</p></td>
    </tr>

    <tr>
      <td colSpan="3"><p>`com.cerebro.domino.environments.buildPropagation.enabled`</p></td>
    </tr>

    <tr>
      <td />

      <td><p>`true`</p></td>
      <td><p>If set to `true`, users will have the option to toggle whether environment revisions should be marked as active, and will have the option to automatically rebuild Environments whenever the active revision of a base environment changes.</p></td>
    </tr>
  </tbody>
</table>

## Feature flags

<table>
  <thead>
    <tr>
      <th>Key</th>
      <th>Default</th>
      <th>Description</th>
    </tr>
  </thead>

  <tbody>
    <tr>
      <td colSpan="3"><p>`com.cerebro.domino.caching.featureFlagOverridesCacheTimeMs`</p></td>
    </tr>

    <tr>
      <td />

      <td><p>`10000`</p></td>
      <td><p>Cache duration in milliseconds for feature flag data before re-fetching from server.</p></td>
    </tr>
  </tbody>
</table>

## Feedback

These options relate to the Domino Feedback feature.

<table>
  <thead>
    <tr>
      <th>Key</th>
      <th>Default</th>
      <th>Description</th>
    </tr>
  </thead>

  <tbody>
    <tr>
      <td colSpan="3"><p>`com.cerebro.domino.frontend.enableFeedbackModal`</p></td>
    </tr>

    <tr>
      <td />

      <td><p>`true`</p></td>
      <td><p>If true, and the SMTP server is configured, enables the feedback button in the Domino UI.</p></td>
    </tr>

    <tr>
      <td colSpan="3"><p>`com.cerebro.domino.feedback.settings.sender.name`</p></td>
    </tr>

    <tr>
      <td />

      <td><p>`Domino Feedback`</p></td>
      <td><p>Name of the feedback email sender.</p></td>
    </tr>

    <tr>
      <td colSpan="3"><p>`com.cerebro.domino.feedback.settings.sender.address`</p></td>
    </tr>

    <tr>
      <td />

      <td><p>`feedback@dominodatalab.com`</p></td>
      <td><p>Email address of the feedback email sender.</p></td>
    </tr>

    <tr>
      <td colSpan="3"><p>`com.cerebro.domino.feedback.settings.recipient.address`</p></td>
    </tr>

    <tr>
      <td />

      <td><p>`feedback@dominodatalab.com`</p></td>
      <td><p>Email address of the feedback email recipient.</p></td>
    </tr>
  </tbody>
</table>

## File download API

These options relate to the `file contents download` [API endpoint](/6.3/reference/api/domino-open-api#_getProjectFileContents). They are available in namespace `common` and must be recorded with no `name`.

<table>
  <thead>
    <tr>
      <th>Key</th>
      <th>Default</th>
      <th>Description</th>
    </tr>
  </thead>

  <tbody>
    <tr>
      <td colSpan="3"><p>`com.cerebro.domino.restrictBlobApi`</p></td>
    </tr>

    <tr>
      <td />

      <td><p>`false`</p></td>
      <td><p>Set to `true` to require an admin API key to download files through API. When `false`, any user with the blob ID for a file might download it through API.</p></td>
    </tr>

    <tr>
      <td colSpan="3"><p>`com.cerebro.domino.frontend.clientBlobModeOverride`</p></td>
    </tr>

    <tr>
      <td />

      <td><p>None</p></td>
      <td><p>Set to `API` to download blobs directly in the Domino API. Set to `S3` to download blobs through S3. You cannot set the blob mode override in `site_config.json`.</p></td>
    </tr>
  </tbody>
</table>

## Flows

<Note>
  Domino Flows is only supported in Cloud, AWS, and Azure deployments.
</Note>

<table>
  <thead>
    <tr>
      <th>Key</th>
      <th>Default</th>
      <th>Description</th>
    </tr>
  </thead>

  <tbody>
    <tr>
      <td colSpan="3"><p>`com.cerebro.domino.flows.enabled`</p></td>
    </tr>

    <tr>
      <td />

      <td><p>`true`</p></td>
      <td><p>Enables <a href="/6.3/platform-capabilities/features/flows">Domino Flows</a> capabilities.</p></td>
    </tr>
  </tbody>
</table>

## ImageBuilder

These options relate to the Domino ImageBuilder V3.

Use the ImageBuilder to create new environment revision and Domino endpoint version Docker images. To satisfy requirements around heightened security and support for non-Docker container runtimes (such as cri-o for OpenShift), the ImageBuilder uses an open-source image building engine named [Buildkit](https://github.com/moby/buildkit) and wraps in a suitable fashion for Domino’s use. The ImageBuilder acts as a controller, built around the [Kubernetes operator](https://kubernetes.io/docs/concepts/extend-kubernetes/operator/) pattern in which it acts on custom resources (`ContainerImageBuild`) using standard CRUD actions.

<table>
  <thead>
    <tr>
      <th>Key</th>
      <th>Default</th>
      <th>Description</th>
    </tr>
  </thead>

  <tbody>
    <tr>
      <td colSpan="3"><p>`com.cerebro.domino.builder.remoteRegistryCredentials.server`</p></td>
    </tr>

    <tr>
      <td />

      <td><p>`quay.io`</p></td>
      <td><p>The external Docker registry URI to pull Domino base images from.</p></td>
    </tr>

    <tr>
      <td colSpan="3"><p>`com.cerebro.domino.builder.remoteRegistryCredentials.additionalServers`</p></td>
    </tr>

    <tr>
      <td />

      <td><p>None</p></td>
      <td><p>If you use multiple external registries, a comma-separated list of Docker registry URIs from which to build the Domino base image.</p></td>
    </tr>

    <tr>
      <td colSpan="3"><p>`com.cerebro.domino.builder.remoteRegistryCredentials.secretName`</p></td>
    </tr>

    <tr>
      <td />

      <td><p>`domino-quay-repos`</p></td>
      <td><p>The K8s secret containing credentials for authentication to an external Docker registry.</p></td>
    </tr>

    <tr>
      <td colSpan="3"><p>`com.cerebro.domino.builder.remoteRegistryCredentials.secretNamespace`</p></td>
    </tr>

    <tr>
      <td />

      <td><p>`<Domino Compute Namespace>`</p></td>
      <td><p>The namespace where the external Docker registry secret is located.</p></td>
    </tr>
  </tbody>
</table>

## Long-running Workspaces

These options relate to long-running workspace sessions, but do not apply to long-running Jobs. They are available in namespace `common` and must be recorded with no `name`.

[Configure long-running workspaces](/6.3/platform-capabilities/core-concepts/workspaces/set-up-a-workspace#configure-long-running-workspaces) has more information about the auto shutdown behavior of long-running workspaces.

**Workload notification options:**

<table>
  <thead>
    <tr>
      <th>Key</th>
      <th>Default</th>
      <th>Description</th>
    </tr>
  </thead>

  <tbody>
    <tr>
      <td colSpan="3"><p>`com.cerebro.domino.workloadNotifications.longRunningWorkloadDefinitionInSeconds`</p></td>
    </tr>

    <tr>
      <td />

      <td><p>`86400`</p></td>
      <td><p>Defines how long a workspace must run in seconds before the workspace is classified as 'long-running' and begins to generate notifications or becomes subject to automatic shutdown.</p></td>
    </tr>

    <tr>
      <td colSpan="3"><p>`com.cerebro.domino.workloadNotifications.isEnabled`</p></td>
    </tr>

    <tr>
      <td />

      <td><p>`false`</p></td>
      <td><p>Set to `true` to enable the option for email notifications to users when their workspaces become long-running. If `com.cerebro.domino.workloadNotifications.isEnabled` is `true` and `com.cerebro.domino.workloadNotifications.isRequired` is `false`, users can turn these notifications on or off in their account settings.</p></td>
    </tr>

    <tr>
      <td colSpan="3"><p>`com.cerebro.domino.workloadNotifications.isRequired`</p></td>
    </tr>

    <tr>
      <td />

      <td><p>`false`</p></td>
      <td><p>Set to `true` to turn on long-running workspace notifications for all users. While this is `true` users cannot turn off long-running workspace notifications.</p></td>
    </tr>

    <tr>
      <td colSpan="3"><p>`com.cerebro.domino.workloadNotifications.maximumPeriodInSeconds`</p></td>
    </tr>

    <tr>
      <td />

      <td><p>`7200`</p></td>
      <td><p>Maximum time (in seconds) that a user can set as the period between receiving long-running notification emails.</p><p>NOTE: This does not change how often users will receive notifications. They receive repeated notifications about long-running workspaces based on the frequency that they set in the application. If your users want to change the frequency of their notifications, provide them the following information: <a href="https://tickets.dominodatalab.com/hc/en-us/articles/4413702251284-Auto-Shut-Down-Long-Running-Workspace">Auto Shut Down: Long Running Workspace</a>.</p></td>
    </tr>
  </tbody>
</table>

**Workspace auto shutdown options:**

<table>
  <thead>
    <tr>
      <th>Key</th>
      <th>Default</th>
      <th>Description</th>
    </tr>
  </thead>

  <tbody>
    <tr>
      <td colSpan="3"><p>`com.cerebro.domino.workspaceAutoShutdown.isEnabled`</p></td>
    </tr>

    <tr>
      <td />

      <td><p>`false`</p></td>
      <td><p>Set to `true` to enable automatic shutdown of long-running workspaces. Users can turn automatic shutdown for their workspaces on or off from their account settings.</p></td>
    </tr>

    <tr>
      <td colSpan="3"><p>`com.cerebro.domino.workspaceAutoShutdown.isRequired`</p></td>
    </tr>

    <tr>
      <td />

      <td><p>`false`</p></td>
      <td><p>Set to `true` to turn on automatic shutdown of long-running workspaces for all users. While this is `true` users cannot turn off automatic shutdown of their long-running workspaces.</p></td>
    </tr>

    <tr>
      <td colSpan="3"><p>`com.cerebro.domino.workspaceAutoShutdown.globalMaximumLifetimeInSeconds`</p></td>
    </tr>

    <tr>
      <td />

      <td><p>`259200`</p></td>
      <td><p>Longest time in seconds a long-running workspace will be allowed to continue before automatic shutdown. Users cannot set their automatic shutdown timer to be longer than this.</p></td>
    </tr>
  </tbody>
</table>

## Model Monitoring

These options customize how prediction data is captured for [monitoring](/6.3/platform-capabilities/features/monitoring):

### Data retention and deletion options

<table>
  <thead>
    <tr>
      <th>Key</th>
      <th>Default</th>
      <th>Description</th>
    </tr>
  </thead>

  <tbody>
    <tr>
      <td colSpan="3"><p>`com.cerebro.domino.modelManager.enableDominoModelMonitoringForModelAPIs`</p></td>
    </tr>

    <tr>
      <td />

      <td><p>`true`</p></td>
      <td><p>When `false`, this disables Model Monitoring features in Domino and overrides the feature flag `enableModelMonitoringForModelAPIs`.</p></td>
    </tr>

    <tr>
      <td colSpan="3"><p>`domino.parquet.cleanup_job.retention_days`</p></td>
    </tr>

    <tr>
      <td />

      <td><p>`30`</p></td>
      <td><p>Retention of the parquet files (in number of days) before they get deleted to free up space.</p></td>
    </tr>

    <tr>
      <td colSpan="3"><p>`domino.parquet.conversion_job.autodelete_key`</p></td>
    </tr>

    <tr>
      <td />

      <td><p>autodelete</p></td>
      <td><p>Key of the \{key: value} pair used to select a file for auto-deletion</p></td>
    </tr>

    <tr>
      <td colSpan="3"><p>`domino.parquet.conversion_job.autodelete_value`</p></td>
    </tr>

    <tr>
      <td />

      <td><p>`true`</p></td>
      <td><p>Value of the \{key: value} pair used to select a file for auto-deletion</p></td>
    </tr>

    <tr>
      <td colSpan="3"><p>`domino.parquet.conversion_job.raw_data_debug_grace_days`</p></td>
    </tr>

    <tr>
      <td />

      <td><p>`1`</p></td>
      <td><p>Grace period to keep the source raw log files post processing</p></td>
    </tr>
  </tbody>
</table>

### Domino endpoint-specific options

<table>
  <thead>
    <tr>
      <th>Key</th>
      <th>Default</th>
      <th>Description</th>
    </tr>
  </thead>

  <tbody>
    <tr>
      <td colSpan="3"><p>`com.cerebro.domino.modelmanager.pvc.name`</p></td>
    </tr>

    <tr>
      <td />

      <td><p>`shared-$stage-compute` (Same as domino `filecache`)</p></td>
      <td><p>PVC name for storing prediction data.</p></td>
    </tr>

    <tr>
      <td colSpan="3"><p>`com.cerebro.domino.modelmanager.pvc.mountPoint`</p></td>
    </tr>

    <tr>
      <td />

      <td><p>`/domino/shared`</p></td>
      <td><p>PVC mount point for storing prediction data.</p></td>
    </tr>

    <tr>
      <td colSpan="3"><p>`com.cerebro.domino.modelmanager.pvc.subdir`</p></td>
    </tr>

    <tr>
      <td />

      <td><p>`scratch`</p></td>
      <td><p>PVC sub mount point.</p></td>
    </tr>

    <tr>
      <td colSpan="3"><p>`com.cerebro.domino.modelmanager.fluentBit.image`</p></td>
    </tr>

    <tr>
      <td />

      <td><p>Supplied from Domino Charts</p></td>
      <td><p>Fluent-bit image.</p></td>
    </tr>

    <tr>
      <td colSpan="3"><p>`com.cerebro.domino.modelmanager.logrotate.image`</p></td>
    </tr>

    <tr>
      <td />

      <td><p>Supplied from Domino Charts</p></td>
      <td><p>Logrotate image.</p></td>
    </tr>

    <tr>
      <td colSpan="3"><p>`com.cerebro.domino.modelmanager.ingress.tls.secret`</p></td>
    </tr>

    <tr>
      <td />

      <td><p>Supplied from Domino Charts</p></td>
      <td><p>The secret for the ingress route for Domino endpoint publishing.</p><p>TIP: The value is `<secretname>` and not `<namespace>/<secretname>`.</p></td>
    </tr>

    <tr>
      <td colSpan="3"><p>`com.cerebro.domino.modelApis.async.maxMsgSizeInBytes`</p></td>
    </tr>

    <tr>
      <td />

      <td><p>`10Kb`</p></td>
      <td><p>This property determines the maximum size of message in input and output queues. Therefore this property restricts the size of prediction input payload as well as inference output from model.</p></td>
    </tr>

    <tr>
      <td colSpan="3"><p>`com.cerebro.domino.modelApis.async.mongoDb.minimumAvailableBytes`</p></td>
    </tr>

    <tr>
      <td />

      <td><p>`500000000`</p></td>
      <td><p>Minimum available MongoDB disk storage for asynchronous Domino endpoints. See <a href="/6.3/admin/infrastructure-and-compute/sizing-the-infrastructure/size-async-domino-endpoint">Asynchronous Domino Endpoints Capacity Planning</a> for more information.</p></td>
    </tr>

    <tr>
      <td colSpan="3"><p>`com.cerebro.domino.modelApis.async.rabbitmq.availableAsyncLimitBytes`</p></td>
    </tr>

    <tr>
      <td />

      <td><p>`1000000000`</p></td>
      <td><p>Minimum available RabbitMQ disk storage for asynchronous Domino endpoints. See <a href="/6.3/admin/infrastructure-and-compute/sizing-the-infrastructure/size-async-domino-endpoint">Asynchronous Domino Endpoints Capacity Planning</a> for more information.</p></td>
    </tr>
  </tbody>
</table>

### Cohort Analysis options

<table>
  <thead>
    <tr>
      <th>Key</th>
      <th>Default</th>
      <th>Description</th>
    </tr>
  </thead>

  <tbody>
    <tr>
      <td colSpan="3"><p>`com.cerebro.domino.actionable.insights.project.name`</p></td>
    </tr>

    <tr>
      <td />

      <td><p>`DominoActionableInsights`</p></td>
      <td><p>The name of the project for Actionable Insights.</p></td>
    </tr>

    <tr>
      <td colSpan="3"><p>`com.cerebro.domino.actionable.insights.dataset.name`</p></td>
    </tr>

    <tr>
      <td />

      <td><p>`DominoActionableInsightsDataset`</p></td>
      <td><p>The name of the dataset for Actionable Insights.</p></td>
    </tr>

    <tr>
      <td colSpan="3"><p>`com.cerebro.domino.actionable.insights.environment.id`</p></td>
    </tr>

    <tr>
      <td />

      <td />

      <td><p>Environment ID for the Actionable Insights Job. If not defined</p></td>
    </tr>

    <tr>
      <td colSpan="3"><p>`com.cerebro.domino.actionable.insights.compute.environment.id`</p></td>
    </tr>

    <tr>
      <td />

      <td />

      <td><p>Environment ID for the Actionable Insights Spark Cluster. If not defined</p></td>
    </tr>

    <tr>
      <td colSpan="3"><p>`com.cerebro.domino.actionable.insights.hardware.tier.id`</p></td>
    </tr>

    <tr>
      <td />

      <td><p>`small-k8s`</p></td>
      <td><p>Hardware Tier ID for the Actionable Insights Job.</p></td>
    </tr>

    <tr>
      <td colSpan="3"><p>`com.cerebro.domino.actionable.insights.master.hardware.tier.id`</p></td>
    </tr>

    <tr>
      <td />

      <td><p>`medium-k8s`</p></td>
      <td><p>Hardware Tier ID for the Actionable Insights Spark Master.</p></td>
    </tr>

    <tr>
      <td colSpan="3"><p>`com.cerebro.domino.actionable.insights.worker.hardware.tier.id`</p></td>
    </tr>

    <tr>
      <td />

      <td><p>`medium-k8s`</p></td>
      <td><p>Hardware Tier ID for the Actionable Insights Spark Workers.</p></td>
    </tr>

    <tr>
      <td colSpan="3"><p>`com.cerebro.domino.actionable.insights.worker.count`</p></td>
    </tr>

    <tr>
      <td />

      <td><p>`2`</p></td>
      <td><p>Number of workers for the Spark cluster.</p></td>
    </tr>
  </tbody>
</table>

## Multi-storage support for Datasets

These options relate to [Multi-Storage Support for Datasets](/6.3/admin/data-administration/datasets#set-up-multiple-storage-accounts). They are available in namespace `common` and must be recorded with no `name`. *Do not change these configurations unless you have reached out to your field team and have been instructed to do so.*

<table>
  <thead>
    <tr>
      <th>Key</th>
      <th>Default</th>
      <th>Description</th>
    </tr>
  </thead>

  <tbody>
    <tr>
      <td colSpan="3"><p>`com.cerebro.domino.datacache.pvc.names`</p></td>
    </tr>

    <tr>
      <td />

      <td><p>`domino-shared-store-domino-compute`</p></td>
      <td><p>This is a comma-separated list of all compute-PVC names used for dataset/snapshot storage at Domino. Note that if this is set, it is crucial that the original PVC name is also included in the list.</p></td>
    </tr>

    <tr>
      <td colSpan="3"><p>`com.cerebro.domino.datacache.pvc.primaryName`</p></td>
    </tr>

    <tr>
      <td />

      <td><p>The first value in the array above</p></td>
      <td><p>The compute-PVC name of the volume in which to store every next dataset and snapshot.</p></td>
    </tr>

    <tr>
      <td colSpan="3"><p>`com.cerebro.domino.datacache.pvc.originalName`</p></td>
    </tr>

    <tr>
      <td />

      <td><p>`shared-$stage-compute` (same as domino `filecache`)</p></td>
      <td><p>The compute-PVC name corresponding to the original Domino storage.</p></td>
    </tr>

    <tr>
      <td colSpan="3"><p>`com.cerebro.domino.datacache.pvc.<COMPUTE-PVC-NAME>.mountPoint`</p></td>
    </tr>

    <tr>
      <td />

      <td><p>`/domino/shared`</p></td>
      <td><p>For each PVC name specified in the values of `com.cerebro.domino.datacache.pvc.names`, specify the compute-PVC name in the key, and mount point at which the PVC is mounted in the `nucleus-*` deployments in the value.</p></td>
    </tr>
  </tbody>
</table>

<Warning>
  All the PVC names specified in the settings above must correspond to the PVC in the compute namespace.
</Warning>

## Notifications

The `ShortLived.EnableUserNotifications` feature flag enables the Notifications feature. This means that it shows the following:

* Notifications page for Administrators where they can create and manage notifications.

* Notifications icon and indicator to identify the criticality of the notifications in the navigation pane.

* Notifications page where users can view their notifications.

If this flag is turned off, all these items are hidden.

See [Event Notifications](/6.3/platform-capabilities/core-concepts/projects/collaborate-on-projects/view-event-notifications) in the *User Guide* and [Notifications](/6.3/admin/platform-configuration/notifications) in this *Admin Guide*.

<table>
  <thead>
    <tr>
      <th>Key</th>
      <th>Default</th>
      <th>Description</th>
    </tr>
  </thead>

  <tbody>
    <tr>
      <td colSpan="3"><p>`com.cerebro.domino.userNotifications.dbCleanup.jobFrequency`</p></td>
    </tr>

    <tr>
      <td />

      <td><p>`10 minutes`</p></td>
      <td><p>Frequency with which notifications will be checked for automatic expiry (`dbCleanup.expirationEnabled`) or deletion (`dbCleanup.deletionEnabled`).</p></td>
    </tr>

    <tr>
      <td colSpan="3"><p>`com.cerebro.domino.userNotifications.dbCleanup.expirationEnabled`</p></td>
    </tr>

    <tr>
      <td />

      <td><p>`true`</p></td>
      <td><p>Enables the job that expires notifications. Notifications without a set end time are expired based on the setting in `com.cerebro.domino.userNotifications.dbCleanup.expirationThreshold`.</p></td>
    </tr>

    <tr>
      <td colSpan="3"><p>`com.cerebro.domino.userNotifications.dbCleanup.expirationThreshold`</p></td>
    </tr>

    <tr>
      <td />

      <td><p>`30 days`</p></td>
      <td><p>Sets an expiration time (in days) for notifications without an end date.</p></td>
    </tr>

    <tr>
      <td colSpan="3"><p>`com.cerebro.domino.userNotifications.dbCleanup.deletionThreshold`</p></td>
    </tr>

    <tr>
      <td />

      <td><p>`30 days`</p></td>
      <td><p>Specifies the time (in days) after which expired notifications will be deleted.</p></td>
    </tr>

    <tr>
      <td colSpan="3"><p>`com.cerebro.domino.userNotifications.limit`</p></td>
    </tr>

    <tr>
      <td />

      <td><p>`5000`</p></td>
      <td><p>Specifies the maximum number of notifications allowed in the system.</p></td>
    </tr>

    <tr>
      <td colSpan="3"><p>`com.cerebro.domino.userNotifications.telemetry.enabled`</p></td>
    </tr>

    <tr>
      <td />

      <td><p>`true`</p></td>
      <td><p>Enables backend telemetry (statistics about the number and type of generated notifications) for notifications.</p></td>
    </tr>

    <tr>
      <td colSpan="3"><p>`com.cerebro.domino.userNotifications.telemetry.initialDelay`</p></td>
    </tr>

    <tr>
      <td />

      <td><p>`2 minutes`</p></td>
      <td><p>The delay before Notifications telemetry is executed the first time. This delays the impact on database processing during initial system startup.</p></td>
    </tr>

    <tr>
      <td colSpan="3"><p>`com.cerebro.domino.userNotifications.telemetry.interval`</p></td>
    </tr>

    <tr>
      <td />

      <td><p>`2 hours`</p></td>
      <td><p>The time between when the notification statistics are updated.</p></td>
    </tr>

    <tr>
      <td colSpan="3"><p>`com.cerebro.domino.userNotifications.telemetry.perUserMetricsEnabled`</p></td>
    </tr>

    <tr>
      <td />

      <td><p>`true`</p></td>
      <td><p>If true, the system shows metrics for each user about the number and types of notifications generated. If false, the system shows metrics about all notifications.</p></td>
    </tr>

    <tr>
      <td colSpan="3"><p>`com.cerebro.domino.notification.maxFilesToAttach`</p></td>
    </tr>

    <tr>
      <td />

      <td><p>`10`</p></td>
      <td><p>The maximum number of files that can be attached to a single notification.</p></td>
    </tr>

    <tr>
      <td colSpan="3"><p>`com.cerebro.domino.notification.maxFileSizeToAttachInMB`</p></td>
    </tr>

    <tr>
      <td />

      <td><p>`2`</p></td>
      <td><p>The maximum size, in megabytes, of any single file attached to a notification.</p></td>
    </tr>
  </tbody>
</table>

## Notifications for monitoring

The options relate to [Notification channels](/6.3/platform-capabilities/features/monitoring/7-monitor-settings/3-notification).

<table>
  <thead>
    <tr>
      <th>Key</th>
      <th>Default</th>
      <th>Description</th>
    </tr>
  </thead>

  <tbody>
    <tr>
      <td colSpan="3"><p>`com.cerebro.domino.email.smtp.from`</p></td>
    </tr>

    <tr>
      <td />

      <td><p>N/A</p></td>
      <td><p>The email address from which Domino sends email notifications.</p></td>
    </tr>

    <tr>
      <td colSpan="3"><p>`com.cerebro.domino.email.smtp.host`</p></td>
    </tr>

    <tr>
      <td />

      <td><p>N/A</p></td>
      <td><p>The host address of the SMTP server from which Domino sends emails.</p></td>
    </tr>

    <tr>
      <td colSpan="3"><p>`com.cerebro.domino.email.smtp.password`</p></td>
    </tr>

    <tr>
      <td />

      <td><p>N/A</p></td>
      <td><p>The password for the SMTP server, which is typically the same password for your web server, from which Domino sends emails.</p></td>
    </tr>

    <tr>
      <td colSpan="3"><p>`com.cerebro.domino.email.smtp.port`</p></td>
    </tr>

    <tr>
      <td />

      <td><p>`25`</p></td>
      <td><p>The TCP port to use to communicate with your SMTP server.</p></td>
    </tr>

    <tr>
      <td colSpan="3"><p>`com.cerebro.domino.email.smtp.ssl`</p></td>
    </tr>

    <tr>
      <td />

      <td><p>`false`</p></td>
      <td><p>Indicates whether the SMTP server uses Secure Sockets Layer (SSL) for secure communications.</p></td>
    </tr>

    <tr>
      <td colSpan="3"><p>`com.cerebro.domino.email.smtp.user`</p></td>
    </tr>

    <tr>
      <td />

      <td><p>N/A</p></td>
      <td><p>The username used by the client to authenticate to the SMTP server to send email.</p></td>
    </tr>
  </tbody>
</table>

## On-demand MPI

The options relate to the [on-demand MPI clusters](/6.3/platform-capabilities/features/compute-clusters-hpc/mpi). They are available in namespace `common` and must be recorded with no `name`.

<table>
  <thead>
    <tr>
      <th>Key</th>
      <th>Default</th>
      <th>Description</th>
    </tr>
  </thead>

  <tbody>
    <tr>
      <td colSpan="3"><p>`com.cerebro.domino.computegrid.computeCluster.checkClusterStatusIntervalSeconds`</p></td>
    </tr>

    <tr>
      <td />

      <td><p>`1.0`</p></td>
      <td><p>Frequency in seconds to run status checks on on-demand MPI clusters.</p></td>
    </tr>

    <tr>
      <td colSpan="3"><p>`com.cerebro.domino.computegrid.timeouts.executor.responseTimeout`</p></td>
    </tr>

    <tr>
      <td />

      <td><p>`1.0`</p></td>
      <td><p>How long the frontend waits for a response, in seconds, after a file sync request before sending an error.</p></td>
    </tr>

    <tr>
      <td colSpan="3"><p>`com.cerebro.domino.computegrid.timeouts.computeCluster.fileSyncTimeout`</p></td>
    </tr>

    <tr>
      <td />

      <td><p>`1 hour`</p></td>
      <td><p>The maximum duration a sync runs before being considered to have timed out.</p></td>
    </tr>

    <tr>
      <td colSpan="3"><p>`com.cerebro.domino.computegrid.computeCluster.checkFileSyncStatusIntervalSeconds`</p></td>
    </tr>

    <tr>
      <td />

      <td><p>`15`</p></td>
      <td><p>The interval, in seconds, the Job launcher script checks the compute cluster file sync status waiting for ready status.</p></td>
    </tr>

    <tr>
      <td colSpan="3"><p>`com.cerebro.domino.computegrid.computeCluster.secretName`</p></td>
    </tr>

    <tr>
      <td />

      <td><p>`domino-compute-cluster`</p></td>
      <td><p>The name of the secret in the domino-compute namespace containing the SSH key material used when configuring SSH on MPI workers.</p></td>
    </tr>

    <tr>
      <td colSpan="3"><p>`com.cerebro.domino.computegrid.computeCluster.storageMountPath`</p></td>
    </tr>

    <tr>
      <td />

      <td><p>`/tmp`</p></td>
      <td><p>Volume mount path location of additional storage for the compute cluster.</p></td>
    </tr>

    <tr>
      <td colSpan="3"><p>`com.cerebro.domino.computegrid.computeCluster.mpi.disableIstio`</p></td>
    </tr>

    <tr>
      <td />

      <td><p>`false`</p></td>
      <td><p>Whether to inject the Istio Proxy sidecar into worker Pods.</p></td>
    </tr>

    <tr>
      <td colSpan="3"><p>`com.cerebro.domino.computegrid.computeCluster.mpi.istioMutualTLSMode`</p></td>
    </tr>

    <tr>
      <td />

      <td />

      <td><p>Configures the `istioMutualTLSMode` for MPI if Istio is enabled. Valid values are: `STRICT` and `PERMISSIVE`.</p></td>
    </tr>
  </tbody>
</table>

## On-demand Slurm

<table>
  <thead>
    <tr>
      <th>Key</th>
      <th>Default</th>
      <th>Description</th>
    </tr>
  </thead>

  <tbody>
    <tr>
      <td colSpan="3"><p>`com.cerebro.domino.computegrid.computeCluster.slurm.minReplicaCount`</p></td>
    </tr>

    <tr>
      <td />

      <td><p>`0`</p></td>
      <td><p>Minimum number of Slurm workers in the nodeset.</p></td>
    </tr>
  </tbody>
</table>

## On-demand Spark

These options relate to the [on-demand Spark clusters](/6.3/platform-capabilities/features/compute-clusters-hpc/spark/on-demand-spark). They are available in namespace `common` and must be recorded with no `name`.

<table>
  <thead>
    <tr>
      <th>Key</th>
      <th>Default</th>
      <th>Description</th>
    </tr>
  </thead>

  <tbody>
    <tr>
      <td colSpan="3"><p>`com.cerebro.domino.integrations.spark.checkClusterStatusIntervalSeconds`</p></td>
    </tr>

    <tr>
      <td />

      <td><p>`1`</p></td>
      <td><p>Frequency in seconds to run status checks on on-demand Spark clusters.</p></td>
    </tr>

    <tr>
      <td colSpan="3"><p>`com.cerebro.domino.integrations.spark.onDemand.workerStorageMountPath`</p></td>
    </tr>

    <tr>
      <td />

      <td><p>`/tmp`</p></td>
      <td><p>File system path on which Spark worker storage is mounted.</p></td>
    </tr>

    <tr>
      <td colSpan="3"><p>`com.cerebro.domino.integrations.spark.sparkConfDirDefault`</p></td>
    </tr>

    <tr>
      <td />

      <td><p>None</p></td>
      <td><p>Option to supply alternative default configuration directory for on-demand Spark clusters.</p></td>
    </tr>

    <tr>
      <td colSpan="3"><p>`com.cerebro.domino.workbench.onDemandSpark.worker.memoryOverheadMinMiB`</p></td>
    </tr>

    <tr>
      <td />

      <td><p>`384`</p></td>
      <td><p>Minimum amount of memory in MiB to use for Spark worker overhead.</p></td>
    </tr>

    <tr>
      <td colSpan="3"><p>`com.cerebro.domino.workbench.onDemandSpark.worker.memoryOverheadFactor`</p></td>
    </tr>

    <tr>
      <td />

      <td><p>`0.1`</p></td>
      <td><p>Spark worker overhead scaling factor.</p></td>
    </tr>

    <tr>
      <td colSpan="3"><p>`com.cerebro.domino.computegrid.computeCluster.spark.proxyCompatability`</p></td>
    </tr>

    <tr>
      <td />

      <td><p>None</p></td>
      <td><p>Set to `legacy` when the Spark UI for on-demand Spark on Domino needs to be compatible with Spark versions prior to 3.1.1.</p></td>
    </tr>
  </tbody>
</table>

## Performance

The following configuration settings are used for caching.

<table>
  <thead>
    <tr>
      <th>Key</th>
      <th>Default</th>
      <th>Description</th>
    </tr>
  </thead>

  <tbody>
    <tr>
      <td colSpan="3"><p>`com.cerebro.domino.controlCenter.cacheMaxLoadPeriodInMonths`</p></td>
    </tr>

    <tr>
      <td />

      <td><p>`12`</p></td>
      <td><p>Months of historical data loaded in the Control Center (maximum 12). See the <a href="#control-center">Control Center</a> section for more detail.</p></td>
    </tr>

    <tr>
      <td colSpan="3"><p>`com.cerebro.domino.controlCenter.cacheTimeToLiveInMinutes`</p></td>
    </tr>

    <tr>
      <td />

      <td><p>`30`</p></td>
      <td><p>Cache refresh interval in minutes for Control Center data. See the <a href="#control-center">Control Center</a> section for more detail.</p></td>
    </tr>
  </tbody>
</table>

## Projects

This option is available in namespace `common` and must be recorded with no `name`.

<table>
  <thead>
    <tr>
      <th>Key</th>
      <th>Default</th>
      <th>Description</th>
    </tr>
  </thead>

  <tbody>
    <tr>
      <td colSpan="3"><p>`com.cerebro.domino.frontend.overrideDefaultProject`</p></td>
    </tr>

    <tr>
      <td />

      <td />

      <td><p>String of comma-separated project paths. For example, `admin-user/getting-started-project, admin-user/sample-app-project`. See <a href="/6.3/admin/platform-configuration/configure-projects/change-the-default-qs-project">Change The Default Project For New Users</a>.</p></td>
    </tr>

    <tr>
      <td colSpan="3"><p>`com.cerebro.domino.frontend.defaultMaxFileSizeToRenderInBytes`</p></td>
    </tr>

    <tr>
      <td />

      <td />

      <td><p>String, indicating the biggest file that may be rendered in the filebrowser: `5 MB`, `10 kB`, `1 GB`, `7 B`</p></td>
    </tr>

    <tr>
      <td colSpan="3"><p>`com.cerebro.domino.frontend.configuredMaxFileSizes`</p></td>
    </tr>

    <tr>
      <td />

      <td />

      <td><p>Specify the largest file size that can be rendered in the file browser for various file types.</p> <p>`com.cerebro.domino.frontend.configuredMaxFileSizes` overrides the default size limits set by `com.cerebro.domino.frontend.defaultMaxFileSizeToRenderInBytes`.</p> <p>The CC Flag expects a JSON string with the following format: `{"fileType1": fileSizeInBytes, "fileType2": fileSizeInBytes, "fileTypeN": fileSizeInBytes}`</p> <p>For example, to set the max render size for PDFs to 1MB and CSVs to 5MB:</p> <p>`{"pdf": 1048576, "csv": 5242880}`</p> <p>Make sure that your JSON is valid before inserting values.</p></td>
    </tr>
  </tbody>
</table>

### Project templates

These options enable Git-based project copy for the specified git providers.

<table>
  <thead>
    <tr>
      <th>Key</th>
      <th>Default</th>
      <th>Description</th>
    </tr>
  </thead>

  <tbody>
    <tr>
      <td colSpan="3"><p>`com.cerebro.domino.workbench.project.projectCopy.githubCopyEnabled`</p></td>
    </tr>

    <tr>
      <td />

      <td><p>`true`</p></td>
      <td><p>Enable copy project for a Git-based project created from a Github repository.</p></td>
    </tr>

    <tr>
      <td colSpan="3"><p>`com.cerebro.domino.workbench.project.projectCopy.gitlabCopyEnabled`</p></td>
    </tr>

    <tr>
      <td />

      <td><p>`true`</p></td>
      <td><p>Enable copy project for a Git-based project created from a Gitlab repository.</p></td>
    </tr>
  </tbody>
</table>

### File uploads

These options can be used to configure file uploads to the projects.

<table>
  <thead>
    <tr>
      <th>Key</th>
      <th>Default</th>
      <th>Description</th>
    </tr>
  </thead>

  <tbody>
    <tr>
      <td colSpan="3"><p>`com.cerebro.domino.upload.maxUploadFileSizeInMegabytes`</p></td>
    </tr>

    <tr>
      <td />

      <td><p>`550`</p></td>
      <td><p>Maximum size (MB) file that can be uploaded.</p></td>
    </tr>

    <tr>
      <td colSpan="3"><p>`com.cerebro.domino.upload.maxUploadFilesCount`</p></td>
    </tr>

    <tr>
      <td />

      <td><p>`1000`</p></td>
      <td><p>Maximum number of files that can be uploaded.</p></td>
    </tr>

    <tr>
      <td colSpan="3"><p>`com.cerebro.domino.upload.restrictedFileTypes`</p></td>
    </tr>

    <tr>
      <td />

      <td><p>`""` (empty string)</p></td>
      <td><p>String, comma separated list of file extensions that cannot be uploaded, e.g., `php`, `exe`, `asp`.</p></td>
    </tr>
  </tbody>
</table>

### Project visibility options

These options relate to [project visibility settings](/6.3/platform-capabilities/core-concepts/projects/collaborate-on-projects/set-project-visibility). They are available in namespace `common` and must be recorded with no `name`.

<table>
  <thead>
    <tr>
      <th>Key</th>
      <th>Default</th>
      <th>Description</th>
    </tr>
  </thead>

  <tbody>
    <tr>
      <td colSpan="3"><p>`com.cerebro.domino.publicProjects.enabled`</p></td>
    </tr>

    <tr>
      <td />

      <td><p>`true`</p></td>
      <td><p>If set to `false`, Practitioners cannot set projects to <a href="/6.3/platform-capabilities/core-concepts/projects/collaborate-on-projects/set-project-visibility#tr1">public visibility</a>. However, an Admin can still create public projects. A change in this setting does not affect existing projects.</p></td>
    </tr>

    <tr>
      <td colSpan="3"><p>`com.cerebro.domino.defaultProjectVisibility`</p></td>
    </tr>

    <tr>
      <td />

      <td><p>`Public`</p></td>
      <td><p>Controls the default <a href="/6.3/platform-capabilities/core-concepts/projects/collaborate-on-projects/set-project-visibility#tr1">visibility setting</a> for new projects. Options are `Public` or `Private`.</p></td>
    </tr>
  </tbody>
</table>

### Project sizes

The Project size can be used to determine the persistent volume capacity used by Project files, either as an auditing mechanism or to estimate volume sizes for Jobs or Workspaces.

The following options control the background scheduled process that computes Project sizes.

<table>
  <thead>
    <tr>
      <th>Key</th>
      <th>Default</th>
      <th>Description</th>
    </tr>
  </thead>

  <tbody>
    <tr>
      <td colSpan="3"><p>`com.cerebro.domino.projectSizeScheduledService.isEnabled`</p></td>
    </tr>

    <tr>
      <td />

      <td><p>`false`</p></td>
      <td><p>Enable/disable the scheduled service that computes projects sizes.</p></td>
    </tr>

    <tr>
      <td colSpan="3"><p>`com.cerebro.domino.projectSizeScheduledService.runDelayInMinutes`</p></td>
    </tr>

    <tr>
      <td />

      <td><p>`120`</p></td>
      <td><p>Defines a fixed delay (in minutes) between each execution of the service. A longer delay prolongs the time it takes for changes in Project files to impact size estimates, while a shorter delay keeps the estimates more up-to-date but consumes additional resources.</p></td>
    </tr>

    <tr>
      <td colSpan="3"><p>`com.cerebro.domino.projectSizeScheduledService.batchSize`</p></td>
    </tr>

    <tr>
      <td />

      <td><p>`20`</p></td>
      <td><p>Defines the maximum number of Projects the sizing services loads into memory simultaneously. The sizing service only loads Project metadata, not files. Increasing this value will demand more heap memory from the service to handle Project sizing.</p></td>
    </tr>

    <tr>
      <td colSpan="3"><p>`com.cerebro.domino.projectSizeScheduledService.maxBatchesPerRun`</p></td>
    </tr>

    <tr>
      <td />

      <td><p>`Int.MaxValue (2,147,483,647)`</p></td>
      <td><p>Defines the maximum number of Project batches to process in each scheduled execution of the sizing service. This can be used to shorten the execution time of the service, by processing less Projects on each run.</p></td>
    </tr>
  </tbody>
</table>

The following option controls the visibility of the Project size information in the Admin portal.

<table>
  <thead>
    <tr>
      <th>Key</th>
      <th>Default</th>
      <th>Description</th>
    </tr>
  </thead>

  <tbody>
    <tr>
      <td colSpan="3"><p>`com.cerebro.domino.frontend.admin.projects.sizeColumnEnabled`</p></td>
    </tr>

    <tr>
      <td />

      <td><p>`false`</p></td>
      <td><p>Show/hide the Project size column in the <strong>Admin > Projects</strong> report.</p></td>
    </tr>
  </tbody>
</table>

### Git and Jira credentials

These options enable storing Git and Jira credentials in Vault.

<table>
  <thead>
    <tr>
      <th>Key</th>
      <th>Default</th>
      <th>Description</th>
    </tr>
  </thead>

  <tbody>
    <tr>
      <td colSpan="3"><p>`com.cerebro.domino.jira.vault.enabled`</p></td>
    </tr>

    <tr>
      <td />

      <td><p>`true`</p></td>
      <td><p>Consult your Domino representative before changing this key. If set to `true`, Jira credentials are stored in Vault. If `false`, they are stored in Mongo.</p></td>
    </tr>

    <tr>
      <td colSpan="3"><p>`com.cerebro.domino.workbench.project.vaultGitCredentials`</p></td>
    </tr>

    <tr>
      <td />

      <td><p>`true`</p></td>
      <td><p>Consult your Domino representative before changing this key. If set to `true`, user Git credentials are stored in Vault. If `false`, they are stored in S3’s blob store.</p></td>
    </tr>
  </tbody>
</table>

## Public applications

This option is related to [Domino Apps](/6.3/platform-capabilities/core-concepts/products/apps). This is available in namespace `common` and must be recorded with no `name`.

<table>
  <thead>
    <tr>
      <th>Key</th>
      <th>Default</th>
      <th>Description</th>
    </tr>
  </thead>

  <tbody>
    <tr>
      <td colSpan="3"><p>`com.cerebro.domino.launchpad.allowPublicModelProducts`</p></td>
    </tr>

    <tr>
      <td />

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

    <tr>
      <td colSpan="3"><p>`com.cerebro.domino.apps.extendedIdentityPropagationToAppsEnabled`</p></td>
    </tr>

    <tr>
      <td />

      <td><p>`false`</p></td>
      <td><p>Enables the Extended Apps Identity Propagation feature.</p></td>
    </tr>

    <tr>
      <td colSpan="3"><p>`com.cerebro.domino.apps.extendedIdentityPropagationToAppsRememberMeExpirationInSecs`</p></td>
    </tr>

    <tr>
      <td />

      <td><p>`2592000` (i.e. 30 days)</p></td>
      <td><p>Specifies how long (in seconds) the consent granted to an App will be stored if the “Remember me” checkbox <strong>is</strong> selected.</p></td>
    </tr>

    <tr>
      <td colSpan="3"><p>`com.cerebro.domino.apps.extendedIdentityPropagationToAppsDontRememberMeExpirationInSecs`</p></td>
    </tr>

    <tr>
      <td />

      <td><p>`28800` (i.e. 8 hours)</p></td>
      <td><p>Specifies how long (in seconds) the consent granted to an App will be stored if the “Remember me” checkbox <strong>isn’t</strong> selected.</p></td>
    </tr>

    <tr>
      <td colSpan="3"><p>`com.cerebro.domino.apps.extendedIdentityPropagationToAppsMaximumExpirationInSecs`</p></td>
    </tr>

    <tr>
      <td />

      <td><p>`2592000` (i.e. 30 days)</p></td>
      <td><p>Specifies the maximum duration (in seconds) for which consent granted to an App may remain valid.</p></td>
    </tr>
  </tbody>
</table>

## Read-write Datasets

These options relate to [read-write datasets](/6.3/platform-capabilities/core-concepts/data/datasets/create-and-manage-datasets). They are available in namespace `common` and must be recorded with no `name`.

<table>
  <thead>
    <tr>
      <th>Key</th>
      <th>Default</th>
      <th>Description</th>
    </tr>
  </thead>

  <tbody>
    <tr>
      <td colSpan="3"><p>`com.cerebro.domino.dataset.graceTimeForDeletion`</p></td>
    </tr>

    <tr>
      <td />

      <td><p>`15min`</p></td>
      <td><p>The time before the system deletes a dataset that was marked for deletion. If you deleted a dataset, you have this time to retrieve the dataset. After this time expires, the dataset cannot be recovered. See <a href="/6.3/platform-capabilities/core-concepts/data/datasets">Datasets and Snapshots</a>.</p></td>
    </tr>

    <tr>
      <td colSpan="3"><p>`com.cerebro.domino.dataset.maxFileListingLength`</p></td>
    </tr>

    <tr>
      <td />

      <td><p>`1000`</p></td>
      <td><p>The maximum number of files shown in the dataset snapshot file viewer</p></td>
    </tr>

    <tr>
      <td colSpan="3"><p>`com.cerebro.domino.dataset.fileCacheTimeout`</p></td>
    </tr>

    <tr>
      <td />

      <td><p>`2s`</p></td>
      <td><p>The timeout for fetching files in the dataset snapshot file viewer</p></td>
    </tr>

    <tr>
      <td colSpan="3"><p>`com.cerebro.domino.dataset.quota.enabled`</p></td>
    </tr>

    <tr>
      <td />

      <td><p>`true`</p></td>
      <td><p>If `true`, the dataset (`com.cerebro.domino.dataset.quota.maxActiveSnapshotsPerDataset`) and snapshot (`com.cerebro.domino.dataset.quota.maxDatasetsPerProject`) limits will be enforced. If `false`, these settings are ignored and there will not be any enforced quota. If the ignore Dataset limit checkbox in a Project is checked, then Datasets local to that Project will not enforce quotas regardless of this configuration record. The checkbox is an override per Project.</p></td>
    </tr>

    <tr>
      <td colSpan="3"><p>`com.cerebro.domino.dataset.quota.maxActiveSnapshotsPerDataset`</p></td>
    </tr>

    <tr>
      <td />

      <td><p>`20`</p></td>
      <td><p>The maximum number of snapshots a user can create for a dataset. `com.cerebro.domino.dataset.quota.enabled` must be `true` for this to work.</p> <p>If the user reaches the maximum number of snapshots, the next time they create a snapshot, Domino shows a warning that they have reached their snapshot limit and that if they proceed, their oldest snapshot will be marked for deletion.</p> <p>See <a href="/6.3/platform-capabilities/core-concepts/data/datasets/version-data-with-snapshots">Create a Snapshot of a Dataset</a> and <a href="/6.3/platform-capabilities/core-concepts/data/datasets">Datasets and Snapshots</a>.</p></td>
    </tr>

    <tr>
      <td colSpan="3"><p>`com.cerebro.domino.dataset.quota.maxDatasetsPerProject`</p></td>
    </tr>

    <tr>
      <td />

      <td><p>`50`</p></td>
      <td><p>The maximum number of Datasets you can create in a Project. `com.cerebro.domino.dataset.quota.enabled` must be `true` for this to work.</p> <p>If the user reaches the maximum number of datasets, Domino shows a message about the limit.</p></td>
    </tr>

    <tr>
      <td colSpan="3"><p>`com.cerebro.domino.dataset.quota.maxFileSizeForPreview`</p></td>
    </tr>

    <tr>
      <td />

      <td><p>`5000000`</p></td>
      <td><p>The maximum file size (in bytes) that the Data renderer will support to preview files. If a file is larger than this limit, the renderer will default to a message recommending file download.</p> <p>See <a href="/6.3/platform-capabilities/core-concepts/data/datasets">Datasets and Snapshots</a>.</p></td>
    </tr>

    <tr>
      <td colSpan="3"><p>`com.cerebro.domino.dataset.containerHome`</p></td>
    </tr>

    <tr>
      <td />

      <td><p>`/domino/datasets`</p></td>
      <td><p>Set the path to mount datasets in Domino projects. Users see this path in the Path column on the Domino Datasets tab on the Data page.</p><p>NOTE: This is not for git-based projects.</p><p>TIP: Add '/' to the beginning of the path to make it clear that it is an absolute path.</p> <p>See <a href="/6.3/platform-capabilities/core-concepts/data/datasets/create-and-manage-datasets">Domino Datasets</a>.</p></td>
    </tr>

    <tr>
      <td colSpan="3"><p>`com.cerebro.domino.dataset.batchDownloadArchiveFormat`</p></td>
    </tr>

    <tr>
      <td />

      <td><p>`zip`</p></td>
      <td><p>The file format of the created archive file when downloading multiple files and/or folders, including downloading snapshots. `zip` and `tar` are supported formats.</p></td>
    </tr>

    <tr>
      <td colSpan="3"><p>`com.cerebro.domino.dataset.gitBasedContainerHome`</p></td>
    </tr>

    <tr>
      <td />

      <td><p>`/mnt`</p></td>
      <td><p>Path at which datasets reside in git-based projects.</p><p>TIP: Add '/' to the beginning of the path to make it clear that it is an absolute path.</p></td>
    </tr>

    <tr>
      <td colSpan="3"><p>`com.cerebro.domino.dataset.executor.snapshotSizeTimeout`</p></td>
    </tr>

    <tr>
      <td />

      <td><p>1 minute</p></td>
      <td><p>The time allotted to gather all file sizes to calculate the size of the snapshot. If the time expires and the size hasn’t finished calculating, Domino shows the current calculation for the snapshot but doesn’t notify the user that the calculation is incomplete.</p></td>
    </tr>

    <tr>
      <td colSpan="3"><p>`com.cerebro.domino.dataset.storageUsageWarningThreshold`</p></td>
    </tr>

    <tr>
      <td />

      <td><p>`70`</p></td>
      <td><p>The percentage of a user’s dataset storage quota that, when reached, triggers warning notifications.</p></td>
    </tr>

    <tr>
      <td colSpan="3"><p>`com.cerebro.domino.dataset.storageUsageCriticalThreshold`</p></td>
    </tr>

    <tr>
      <td />

      <td><p>`85`</p></td>
      <td><p>The percentage of a user’s dataset storage quota that, when reached, triggers email notifications.</p></td>
    </tr>

    <tr>
      <td colSpan="3"><p>`com.cerebro.domino.dataset.snapshotSizingPeriod`</p></td>
    </tr>

    <tr>
      <td />

      <td><p>`7 days`</p></td>
      <td><p>Interval during which the size of a snapshot are not recalculated.</p></td>
    </tr>

    <tr>
      <td colSpan="3"><p>`com.cerebro.domino.dataset.thresholdActionPeriod`</p></td>
    </tr>

    <tr>
      <td />

      <td><p>`7 days`</p></td>
      <td><p>Interval during which notifications to users about their storage usage are not repeated.</p></td>
    </tr>

    <tr>
      <td colSpan="3"><p>`com.cerebro.domino.dataset.unitCostDollarsPerGbPerMonth`</p></td>
    </tr>

    <tr>
      <td />

      <td><p>`None`</p></td>
      <td><p>Estimate unit cost of a dataset (in dollars/GB/month). This value is multiplied linearly by the size of a dataset to estimate its cost per month.</p></td>
    </tr>
  </tbody>
</table>

## Remote Connection to Workspaces via SSH

These options relate to remote connection to user workspaces via SSH (provided that the feature is enabled in the cluster).

<table>
  <thead>
    <tr>
      <th>Key</th>
      <th>Default</th>
      <th>Description</th>
    </tr>
  </thead>

  <tbody>
    <tr>
      <td colSpan="3"><p>`com.cerebro.domino.workbench.workspace.ssh.enabled`</p></td>
    </tr>

    <tr>
      <td />

      <td><p>`false`</p></td>
      <td><p>Enables the UI that displays the checkbox to enable SSH in a Workspace and to display other SSH-related information to the user in the UI.</p></td>
    </tr>

    <tr>
      <td colSpan="3"><p>`com.cerebro.domino.workbench.workspace.ssh.defaultValueOnFirstLaunch`</p></td>
    </tr>

    <tr>
      <td />

      <td><p>`false`</p></td>
      <td><p>Sets the default value for the checkbox in the Create Workspace modal in the UI.</p></td>
    </tr>
  </tbody>
</table>

## Restricted Environments and Projects

<table>
  <thead>
    <tr>
      <th>Key</th>
      <th>Default</th>
      <th>Description</th>
    </tr>
  </thead>

  <tbody>
    <tr>
      <td colSpan="3"><p>`com.cerebro.domino.workbench.restrictedAssets.enabled`</p></td>
    </tr>

    <tr>
      <td />

      <td><p>`false`</p></td>
      <td><p>Set to `true` to enable marking environments and projects as restricted.</p></td>
    </tr>
  </tbody>
</table>

## Run Results

These options relate to the [Execution Results](/6.3/platform-capabilities/core-concepts/jobs/monitor-jobs). They are used to limit the number of file comparisons and number of differences found.

<Note>
  If too many files are compared, you might have to increase the request timeout. See [Increase Request Timeout to Compare Jobs](https://tickets.dominodatalab.com/hc/en-us/articles/10595248082580).
</Note>

<table>
  <thead>
    <tr>
      <th>Key</th>
      <th>Default</th>
      <th>Description</th>
    </tr>
  </thead>

  <tbody>
    <tr>
      <td colSpan="3"><p>`com.cerebro.domino.runResults.maximumNumberOfInputComparisons`</p></td>
    </tr>

    <tr>
      <td />

      <td><p>`1000`</p></td>
      <td><p>The maximum number of input files to compare.</p></td>
    </tr>

    <tr>
      <td colSpan="3"><p>`com.cerebro.domino.runResults.maximumNumberOfInputDiffs`</p></td>
    </tr>

    <tr>
      <td />

      <td><p>`250`</p></td>
      <td><p>The maximum number of input file comparisons that will be found. If this value is reached, the comparison will stop.</p></td>
    </tr>

    <tr>
      <td colSpan="3"><p>`com.cerebro.domino.runResults.maximumNumberOfResultsComparisons`</p></td>
    </tr>

    <tr>
      <td />

      <td><p>`1000`</p></td>
      <td><p>The maximum number of result files to compare.</p></td>
    </tr>

    <tr>
      <td colSpan="3"><p>`com.cerebro.domino.runResults.maximumNumberOfResultsDiffs`</p></td>
    </tr>

    <tr>
      <td />

      <td><p>`250`</p></td>
      <td><p>The maximum number of result file comparisons that will be found. If this value is reached, the comparison will stop.</p></td>
    </tr>
  </tbody>
</table>

## Starburst

These options relate to using [Starburst-powered](/6.3/admin/data-administration/external-data/create-data-sources#starburst-powered-data-sources) Data Sources.

<table>
  <thead>
    <tr>
      <th>Key</th>
      <th>Default</th>
      <th>Description</th>
    </tr>
  </thead>

  <tbody>
    <tr>
      <td colSpan="3"><p>`com.cerebro.domino.datasource.starburstJdbc.enabledConnectors`</p></td>
    </tr>

    <tr>
      <td />

      <td><p>`db2,netezza,sap_hana`</p></td>
      <td><p>A comma-separated list of <a href="/6.3/admin/data-administration/external-data/config-starburst-data-sources#create-a-starburst-jdbc-powered-data-source">Starburst JDBC</a> data entities available to the user. The full list includes: `clickhouse,druid,db2,synapse,greenplum,ignite,mariadb,singlestore,vertica,generic_jdbc,sap_hana,netezza`.</p></td>
    </tr>
  </tbody>
</table>

## System log

These options relate to the [system log](/6.3/admin/operations/audit-logs/monitor-project-logs). They are available in namespace `common` and must be recorded with no `name`.

<table>
  <thead>
    <tr>
      <th>Key</th>
      <th>Default</th>
      <th>Description</th>
    </tr>
  </thead>

  <tbody>
    <tr>
      <td colSpan="3"><p>`com.cerebro.domino.audit.enabled`</p></td>
    </tr>

    <tr>
      <td />

      <td><p>`true`</p></td>
      <td><p>Enables Domino to store audit events and shows the <strong>Audit Log</strong> button. See <a href="/6.3/admin/operations/audit-logs/monitor-project-logs">Download the audit log</a>. Domino recommends that you do not change this value unless you must disable auditing.</p></td>
    </tr>

    <tr>
      <td colSpan="3"><p>`com.cerebro.domino.audit.pagination.page.size`</p></td>
    </tr>

    <tr>
      <td />

      <td><p>`100`</p></td>
      <td><p>Page size for the number of records fetched from MongoDB.</p></td>
    </tr>

    <tr>
      <td colSpan="3"><p>`com.cerebro.domino.audit.pdf.generation.memory.limit`</p></td>
    </tr>

    <tr>
      <td />

      <td><p>`25`</p></td>
      <td><p>The maximum memory limit used by PDF generation. If the memory usage is greater than 25 MB, temporal files are used.</p></td>
    </tr>

    <tr>
      <td colSpan="3"><p>`com.cerebro.domino.requireESignatureWorkflow`</p></td>
    </tr>

    <tr>
      <td />

      <td><p>`Disabled`</p></td>
      <td><p>There are three valid values for this Configuration: `Global`, `PerProject`, and `Disabled`.</p> <p>`Global` enables the e-signature workflow across the whole deployment. Critical actions, regardless of project or user, will require an e-signature to complete.</p> <p>`PerProject` enables a new project setting called `Require E-Signature Workflow`. When checked, critical actions within the project will require the e-signature workflow.</p> <p>`Disabled` means that no e-signature is required for any Domino actions.</p></td>
    </tr>

    <tr>
      <td colSpan="3"><p>`com.cerebro.domino.eSignatureActionOptions`</p></td>
    </tr>

    <tr>
      <td />

      <td><p>See list in Description</p></td>
      <td><p>Allows the admin to configure the values seen in the <strong>Reason for change</strong> dropdown during the e-signature workflow. By default it is set to `Data obsolescence`, `Compliance`, `Business decision`, `Technical reason`, and `Other`.</p> <p>To enter custom values, use a comma and space to separate entries, such as `Data obsolescence, Compliance, Business decision`. The default values will be overwritten as soon as custom text is entered.</p></td>
    </tr>
  </tbody>
</table>

## Telemetry

These records set `customer_name` and `deployment_name`, the values Domino attaches to product analytics events to identify your organization and this environment. See [Deployment identification](/6.3/admin/configuration/deployment-identification) for the full reference. Changes to these records take effect after you [restart the Domino services](#restart-services), same as any other configuration record.

<table>
  <thead>
    <tr>
      <th>Key</th>
      <th>Default</th>
      <th>Description</th>
    </tr>
  </thead>

  <tbody>
    <tr>
      <td colSpan="3"><p>`com.cerebro.domino.telemetry.customerName`</p></td>
    </tr>

    <tr>
      <td />

      <td><p>(value set at install time)</p></td>
      <td><p>Sets the `customer_name` value on telemetry events, identifying your organization.</p></td>
    </tr>

    <tr>
      <td colSpan="3"><p>`com.cerebro.domino.telemetry.deploymentName`</p></td>
    </tr>

    <tr>
      <td />

      <td><p>(value set at install time)</p></td>
      <td><p>Sets the `deployment_name` value on telemetry events, identifying this environment.</p></td>
    </tr>
  </tbody>
</table>

## Usage reports

These options relate to the [User Activity Reports](/6.3/admin/identity-and-access/manage-users/run-user-activity-report).

<table>
  <thead>
    <tr>
      <th>Key</th>
      <th>Default</th>
      <th>Description</th>
    </tr>
  </thead>

  <tbody>
    <tr>
      <td colSpan="3"><p>`com.cerebro.domino.email.usageReportRecipient`</p></td>
    </tr>

    <tr>
      <td />

      <td><p>`usage@dominodatalab.com`</p></td>
      <td><p>Sets the default recipient for the user activity report. To access this report, go to <strong>Admin</strong> > <strong>Advanced</strong> > <strong>User Activity Report</strong>.</p></td>
    </tr>

    <tr>
      <td colSpan="3"><p>`com.cerebro.domino.email.EmailToDomino`</p></td>
    </tr>

    <tr>
      <td />

      <td><p>`true`</p></td>
      <td><p>When `true`, the system sends a scheduled user activity report to <a href="mailto:usage@dominodatalab.com">[usage@dominodatalab.com](mailto:usage@dominodatalab.com)</a> to help improve Domino.</p></td>
    </tr>

    <tr>
      <td colSpan="3"><p>`com.cerebro.domino.Usage.RecentUsageDays`</p></td>
    </tr>

    <tr>
      <td />

      <td><p>`30`</p></td>
      <td><p>Specifies the number of days to report for recent activity in the user activity reports. For example, the default value includes activity within the past 30 days in the Recent Activity section.</p><p>WARNING: The cron entry is set in UTC.</p></td>
    </tr>

    <tr>
      <td colSpan="3"><p>`com.cerebro.domino.Usage.ReportFrequency`</p></td>
    </tr>

    <tr>
      <td />

      <td><p>`0 0 2 * * ?`</p></td>
      <td><p>Defines the frequency for automatically scheduled user activity reports. The default cron string value is set to daily at 02:00.</p><p>NOTE: This value must be a QUARTZ cron string expression. See the <a href="http://www.quartz-scheduler.org/documentation/quartz-2.3.0/tutorials/crontrigger.html">Cron Quartz tutorial</a>.</p></td>
    </tr>

    <tr>
      <td colSpan="3"><p>`com.cerebro.domino.Usage.ReportRecipients`</p></td>
    </tr>

    <tr>
      <td />

      <td><p>Empty</p></td>
      <td><p>Identifies a comma-separated list of email addresses that receive automatic scheduled user activity reports. This is not shown in the Configuration record unless it is set explicitly. Example values are: `email1@domain.com`, `email2@domain.com`.</p></td>
    </tr>

    <tr>
      <td colSpan="3"><p>`com.cerebro.domino.Usage.IncludeUsernameAndEmail`</p></td>
    </tr>

    <tr>
      <td />

      <td><p>`false`</p></td>
      <td><p>When `true`, automatically generated and emailed user activity reports include username and email address columns.</p></td>
    </tr>
  </tbody>
</table>

## Vault

In Domino, secrets are stored in an instance of HashiCorp Vault. By default, Vault does not require any configuration for specific secrets to be stored in encrypted form at rest. Supported Secrets are:

* User environment variables

* User API keys

* Data source access secrets

* Project environment variables

The following configuration settings are used to connect to Vault.

<table>
  <thead>
    <tr>
      <th>Key</th>
      <th>Default</th>
      <th>Description</th>
    </tr>
  </thead>

  <tbody>
    <tr>
      <td colSpan="3"><p>`com.cerebro.domino.vault.auth.token.tokenFile`</p></td>
    </tr>

    <tr>
      <td />

      <td><p>N/A</p></td>
      <td><p><strong>Beta feature:</strong> Contact your Domino representative for assistance. Used to configure Domino to work with your Vault installation outside the Domino cluster.</p> <p>This is the path where the Vault token is present. If the .token config key is present, this is ignored.</p></td>
    </tr>

    <tr>
      <td colSpan="3"><p>`com.cerebro.domino.vault.auth.token.token`</p></td>
    </tr>

    <tr>
      <td />

      <td><p>N/A</p></td>
      <td><p><strong>Beta feature:</strong> Contact your Domino representative for assistance. Used to configure Domino to work with your Vault installation outside the Domino cluster.</p> <p>This is the literal value of the Vault token that overrides the `.tokenFile` config key.</p></td>
    </tr>

    <tr>
      <td colSpan="3"><p>`com.cerebro.domino.vault.auth.token.refreshEvery`</p></td>
    </tr>

    <tr>
      <td />

      <td><p>N/A</p></td>
      <td><p><strong>Beta feature:</strong> Contact your Domino representative for assistance. Used to configure Domino to work with your Vault installation outside the Domino cluster.</p> <p>Specifies how often to reread the token when configuring an external Vault integration. This setting is only useful when the token is configured with `tokenFile`. Example values are: `2s`, `10m`, `1h`. See <a href="https://github.com/lightbend/config/blob/master/HOCON.md#duration-format">duration format</a> for syntax information.</p></td>
    </tr>

    <tr>
      <td colSpan="3"><p>`com.cerebro.domino.vault.secretstore.baseUrl`</p></td>
    </tr>

    <tr>
      <td />

      <td><p>N/A</p></td>
      <td><p><strong>Beta feature:</strong> Contact your Domino representative for assistance. Used to configure Domino to work with your Vault installation outside the Domino cluster.</p> <p>The URL with port for the Vault’s API endpoint which is used to configure the external Vault integration.</p></td>
    </tr>

    <tr>
      <td colSpan="3"><p>`com.cerebro.domino.vault.secretsengine.kv2.basePath`</p></td>
    </tr>

    <tr>
      <td />

      <td><p>`domino/kv`</p></td>
      <td><p><strong>Beta feature:</strong> Contact your Domino representative for assistance. Used to configure Domino to work with your Vault installation outside the Domino cluster.</p> <p>The path in the Vault to the key-value store that Domino uses.</p></td>
    </tr>

    <tr>
      <td colSpan="3"><p>`com.cerebro.domino.vault.secretsengine.kv2.subPath`</p></td>
    </tr>

    <tr>
      <td />

      <td><p>`nucleus`</p></td>
      <td><p><strong>Beta feature:</strong> Contact your Domino representative for assistance. Used to configure Domino to work with your Vault installation outside the Domino cluster.</p> <p>An optional path in the key-value store that serves as the root for all Domino-stored secrets.</p></td>
    </tr>
  </tbody>
</table>

## White labeling

Use these options to customize the Domino application with your organization’s brand. See [Customize the Domino UI](/6.3/admin/configuration/customize-ui).

<table>
  <thead>
    <tr>
      <th>Key</th>
      <th>Default</th>
      <th>Description</th>
    </tr>
  </thead>

  <tbody>
    <tr>
      <td colSpan="3"><p>`com.cerebro.domino.frontend.footerCustomization.customContactUsHref`</p></td>
    </tr>

    <tr>
      <td />

      <td><p>N/A</p></td>
      <td><p>Set a URL that directs your users to a web-based form or email address (`mailto:support@domain.com`).</p></td>
    </tr>

    <tr>
      <td colSpan="3"><p>`com.cerebro.domino.frontend.footerCustomization.customFooterHtml`</p></td>
    </tr>

    <tr>
      <td />

      <td><p>N/A</p></td>
      <td><p>Set the custom HTML to show immediately above the page footer.</p></td>
    </tr>

    <tr>
      <td colSpan="3"><p>`com.cerebro.domino.frontend.footerCustomization.customFooterImageUrl`</p></td>
    </tr>

    <tr>
      <td />

      <td><p>N/A</p></td>
      <td><p>Set the URL for the image that you want shown in the footer. The image displays on the same line as the Domino logo. If `customFooterHTML` is set, this displays below the custom HTML, inside the footer.</p></td>
    </tr>

    <tr>
      <td colSpan="3"><p>`com.cerebro.domino.whitelabel.jsonConfig`</p></td>
    </tr>

    <tr>
      <td />

      <td><p>N/A</p></td>
      <td><p>A JSON-formatted list of white labeling configuration parameters (see example below).</p></td>
    </tr>
  </tbody>
</table>

Example of a JSON-formatted list of white labeling configuration parameters:

```json theme={null}
{
"appLogo": "https://s3-us-west-2.amazonaws.com/your-logo.png",
"appName": "Your Company Name",
"favicon": "https://www.your-website.com/favicon.ico",
"helpContentUrl": "https://your-support-website.com",
"showSupportButton": true,
"supportEmail": "support@your-email-domain.com",
"errorPageContactEmail": "support-error@your-email-domain.com",
"hidePopularProjects": true,
"hideSuggestedProjects": true,
"gitCredentialsDescription": "Authenticate to your Git Account by clicking Add a New Git Credential",
"hideDownloadDominoCli": true,
"pageFooter": "<p>Your Custom Footer</p>",
"hideSearchableProjects": true
}
```

## Workloads

These options relate to Domino Workspaces, Jobs and Apps.

<table>
  <thead>
    <tr>
      <th>Key</th>
      <th>Default</th>
      <th>Description</th>
    </tr>
  </thead>

  <tbody>
    <tr>
      <td colSpan="3"><p>`com.cerebro.domino.executor.workingDirectoryPrep.timeout`</p></td>
    </tr>

    <tr>
      <td />

      <td><p>`15m`</p></td>
      <td><p>Controls the default preparing timeout (in minutes) to move files to the execution. For large amounts or sizes of files, consider making use of <a href="/6.3/platform-capabilities/core-concepts/data/datasets">Domino Datasets</a>.</p></td>
    </tr>
  </tbody>
</table>

### Workspaces

These options relate to Domino workspaces.

<table>
  <thead>
    <tr>
      <th>Key</th>
      <th>Default</th>
      <th>Description</th>
    </tr>
  </thead>

  <tbody>
    <tr>
      <td colSpan="3"><p>`com.cerebro.domino.workbench.project.defaultVolumeSizeGiB`</p></td>
    </tr>

    <tr>
      <td />

      <td><p>`10`</p></td>
      <td><p>Controls default allocated persistent volume size for a new workspace.</p></td>
    </tr>

    <tr>
      <td colSpan="3"><p>`com.cerebro.domino.workbench.project.minVolumeSizeGiB`</p></td>
    </tr>

    <tr>
      <td />

      <td><p>`4`</p></td>
      <td><p>Controls min allocated persistent volume size for a new workspace.</p></td>
    </tr>

    <tr>
      <td colSpan="3"><p>`com.cerebro.domino.workbench.project.maxVolumeSizeGiB`</p></td>
    </tr>

    <tr>
      <td />

      <td><p>`200`</p></td>
      <td><p>Controls max allocated persistent volume size for a new workspace.</p></td>
    </tr>

    <tr>
      <td colSpan="3"><p>`com.cerebro.domino.workbench.workspace.maxWorkspacesPerUserPerProject`</p></td>
    </tr>

    <tr>
      <td />

      <td><p>`4`</p></td>
      <td><p>Sets a limit on the number of provisioned workspaces per user per project.</p></td>
    </tr>

    <tr>
      <td colSpan="3"><p>`com.cerebro.domino.workbench.workspace.maxWorkspacesPerUser`</p></td>
    </tr>

    <tr>
      <td />

      <td><p>`16`</p></td>
      <td><p>Sets a limit on the number of provisioned workspaces per user across all projects.</p></td>
    </tr>

    <tr>
      <td colSpan="3"><p>`com.cerebro.domino.workbench.workspace.maxWorkspaces`</p></td>
    </tr>

    <tr>
      <td />

      <td><p>`3000`</p></td>
      <td><p>Sets a limit on the number of provisioned workspaces across the whole Domino.</p></td>
    </tr>

    <tr>
      <td colSpan="3"><p>`com.cerebro.domino.workbench.workspace.maxAllocatedVolumeSizeAcrossAllWorkspacesGiB`</p></td>
    </tr>

    <tr>
      <td />

      <td><p>`None`</p></td>
      <td><p>Sets a limit on the total volume size of all provisioned workspaces across the whole Domino combined.</p></td>
    </tr>

    <tr>
      <td colSpan="3"><p>`com.cerebro.domino.workbench.workspace.stopToDeleteDelayDuration`</p></td>
    </tr>

    <tr>
      <td />

      <td><p>`20.seconds`</p></td>
      <td><p>The number of seconds the frontend waits after the workspace stops before making the delete request to the backend. This allows for enough time after workspace stop for the workspace’s persistent volume to be released. If users frequently receive an error after trying a delete, then this value should be increased.</p></td>
    </tr>

    <tr>
      <td colSpan="3"><p>`com.cerebro.domino.workbench.workspace.volume.enableSnapshots`</p></td>
    </tr>

    <tr>
      <td />

      <td><p>`true`</p></td>
      <td><p>Whether to capture snapshots of workspace persistent volumes in AWS. Workspace volume snapshotting is disabled for remote data planes.</p></td>
    </tr>

    <tr>
      <td colSpan="3"><p>`com.cerebro.domino.workbench.workspace.volume.snapshotCleanupFrequency`</p></td>
    </tr>

    <tr>
      <td />

      <td><p>`1.day`</p></td>
      <td><p>How often to delete all but the X most recent snapshots , including snapshots of deleted workspaces. Where X is a number defined by `workbench.workspace.volume.numSnapshotsToRetain`. Only snapshots older than two hours are cleaned up. Snapshots of deleted workspaces are cleaned up regardless of their age.</p></td>
    </tr>

    <tr>
      <td colSpan="3"><p>`com.cerebro.domino.workbench.workspace.volume.numSnapshotsToRetain`</p></td>
    </tr>

    <tr>
      <td />

      <td><p>`5`</p></td>
      <td><p>The number of snapshots to retain. All older snapshots beyond this limit will be deleted during a periodic cleanup. Domino does not retain snapshots for deleted workspaces.</p></td>
    </tr>

    <tr>
      <td colSpan="3"><p>`com.cerebro.domino.workbench.workspace.volume.recommendedSizeFactor`</p></td>
    </tr>

    <tr>
      <td />

      <td><p>`1.2`</p></td>
      <td><p>The number by which Domino multiples the project size to calculate the recommended volume size.</p></td>
    </tr>

    <tr>
      <td colSpan="3"><p>`com.cerebro.domino.workbench.workspace.volume.highDiskUsageThresholdPercent`</p></td>
    </tr>

    <tr>
      <td />

      <td><p>`90`</p></td>
      <td><p>The threshold, as a percentage, at which Domino notifies users and recommends reducing the project size or adjusting the volume size to avoid performance issues.</p></td>
    </tr>

    <tr>
      <td colSpan="3"><p>`com.cerebro.domino.workbench.workspace.enabledPVCleanup`</p></td>
    </tr>

    <tr>
      <td />

      <td><p>`false`</p></td>
      <td><p>"True" to enable the unused workspace volume cleaner job, which deletes unused disk volumes to reduce cost.</p></td>
    </tr>

    <tr>
      <td colSpan="3"><p>`com.cerebro.domino.workbench.workspace.cleanupFrequencyDays`</p></td>
    </tr>

    <tr>
      <td />

      <td><p>`1.day`</p></td>
      <td><p>The frequency, in days, at which the workspace volume cleaner job runs.</p></td>
    </tr>

    <tr>
      <td colSpan="3"><p>`com.cerebro.domino.workbench.workspace.idlePeriodThresholdDays`</p></td>
    </tr>

    <tr>
      <td />

      <td><p>`10`</p></td>
      <td><p>The number of days a workspace can remain unused before it is marked for deletion and the grace period begins.</p></td>
    </tr>

    <tr>
      <td colSpan="3"><p>`com.cerebro.domino.workbench.workspace.unusedGracePeriodDays`</p></td>
    </tr>

    <tr>
      <td />

      <td><p>`30`</p></td>
      <td><p>The number of days between when a workspace is marked for deletion and when it is actually deleted, also called the grace period. During this period, the workspace owner is notified in Domino and through email.</p></td>
    </tr>

    <tr>
      <td colSpan="3"><p>`com.cerebro.domino.workbench.workspace.persistence.packages.enabled`</p></td>
    </tr>

    <tr>
      <td />

      <td><p>`false`</p></td>
      <td><p>If set to `true`, users have the option to persist packages in environments between Workspace sessions.</p></td>
    </tr>

    <tr>
      <td colSpan="3"><p>`com.cerebro.domino.workbench.workspace.persistence.directories.enabled`</p></td>
    </tr>

    <tr>
      <td />

      <td><p>`false`</p></td>
      <td><p>If set to `true`, adds an option on the Workspace Launch modal to persist the home directory contents between Workspace sessions.</p></td>
    </tr>
  </tbody>
</table>

## Workspace File Audit App

Configure event capture frequency and which operations to track. Event logging applies to all workspace files across all users and increases compute consumption by approximately 10–15% during active sessions. You can’t restrict logging to specific datasets or projects.

<Tip>
  Shorter deduplication intervals capture more events, which increases storage volume and may impact performance.
</Tip>

<table>
  <thead>
    <tr>
      <th>Key</th>
      <th>Default</th>
      <th>Description</th>
    </tr>
  </thead>

  <tbody>
    <tr>
      <td colSpan="3"><p>`com.cerebro.domino.workspaceFileAudit.eventProcessingInMinutes`</p></td>
    </tr>

    <tr>
      <td />

      <td><p>`60`</p></td>
      <td><p>Frequency (in minutes) for processing and persisting captured workspace events. A value of `60` means that new events will appear in the App every 60 minutes.</p></td>
    </tr>

    <tr>
      <td colSpan="3"><p>`com.cerebro.domino.workspaceFileAudit.TrackedEventTypes`</p></td>
    </tr>

    <tr>
      <td />

      <td><p>`Read, Write, Delete, Create, Rename`</p></td>
      <td><p>Defines which file operations to track. Events added to this list are the dataset/netapp events being tracked by falco and stored in the workspace audit trail.</p></td>
    </tr>

    <tr>
      <td colSpan="3"><p>`com.cerebro.domino.workspaceFileAudit.UniqueReadEventPeriodInMinutes`</p></td>
    </tr>

    <tr>
      <td />

      <td><p>`60`</p></td>
      <td><p>Deduplication window for file read events. Events that are exactly the same within this time interval are treated as duplicated and only 1 event will be recorded.</p></td>
    </tr>

    <tr>
      <td colSpan="3"><p>`com.cerebro.domino.workspaceFileAudit.UniqueWriteEventPeriodInMinutes`</p></td>
    </tr>

    <tr>
      <td />

      <td><p>`60`</p></td>
      <td><p>Deduplication window for file write events. Events that are exactly the same within this time interval are treated as duplicated and only 1 event will be recorded.</p></td>
    </tr>
  </tbody>
</table>