- In Domino, click on your avatar, then go to Admin Panel > Platform settings > Configuration records.
- Configure the necessary settings. Fields left blank will use default values (as indicated in the tables below).
- Click Save Configuration, which will trigger a brief Nucleus restart to apply the changes.
Apps
Controls limits on App publishing within Projects.| Setting | Default | Description |
|---|---|---|
| Max Active App Runs per Project | 4 | Maximum number of simultaneously running Apps allowed in a single Project. |
| Max Apps per Project | 10 | Maximum number of Apps that can be created in a single Project. |
Compute Grid
Controls execution queuing behavior across the platform.| Setting | Default | Description |
|---|---|---|
| Global Execution Queue Limit | 1000 | Maximum number of executions that can be queued across all users at one time. |
| Max Executions per User | 25 | Maximum number of executions a single user can run concurrently before their additional executions are queued. |
Environments
Controls environment customization options available to users.| Setting | Default | Description |
|---|---|---|
| Custom File Handlers | False | When enabled, users can define custom file handlers that override the default behavior for supported file types. |
Long-Running Workspaces
Controls detection, notification, and automatic shutdown policies for long-running Workspaces. Configure long-running workspaces has more information about the auto shutdown behavior of long-running workspaces.| Setting | Default | Description |
|---|---|---|
| Long-Running Threshold | 86400 | Time in seconds a Workspace must be running before it is considered long-running. Long-running Workspaces are eligible for automatic shutdown and notifications. |
| Max Workspace Lifetime | 259200 | Maximum Workspace lifetime in seconds that a user can configure before the platform forces automatic shutdown. |
| Notifications Enabled | False | When enabled, users may opt in to receive email notifications for their long-running Workspaces. |
| Notifications Required | False | When enabled, all users will always receive email notifications for their long-running Workspaces, regardless of their personal preference. |
| Auto-Shutdown Enabled | False | When enabled, users can choose to have their long-running Workspaces automatically shut down after the configured threshold. |
| Auto-Shutdown Required | False | When enabled, long-running Workspaces are automatically shut down for all users. Users cannot override this behavior. |
- Auto-Shutdown Required takes precedence over Auto-Shutdown Enabled.
- Notifications Required takes precedence over Notifications Enabled.
Restricted Environments and Projects
Controls access isolation between environments and Projects.| Setting | Default | Description |
|---|---|---|
| Restricted Assets Enabled | False | When enabled, administrators can mark individual environments and Projects as restricted. Executions in restricted Projects can only run in environments that are also marked as restricted. |
Workloads
Controls Workspace provisioning limits per user.| Setting | Default | Description |
|---|---|---|
| Max Workspaces per User | 16 | Maximum number of Workspaces a single user can have provisioned at one time, across all Projects. |
| Max Workspaces per User per Project | 4 | Maximum number of Workspaces a single user can have provisioned within a single Project. |