# Scheduler settings

> **Set up with an AI agent:** Connect Chrona MCP for documentation, setup guidance and configuration recipes. Server: https://mcp.chrona365.com/mcp (Streamable HTTP; authentication: None). Your agent needs separately authorized Dataverse tools to apply changes. In Copilot Studio, after importing Chrona, add the Chrona Scheduler connector to your agent alongside Microsoft’s Dataverse tools. [Connection guide](https://chrona365.com/workforce/install-with-an-agent).

Each scheduler has its own shift scheduling settings: its board's display, its roster period, its roles and skills, its rules, its goals, its call-out and who has access. A change applies to everyone who uses the scheduler.

## Open the settings

1. In the **Chrona Workforce Scheduler** app, open **Schedulers** and open the scheduler.
2. Select the gear on its board, **Scheduler settings**. The settings open under the board.

The gear opens the section you used last, or **General** the first time. One section is open at a time, and each shows a short summary beside its name.

**Save** keeps the changes in every section at once, and **Discard changes** puts the saved values back. Closing the settings with unsaved changes asks first. A field with a problem says what to enter, and **Save** opens the first section that holds one.

**Shift types**, **Coverage** and **Groups** open on pages of their own, and a demand driver's values on its form; each saves there. Staffing standards and their values save with their own **Save**.

## Who can change them

| Who | What they can do |
| --- | --- |
| **Use scheduler** | Plan and publish shifts, and decide requests. They do not see the gear. |
| **Change settings** | Also see the gear and change these settings. |
| **Chrona administrators** | Users with the **Chrona Workforce Admin** or **System Administrator** role use and change every scheduler. |

