Administering Dime.Scheduler

Administering Dime.Scheduler means deciding how it behaves for everyone who plans in it: what data flows in from the back office, what planners see, and who is allowed to do what. This section is your map to all of it.

Common starting points

Pick the entry point that matches today's task.

Implementation checklist

End-to-end setup walkthrough for a new tenant

BC quick start

Spin up Business Central + Dime.Scheduler on Docker

Connectors

Wire up data flow between Dime.Scheduler and your back-office

User setup

Create accounts, assign roles, and group users

Exchange setup

Two-way calendar sync with Microsoft 365

What's in here

Set up the application

Global configuration, API keys, and connectors that define how Dime.Scheduler behaves and what data flows in.

Manage users & access

Users, user groups, roles, and permissions for your Dime.Scheduler instance.

Set up planning data

Resources, calendars, templates, and indicators - the building blocks planners work with.

Monitor transactions

Track the appointments and master data flowing to the back office, and resolve transaction errors.

System & license

License usage, version information, and overall system health.

Setup packages

Package configuration and replay it across environments and tenants.

Where the data flows

Dime.Scheduler sits between your back-officeBack officeThe ERP or business system Dime.Scheduler plans for - most often Microsoft Dynamics 365 Business Central. It owns the master data and remains authoritative over what it receives. system (BC, NAV, CRM, custom) and your dispatchers. ConnectorsConnectorAn integration that links Dime.Scheduler to a back-office system, routing data in and scheduling decisions back out. define how data moves in and out; resourcesResourceAn entity that can carry out work - a person, vehicle, tool, or room - that you schedule on the planning board., calendarsCalendarA definition of when work can happen, for the whole tenant or for specific resources: business hours, weekends and holidays. Calendars shade non-working time on the planning board and skip it in Gantt durations., and templates define what dispatchers see; users, rolesUser roleA named bundle of user actions assigned to users and user groups. Permissions flow through roles, never directly to a user., and groups define who can do what. Most administration tasks fall into one of those three buckets.

Something not working?

Common admin issues, transaction errors, and system monitoring - all in one place.

Open troubleshooting

Setting up a new tenant? Start with the implementation checklist for the end-to-end path. Everything else is in the sidebar on the left.