# Scheduling and calendars

RivetMSP schedules work as **appointments on tickets**, shows them on a shared dispatch calendar, and can push them into each technician's own calendar.

## Appointments on a ticket

From a ticket you can schedule a visit. An appointment has:

- a start and an **end time**, with a duration picker from 30 minutes to 8 hours,
- a **Remote** or **Onsite** toggle,
- notes for the visit,
- a live preview of how it will look.

A ticket can have several appointments. The mobile app can create and view them too.

## The dispatch calendar

The **Calendar** in the agent portal shows scheduled tickets for the team. Each technician picks a **colour**, shown on the calendar, so you can see who is doing what at a glance.

## Putting appointments in Outlook

There are two ways to see your appointments in the calendar you already use. Use either or both.

### Option A: Outlook calendar push sync

Each technician connects their Microsoft account once. After that, scheduled tickets are **created, updated and cancelled** as events in their personal Outlook calendar through Microsoft Graph. Changes made in Outlook flow back to RivetMSP on the next cron cycle.

An administrator sets this up once, under **Administration > Settings > Calendar sync**, by registering RivetMSP as an app in Microsoft Azure. You need a Microsoft 365 or Azure account with admin rights.

1. In the Azure portal, open **App registrations** and choose **New registration**.
2. Name it, for example *RivetMSP Calendar Sync*.
3. Set **Supported account types** to *Accounts in this organizational directory only* (single tenant).
4. Set the **Redirect URI** to type *Web* and paste the URL shown in the Redirect URI field on the Calendar sync settings page.
5. Click **Register**, then copy the **Application (client) ID** and **Directory (tenant) ID** into the settings page.
6. Under **API permissions**, choose *Add a permission*, then *Microsoft Graph*, then *Delegated permissions*, and add **Calendars.ReadWrite** and **offline_access**.
7. Under **Certificates & secrets**, create a client secret and copy its **value** straight away. Azure only shows it once, and it is the value you need, not the secret ID.
8. Save the three credentials in RivetMSP.

Once saved, technicians can connect their calendars from their own profile.

Two housekeeping notes: the settings page has a **Sync All Appointments to Outlook** button that pushes every existing appointment for everyone who has connected, which is useful after reconnecting a revoked token or migrating from another system. And the pull direction runs from the cron job, so cron must be enabled (see [Cron Manager](/docs/msp/cron-manager)).

### Option B: a calendar subscription feed

Every technician has a private **iCal subscription URL** (a `webcal://` link). Subscribe to it in Outlook Classic, Apple Calendar or Google Calendar and your scheduled tickets and appointments appear there, covering upcoming items and the past 30 days. It is read-only and needs no Azure setup.

The link carries a secret token, so treat it like a password. Anyone with the link can read that technician's schedule.

## Recurring work

Tickets that repeat on a schedule are handled by **recurring tickets**, which cron generates. See [Cron Manager](/docs/msp/cron-manager).
