Application Setup

There are many settings that the administrator needs to manage. These settings are applied globally, so it is important to understand the meaning of each item and their impact on the application.

The setup screen is organised in five tabs:

• General - company information and notification preferences
• Planning - defaults that drive how the planning board behaves
• Map - map and routing defaults
• Mobile - settings that affect the mobile app
• Preview - feature flags for experimental and opt-in capabilities

General

Field	Description
Company name	The company name.
Company address	The primary address. This address is used as the default location on the map.
Company address country	The primary address' country.
Duration format	How the planning totals on a task (required, planned, remaining) should be displayed. Options: Decimal, Hour, Day and Decimal, Day and Hour.
Notification email	Optional email address that receives system notifications such as setup import results.
API key expiry reminder frequency	When and how often administrators are reminded that an API key is about to expire. Options: Disabled, 1 month before, 2 weeks before, 1 week before, 3 days before, 1 day before. See API keys for the underlying expiration mechanism.

Planning

The Planning tab is grouped into four cards: a generic block, Time Windows, Visualization, and Calendars.

Generic

Field	Description
Enable appointment containers	Feature flag to toggle appointment containers.
Multi-day capacity distribution mode	Controls how the capacity is calculated for multi-day appointments. Options: None, Constant, Even. To learn what these do, continue here.
Do not count appointment resource	When enabled, the resource that owns an appointment is not counted toward the appointment's resource quantity. Useful when one resource always supervises rather than performs.
Disable recalculate planning quantity	When enabled, Dime.Scheduler stops recalculating planned and remaining quantities on the task whenever appointments change. Use this only when a back-office system owns those values.

Time Windows

Field	Description
Apply requested dates	When activated, appointments are created from the task's Requested start date and Requested end date fields. Read more about this here.
Apply requested times	When activated, appointments are created from the task's Requested start time and Requested end time fields. Read more about this here.
Respect allowed date constraints	When activated, extra data validation is executed on tasks. Read more about this here.

Visualization

Field	Description
Enable planning board tooltip	When activated, hovering over an appointment on the planning board shows a tooltip. The tooltip's content is configured in Field Templates.
Render category in background	When enabled, all grid-based components displaying appointment or task data render the category color in the row background.
Alternate rows	When enabled, all grid-based components in the planning view show alternating row colors.

Calendars

Field	Description
Enable resource calendar visualisation	When enabled, resource availability is visualised in the planning board. Read more about it here.
Resource zone color	Color picker for the background color of non-working times in the planning board. Read more about it here.
Resource calendar recalculation mode	Controls how appointments react when they overlap with a resource's non-working time. Options: None (no automatic recalculation), Extend duration (extend the appointment to compensate for non-working time), Update planning quantity (keep the duration but adjust the planned quantity).

Applying requested dates

When you drag and drop a task from the open task list onto the planning board, this setting forces an appointment to be created using the Requested start date and Requested end date parameters of the task:

• When only the Requested start date is populated, the appointment is created on the Requested start date with the duration as specified on the task's Duration value.
• If both Requested start date and Requested end date are filled out, an appointment is created with start and end dates equal to the requested start and end dates.

Applying requested times

The scope of this setting is nearly identical to the requested dates feature but with one different detail: instead of applying dates, this feature applies only hours and minutes; thus it does not affect the date.

Respect allowed date constraints

When you drag and drop an appointment, this setting disallows the user to place an appointment outside the Earliest allowed date or Latest allowed date, which is data that can be found on the task.

Appointments that are created manually or backed by tasks that have no requirements set on these fields are not impacted by this restricted planning mode.

Calendars

Calendars are used to define common work patterns. They are used in the Gantt chart and the planning board.

Calendars fulfill two functions in the planning board:

• Showing unavailable working times for each resource
• Recalculating the duration of an appointment to take non-working time into account

These are reflected in the following three configuration items:

• Enable resource calendar visualisation
• Resource zone color
• Resource calendar recalculation mode