Set both lists in [Access](https://chrona365.com/docs/workforce/scheduler-settings#access). Chrona refuses a change to a scheduler's settings from anyone else, with the reason.

## General

| Setting | What it does | Empty or default |
| --- | --- | --- |
| **Name** | The scheduler's name, as the app shows it in its lists. | Required. |
| **Site** | The site this scheduler plans. The board shows the site's time zone, for everyone, and takes the site's week start, both shown under the field; new shifts get this site. Change those two on the site. | Empty until you choose one. |

### Display

| Setting | What it does | Empty or default |
| --- | --- | --- |
| **Layout** | The layout the board shows to everyone who opens this scheduler: **Timeline**, **Roster grid**, **Top-down** or **Agenda**. | **Roster grid**. |
| **Color by** | What colors the shifts: each role's color (**Role**), a color per group (**Group**), a warning color on open shifts (**Status**), or **None**. | **None**. |
| **Working start**, **Working end** | The board shades the hours before the start and after the end, and the **Working hours rule** checks shifts placed there. An end before the start runs past midnight: 21:00 to 05:00 ends at 05:00 the next day. | No shading. |
| **Show weekends** | **On** shows Saturdays and Sundays on the board; **Off** hides them. | **On**. |
| **Slot length** | The step shifts snap to when you drag or resize them, from 30 to 240 minutes; zooming out makes it larger. A planner's own time scale on the board comes first. | 30 minutes. |
| **Hour width** | How wide an hour is when the board shows one day, from 20 to 400 pixels. Week and month fit the board, and a planner's own zoom comes first. | 60 pixels. |

### Shift menu

| Setting | What it does | Empty or default |
| --- | --- | --- |
| **Show Open in form** | **On** shows **Open in form** in a shift's right-click menu, which opens the shift's form. **Off** hides it. | **On**. |
| **Show app commands** | **On** shows the app's own commands for a shift in its right-click menu. **Off** hides them. When the app cannot hand them over, the menu says so in a grayed-out line. | **On**. |

## Roster period

| Setting | What it does | Empty or default |
| --- | --- | --- |
| **Period** | The roster period you plan and publish: **Week**, **Fortnight** or **Month**. **Turn period off** clears it. | Off: you plan one week at a time. |
| **Period starts on** | The first day of the first roster period; the next periods follow on from it. Choosing a period fills in a start when there is none, and the hint shows the current period. A month always runs from the 1st to its last day, so this date is fixed for **Month**. | Required with **Week** or **Fortnight**. |

Generate, Auto Schedule, the planning horizon and self-rostering follow the period. See [Roster periods and publishing](https://chrona365.com/docs/workforce/roster-periods).

## Planning

| Setting | What it does | Empty or default |
| --- | --- | --- |
| **Planning horizon** | **On** shows the current roster and the next ones as cards above the board, each with the day it is due to be published. Needs a roster period. | **Off**. |
| **Plan ahead** | How many rosters after the current one show as cards, from 0 to 52. Shown while **Planning horizon** is on. | 6. |
| **Publish ahead** | A roster is due by 17:00 this many days before it starts, from 0 to 90. After that, its card shows how many days it is overdue. Shown while **Planning horizon** is on. | 3 days. |

### Self-rostering

| Setting | What it does | Empty or default |
| --- | --- | --- |
| **Picks open** | How many days before a roster starts the scheduler's workers can start picking its shifts in Chrona Workforce Mobile, from 0 to 365. | Empty: self-rostering is off. |
| **Picks close** | How many days before a roster starts picking ends. It must be fewer than **Picks open**. After it, workers cannot pick shifts for that roster or change their picks. | Empty: self-rostering is off. |
| **Guaranteed share** | The percent of their picks a worker can star, from 0 to 100. Starred picks are kept when the roster is made; with 0, no pick is sure to be kept. | 30%. |

Self-rostering needs a roster period. Without one, the section shows **Roster period: Off**, which opens **Roster period**. See [Self-rostering](https://chrona365.com/docs/workforce/self-rostering).

## Shift types and coverage

**Shift types** opens the page of each shift type's times, breaks, roles and skills. **Coverage** opens the page of how many workers each shift type needs. The summary counts both. See [Shift types, coverage and Generate](https://chrona365.com/docs/workforce/templates).

## Groups

**Groups** opens the scheduler's list of groups and subgroups, such as a ward or a building. The board lists them in that order, and the summary counts both. See [Groups](https://chrona365.com/docs/workforce/roles-and-skills#groups).

## Roles and skills

- **Owned by this scheduler** lists the roles and skills the scheduler owns. **New role** and **New skill** add one; its name is used once among the scheduler's roles and skills. Select a name to open its form.
- Under each role, set its **Standard hourly rate** and **Currency**, its **Required skills** and, in **Advanced**, its **Pairing**. The rate is required: it is the hourly rate of a worker in this role whose contract sets none, and it only estimates the roster's cost.
- **Shared with** picks the other schedulers that can use a role or skill. Sharing a role also shares its required skills. A share that another scheduler still uses stays, and the save says where it is used.
- **Shared with this scheduler** lists the roles and skills other schedulers share with this one, each with its owner. Only the owner changes them.

Only people with **Change settings** change what the scheduler owns and shares. See [Roles, skills and groups](https://chrona365.com/docs/workforce/roles-and-skills).

## Demand drivers

A demand driver counts what makes the work, such as residents or orders, by day or by service. **New demand driver** adds one.

| Setting | What it does | Empty or default |
| --- | --- | --- |
| **Name** | The driver's name. | Required. |
| **Unit name** | What one unit of the count is. Staffing standards give the hours each role needs per unit. | Empty. |
| **Window kind** | The time each value covers: **Day**, **Service**, **Week** or **Custom**. | **Day**. |

Under a saved driver, a line shows its latest value. **Edit values** opens the driver's form, where its values are kept. **Delete** removes the driver when you save. See [Demand drivers](https://chrona365.com/docs/workforce/demand#demand-drivers).

## Staffing standards

| Setting | What it does | Empty or default |
| --- | --- | --- |
| **Staffing counted per** | The demand driver the staffing standards count. Choose it and save; then add standards and values. | **None**: the staffing check is off. |
| **Check staffing every** | How often Chrona checks the standards and adds open shifts where hours are short, from 1 to 24 hours. Shown once **Staffing counted per** has a driver. The hint says when it last checked. | Every hour. |
| **Fill new shifts automatically** | **On**: Auto Schedule fills the open shifts each check adds. **Off**: they wait for you to fill them. Shown with **Check staffing every**. | **On**. |

**Add standard** sets the hours a role needs per unit, for a group or **All groups**, with **Rounding** (**Round up** unless you choose **Nearest**, **Round down** or **Up from .51**) and optional limits to a shift type, a site or another driver. **Add value** enters a count for a date when your system has not sent one. See [Staffing standards](https://chrona365.com/docs/workforce/demand#staffing-standards).

## Rules

The four rules check the changes you make by hand on the board. Each one is **Off** (no check), **Warn** (the move stays, with a warning) or **Don't allow** (the board asks for a reason first: see [Assign anyway](https://chrona365.com/docs/workforce/call-out#assign-anyway)).

| Rule | What it checks | Empty or default |
| --- | --- | --- |
| **Overlap rule** | You give a worker a shift that overlaps another of theirs. | **Warn**. |
| **Skill rule** | You move a shift to a worker without its role or its skills. See [Moving a shift by hand](https://chrona365.com/docs/workforce/roles-and-skills#moving-a-shift-by-hand). | **Don't allow**. |
| **Working hours rule** | You place a shift outside **Working start** and **Working end**. The shading guides you, and night work is normal. | **Off**. |
| **Availability policy** | You move a shift into a worker's unavailable time. See [Moving a shift by hand](https://chrona365.com/docs/workforce/availability#moving-a-shift-by-hand). | **Don't allow**. |

### Auto Schedule

| Setting | What it does | Empty or default |
| --- | --- | --- |
| **Run for** | The longest an Auto Schedule run takes, from 5 to 900 seconds. A run also stops when it stops finding a better roster. See [Runs and billing](https://chrona365.com/docs/workforce/auto-schedule#runs-and-billing). | 30 seconds. |

## Fair share

**Fair share** shows the site's **Share work fairly**, the work Auto Schedule shares evenly between workers, and its **Roster periods counted**. It applies to every scheduler at the site, so you change it on the site: select **Open** with the site's name. Without a site, it asks you to choose one in **General**. See [Share work fairly](https://chrona365.com/docs/workforce/self-rostering#share-work-fairly).

## Goals

Goals choose between rosters that keep every Must rule. **Never break a Must rule** and **Fill every required shift** always come first. Rank the five goals below them by dragging or with the arrows, or pick a preset: **Balanced**, **Lowest cost**, **Happiest team** or **Best coverage**. A new scheduler uses **Balanced**; any other order is **Custom**. See [Goals](https://chrona365.com/docs/workforce/goals).

## Call-out

When a published shift loses its worker and is open, Chrona offers it to the best candidates among the scheduler's workers, level by level, until someone accepts. See [Candidates and call-out](https://chrona365.com/docs/workforce/call-out).

| Setting | What it does | Empty or default |
| --- | --- | --- |
| **Call-out** | **On**: Chrona offers each published open shift that lost its worker. **Off**: no offers go out, and open shifts wait for you to fill them. | **On**. |
| **Start offering** | An open shift that lost its worker is offered from this many days before it starts, from 1 to 60. | 3 days. |
| **Stop offering** | Offers stop this many minutes before the shift starts, from 0 to 1,440 in steps of 15; then the planners get an alert. 0 offers it until the start. It must be closer to the shift than **Start offering**. | 60 minutes. |
| **Send texts** | **On**: each offer also goes as a text to workers who haven't opted out. Texts need your Twilio account: see [Set up call-out](https://chrona365.com/docs/workforce-callout). | **Off**. |

## Access

- **Use scheduler**: in **People who can use this scheduler**, pick the users who plan and publish shifts and decide requests. With no one on it, only Chrona administrators can open the scheduler, and the section warns you.
- **Change settings**: in **People who can change settings**, pick the users who also change these settings. They can also use this scheduler.

Both lists offer users with the **Chrona Workforce User** role, also through a team. Taking yourself off a list takes effect when you save, and the section warns you first unless you are a Chrona administrator. Chrona administrators always have access and are on neither list.

---
Product: Workforce Scheduler
Language: English
Canonical: https://chrona365.com/docs/workforce/scheduler-settings
