# Workers

> **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).

Manage each [worker](https://chrona365.com/glossary/worker) in one tabbed page. Open **Workers** and select a worker, or select their name on the board. Each setting's **(i)** explains it.

## Overview

**Where they work** lists the schedulers whose board lists the worker, one block for each scheduler, with its site.

1. Select **Add to scheduler**, tick one or more schedulers and select **Add**. The worker then works at each scheduler's site.
2. In a scheduler's block, pick their **Home group** and add their **Other groups**. Auto Schedule keeps workers in the groups they may work and prefers their home group. Each scheduler has its own groups: see [Groups](https://chrona365.com/docs/workforce/roles-and-skills#groups).
3. **Remove** takes the worker off that scheduler, with their groups there. Their shifts stay.

A worker works only at the sites of the schedulers they are on. Removing them from a scheduler takes its site away, unless another of their schedulers is at the same site. A shift they still hold at a site none of their schedulers has shows under **Wrong site** in Auto Schedule's review until you add them to a scheduler there.

Under **Details**, set:

| Field | Purpose |
| --- | --- |
| **Name** | Worker name. |
| **Payroll ID** | Their payroll worker number. An ID too long for a fixed-width Format warns here and blocks that export until it fits. |
| **Manager** | Approves their Mobile requests. A planner of the receiving scheduler can also approve on **Requests**. |
| **Power Apps user** | Link workers who also use Chrona in Power Apps, such as a team leader who plans shifts. |

Choose manager and user from the matching list; unmatched text blocks **Save**. Select **Save** or **Discard** for these changes.

Under **Advanced**, **Prohibited risk factors** keeps the worker off any shift that carries one of them. Record the label only; keep the reason outside Chrona.

## Roles and skills, contract and hours

**Roles and skills** shows the worker's roles and skills as tags: pick one to add it, and its **x** removes it. See [Roles, skills and groups](https://chrona365.com/docs/workforce/roles-and-skills).

**Contract and hours** shows the worker's **Agreement**, their contracts and their hours balance. See [Contracts](https://chrona365.com/docs/scheduler/configure#contracts) and [Hours balance](https://chrona365.com/docs/workforce/hours-balance).

## Availability

The **Availability pattern** is when the worker can work: their own pattern, else their employment type's default, else any time. Pick another pattern in the list, or select **Open Availability patterns** to paint one.

Under **Time off and availability**, select **Add** for one-off **Unavailable** or **Available** time, with its **Type**, such as *Annual leave*, and its **Start** and **End** on the clock of their scheduler's site. **Edit** and **Remove** change a row. See [Availability and leave](https://chrona365.com/docs/workforce/availability).

## Preferences

**Time preferences** are one-off **Preferred** and **Unpreferred** times: when the worker would like to work, or would rather not. Auto Schedule tries to honour them and never treats them as a must. Under each, a note says who set it last: the worker in Chrona Workforce Mobile, or a planner in Power Apps.

- Select **Add**, choose **Preferred** or **Unpreferred**, and set **Start** and **End**.
- A **Preferred** time can't overlap the worker's **Unavailable** time: the page refuses it as you type. An **Unpreferred** time there is fine.
- Whether the worker changes their own preferences in Chrona Workforce Mobile follows **Changes from the phone** on the employment type of their contract.

Preferred times in the worker's weekly pattern repeat every week and show on the **Availability** tab, not here.

**Shift types** lists standing **Preferred** / **Unpreferred** choices by site, including **Night shifts** and **Weekend shifts**. Each shift type shows its times. Choices last until changed; Auto Schedule treats them as preferences, never Must rules.

- Under **Add as**, choose **Preferred** or **Unpreferred**, then a shift type by site, or **Night shifts** / **Weekend shifts** under **Nights and weekends**. The list excludes existing choices and ineligible types: the worker must be on the scheduler and site, hold a listed role (if any) and Must skills, and have no Prohibited worker or risk-factor conflict.
- A preference that becomes ineligible stays with the reason, such as **Not eligible: missing skill BLS** or **Not eligible: prohibited risk factor Heavy lifting**; deactivated types say **shift type inactive**. **Remove** deletes it. Mobile hides it.
- Two schedulers on one site can each have a shift type with the same name and times. The worker sees one row for them, and a change saves to each.
- Change a row's **Preferred** or **Unpreferred** in place, or select **Remove**: no row means no preference.
- In Mobile, use **More** > **Work preferences**: thumb up for **Preferred**, thumb down for **Unpreferred**, then tap again to clear. Each row names who last changed it. For multiple sites, tap a closed site to expand it; its header counts set preferences.
- A preference stands as soon as someone sets it, the worker or a planner. It needs no approval. Availability changes still wait for a planner.

## Notification preferences

Workers choose channels for offers and clock-out reminders in Mobile under **More** > **Notification preferences**. Each setting has an **(i)** explanation.

- **In the app.** Always on. Every notification shows there.
- **Email** and **Text message.** On until the worker turns them off. Each switch saves at once. A channel your organization does not send is grayed, with the reason.
- Email goes when a scheduler the worker is on runs call-outs, or when App settings send clock-out reminders by email.
- Texts need your Twilio account. They also need either a scheduler the worker is on that has [Send texts](https://chrona365.com/docs/workforce/scheduler-settings#call-out) on, or **Text message** on for clock-out reminders with reminders on.
- With **Text message** on, a reminder to text START to your sending number explains how to reverse a previous STOP. Tapping the number opens a text with START filled in. Twilio keeps STOP in your account; Chrona reads no reply. Messaging Service or sender-name senders show no reminder.
- On the worker's page, **Mobile app status** shows **Email** and **Text message**, each **On** or **Off**: what the worker chose. They are read-only: only the worker changes them, in the app.

## Mobile app status

**Mobile app status** says where the worker stands with Chrona Workforce Mobile: not invited, invitation sent, active (when they joined and last used the app), or access stopped, with its dates and reason. Select **Invite to app** or **Open in App access** to change it in **App access**.

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