The first two are particularly useful for the planner because the user actually sees when resources are available. The recalculation mode is part of the optimization suite and is quite powerful: when an appointment is created or updated, the application can automatically extend the duration to make sure the resource can finish the task according to their calendar. For example, if a resource has a normal nine-to-five job and is scheduled to perform a two-hour task at four o'clock, then the application is smart enough to set the end date to the following day at ten o'clock. The planner can always override this behavior in the planning board or the appointment, which is a good example of the multi-layered configuration mechanism Dime.Scheduler applies:

Map

Field	Description
Calculate route and travel time	Activate automatic route calculation on the map. A route is calculated between all selected tasks and appointments.
Unit of distance	Select the unit in which the calculated distance is displayed on the map. Options: Kilometer, Mile.
Route profile	The vehicle profile used for route, distance and travel time calculation. Options: Car, Van, Truck, Motorcycle, Bicycle, Pedestrian.
Show waypoints	Show the route selection sequence by displaying a number in the pins on the map.

There are heaps of features on the map, just as there are many configurable items on multiple levels. The highest configuration level is, of course, the application setup. However, users are free to override the following elements on the user profile level:

• Calculate route and travel time
• Unit of distance
• Route profile
• Show waypoints

The best way to understand this multi-layered configuration mechanism is via the following graph:

Like the above image suggests, the different levels are cascading. The application setup provides the default configuration but can be overridden by users on the user profile level and ultimately on the map itself.

Client secret expiration reminders

Dime.Scheduler monitors the expiration dates of client secrets configured in the application setup and the Exchange setup, and sends reminders before they expire. This prevents service disruptions caused by expired credentials.

• Expiration tracking: secrets across the application and Exchange setup are watched continuously.
• Proactive reminders: notifications go out ahead of the expiration date, giving you time to renew.

Mobile

Field	Description
Visibility for locked appointments	Controls how the mobile app treats appointments whose Locked flag is set. Options: Locked (the appointment is shown but cannot be modified) or Hidden (the appointment does not appear in the mobile agenda at all).

Preview

The items in this tab are subject to change. They cover experimental flags, deprecated toggles that are kept around for backwards compatibility, and configuration for opt-in capabilities such as route optimization and the AI Chat. For an overview of what each experimental flag does in the planning view itself, see Experimental features.

Solver & optimization

Field	Description
Solver API key	API key for the route-optimization solver. Required for any of the optimization features below.
Enable route optimization	Adds the Optimize route action to the route sequence. Requires the Advanced Map license.
Enable field service solver	Enables the Vehicle Routing Problem (VRP) solver, used by the planning board and the optimize_field_service MCP tool to assign and sequence appointments across resources. Requires the Field Service Optimizer optional module.

Planning board

Field	Description
Recalculate travel time	Deprecated. Original travel-time recalculation switch. New deployments should use the route-sequence flow instead. Read more here.
Planning board zoom	Deprecated. When switched on, you can zoom in and out on the planning board with Ctrl + scroll. Replaced by the new planning board.
New planning board	Switches the planning board to the new rendering engine.

AI Chat

These settings configure the in-product AI Chat. When the chat is enabled but no API key is configured, the chat panel shows a configuration prompt instead of the conversation UI.

Field	Description
Show AI chat	Toggles the AI Chat panel in the planning view.
Provider	LLM provider to use. Options: OpenAI, Anthropic, Azure OpenAI.
Model	Model identifier (e.g. gpt-4o-mini, claude-haiku-4-5-20251001). Leave blank to use the provider default.
API key	The API key for the selected provider.
Endpoint	Azure OpenAI only. The Azure resource endpoint (e.g. https://<resource>.openai.azure.com).
Deployment	Azure OpenAI only. The deployment name configured in Azure.

Read more

• Gantt chart component
• Planning board component
• Map component
• Route sequence component
• AI Chat
• Experimental features