Staff can connect their Outlook calendar to Plinth so appointments work with the calendar they already use. It works in both directions:
Meetings in Outlook block out that person's appointment availability in Plinth, so nobody can book them when they're busy.
Appointments booked in Plinth are added to their Outlook calendar, with a Teams meeting for online appointments.
Outlook meetings aren't copied into Plinth as appointments. Plinth only uses them to know when someone is busy.
Step 1: Your IT team approves Plinth (once)
Microsoft 365 only lets staff connect apps that use calendars once an admin has approved them. Someone with admin rights in your Microsoft 365 organisation needs to:
Open app.plinth.org.uk/outlook-admin-consent. They don't need a Plinth account.
Sign in with Microsoft and accept the permissions Plinth asks for.
Approving Plinth doesn't share anyone's calendar. It only lets your staff choose to connect their own.
Step 2: Each staff member connects their own calendar
Plinth can only use the calendars of people who connect them individually. Each person who hosts appointments needs to:
Go to Appointments in Plinth.
Click the Appointment settings cog in the top right.
Under Your Outlook calendar, click Connect Outlook and sign in with your work Microsoft account.
If you see "Your IT team needs to approve Plinth in Microsoft", step 1 hasn't been done yet.
What Plinth can see and do
Reads: only the start time, end time and busy status of events in your calendar. Plinth doesn't read titles, descriptions or attendees.
Writes: only events for Plinth appointments. Plinth updates or cancels them when the appointment changes, and doesn't change any other events.
Permissions: Microsoft asks you to approve Read and write user calendars, because that is the narrowest permission that lets Plinth create events with Teams meetings. It allows more than Plinth uses.
Storage: Plinth never sees your Microsoft password. You sign in on Microsoft's own page, and Microsoft gives Plinth an access token. Plinth keeps that token in encrypted storage (Google Cloud Secret Manager), separate from its main database.
Who it applies to: Plinth only uses a calendar while its owner is staff in your Plinth organisation.
Removing access
Staff can click Disconnect in Appointment settings at any time. Plinth then deletes its copy of their sign-in details. To remove access for everyone at once, your IT team can remove Plinth from Enterprise applications in Microsoft Entra.