Application Settings
Dime.Scheduler configures behavior in layers. Understanding how those layers interact is key to setting up the application so it stays both flexible and predictable.
The highest level applies unless a lower, more specific level overrides it. Set a value on the user profile or layout to see it win; switch it back to Inherit to fall through.
The configuration cascades. Administrators set the default behavior of the application. Planners can then deviate from those defaults by customizing their own user profiles and components (layouts). This split of responsibilities may look complex at first, but it is what lets the system stay flexible without becoming unpredictable.
The highest level of configuration is the administrator's responsibility. Unlike the static configuration, this global configuration affects how Dime.Scheduler's planning capabilities actually work. Turning on the "Apply requested dates" switch, for example, has a profound effect on the planning board.
The next two levels belong to the planner. Users manage their own profiles and layouts. Some buttons and switches override the higher levels (such as the "unit of distance" flag or the "ignore calendars" mode on the planning board or appointment), while others simply extend the application's behavior (like the planning board's start date or snap interval).
The rule of thumb across these layers is straightforward:
The highest level of a given configuration item is applied unless a lower level overrides it.
The top two levels are easy to grasp because there are only so many setups to do. Profiles and layouts, on the other hand, have no limits and can produce very different planning views.
This section covers the static and global configuration. For user-level configuration, continue here.
Application Setup
5 items
API keys
Authenticate through API keys
Connectors
Link Dime.Scheduler to any back-office system.