What Is the Registry?
Every organization that uses Dash360 is different. One client needs currency values displayed in thousands (“K values”), another needs eight decimal places. One project tracks contingency; an operational project wants it completely hidden. Some organizations use “Labour” and “Non-Labour” (UK spelling), others use the US equivalents. The Registry is Dash360’s answer to this problem. It is a centralized configuration database that controls how Dash360 looks and behaves (from display formatting to which features are visible) without requiring any code changes or redeployments. Think of it like the Windows Registry, but purpose-built for enterprise project management software. Administrators configure it through the Admin area; the rest of the application reads it dynamically on every page load.Registry Sets and Registry Items
The Registry system has two components that work together: Registry Items are individual settings: key/value pairs that control a specific behavior. Examples:Currency-Format, Labor-Title, CostEstimatingForm-Hide-Travel. Each item has a name, a value, and a type (toggle On/Off, or free-form text).
Registry Sets are named collections of Registry Items. A Registry Set captures a complete configuration profile. Examples: “US Government Standard”, “UK Client Config”, “Development Testing”.
Every project in Dash360 is assigned exactly one Registry Set. This means:
- Multiple projects can share a Registry Set (and automatically inherit any changes to it).
- A single organization can have projects with completely different configurations by assigning them to different Registry Sets.
- The same Dash360 instance can serve multiple clients with distinct requirements; all from one codebase.
How Value Resolution Works
When Dash360 needs a configuration value, it checks three levels in order:
Personal preferences override project settings, which override system defaults. This means a user can choose their own display preferences without affecting colleagues on the same project.
User-overridable settings are limited to display preferences: currency format, currency symbol visibility, decimal places, and comma separators.
Registry Settings Reference
The following tables list all available Registry settings, organized by category.Display & Formatting
Resource Categories
Contingency & Risk
Budget Form (Cost Estimating Form)
The Budget Form can be extensively customized. These settings use theCostEstimatingForm prefix because the Budget Form was originally called the Cost Estimating Form.
Work Package Report
Reports & Display
System Features
CAM Features
File Storage & AWS
Advanced Features
Where to Configure Registry Settings
Registry settings are managed in the Admin area by administrators. See Admin; Registry for step-by-step instructions on creating Registry Sets, editing items, and assigning a Registry Set to a project.Common Customizations
Here are five real-world examples of what organizations use Registry settings for: UK spelling for resource categories: SetLabor-Title to Labour, Non-Labor-Title to Non-Labour. The change takes effect immediately across all grids, reports, and forms for that project.
K-value currency display: Set Currency-Format to K Value. All cost figures across the application display divided by 1,000, making large budgets easier to read without changing any underlying data.
Simplifying the Budget Form: An organization that does not use travel resources can set CostEstimatingForm-Hide-Travel to On. The Travel section disappears from the Budget Form for every user on that project.
Custom CAM label: Organizations that use the title “Project Manager” instead of “Control Account Manager” can set CAM to Project Manager. The label updates everywhere the CAM field appears.
Enabling contingency at the resource assignment level: Set Contingency-at-Resource-Assignment-Level to On to allow separate contingency percentages on each resource assignment rather than a single entry per work package. See Contingency Methodology for a full explanation of the four contingency modes.