---
title: "Flex Office: integrations"
description: "The Integrations page in Flex Office settings has no settings yet. Room meetings already reach connected calendars, and the module's data goes out and comes in through exports, reports and imports."
url: "https://illizeo.com/en/centre-aide/flex-office-integrations-and-exports/"
updated: "2026-11-05"
category: FlexOffice
---

# Flex Office: integrations

The **Integrations** page in Flex Office settings shows the status of the module's links with your other tools: the public API and its keys, webhooks, Slack, Microsoft Teams and calendars. Your bookings can go to your work calendar, and the module's data also goes out and comes in through exports, reports and imports.

## Before you start

The page requires access to the Flex Office module and at least one of the permissions of the screens it summarises. Each block only appears with the permission for its own screen; without any of these permissions, the **Integrations** tile is not shown.

### Permissions in the role matrix

- “Flex Office module — Access”: entry to the module.
- “API tokens — View”: the **Flex Office API** block. Creating a key also requires “API tokens — Create / edit / revoke” at the Execute level.
- “Webhooks — View”: the **Webhooks** block.
- “Application store connectors (OAuth connect / disconnect)”, at the Execute level: the **Slack** and **Microsoft Teams** blocks.
- “Calendar integrations — company settings (what is pushed, OAuth app)”: the **Calendars** block; at the Execute level, its switches.
- “Connect and disconnect one's own calendar (Google / Outlook)”: the **Link my calendars** link.

The API and Webhooks blocks also follow your subscription: they only appear if it includes API access and webhooks.

## What this page is for

It brings together, read-only, the status of each integration that touches Flex Office. Each block links to the screen that manages the integration, where the settings are made; only the calendar switch can also be set here.

![Screenshot — The Integrations page in Flex Office settings](https://i0.wp.com/illizeo.com/wp-content/uploads/2026/11/flex-office-integrations-and-exports-01-v2.en_.png?resize=800%2C500&quality=80&ssl=1)
The Integrations page in Flex Office settings.

- **Flex Office API**: the public API's **Base URL**, to copy, and the **Keys carrying Flex Office**. For each key: its name, the masked start of the key, its status (**Active**, **Expired**, **Disabled** or **No longer responds**), “Acts on behalf of” followed by the name of the person who created it, its Flex Office scopes, its last use, its expiry and the **Open the key** link. The **Manage API tokens** link opens the tokens screen, **API documentation** its documentation.
- **Webhooks**: the subscriptions listening to Flex Office events (bookings, visits, meetings, check-ins), with the host of their receiving address, their status and their last delivery. They are managed with **Manage webhooks**.
- **Slack**: if the company's Slack workspace is connected, its name and the number of matched employees. Flex Office notices go out as a direct message to those who ticked Slack in their preferences, or for whom the company set it by default.
- **Microsoft Teams**: whether Teams is connected, whether notifications and approvals are on, and how many employees have a linked Microsoft account. With notifications on, Flex Office notices arrive as bot messages; with approvals on, desk and visit requests are approved there.
- **Calendars**: for Google and for Outlook, the switch that lets Flex Office go to that provider and the number of people linked, paused, to reconnect or without an “illizeo” calendar; then the status of the subscription link, **Apple and other calendars: subscription**.

Slack and Teams are connected in the app store connectors: the **Open connectors** link takes you there. Nothing secret is shown: no full token, no signing secret, no full receiving address.

## Step by step

### Create an API key for Flex Office

1. In the **Flex Office API** block, click **Create a Flex Office key**.
2. The API tokens screen opens on token creation, pre-filled: the name “Flex Office integration” and the Flex Office read scope ticked.
3. Add write scopes if needed, then finish creating it as for any token. See [Creating and managing API tokens](https://illizeo.com/en/centre-aide/api-managing-tokens/).

The key acts on your behalf: with your permissions and your population, never more. Create it with an account that has the intended Flex Office permissions and population; if that account is deactivated, the key no longer responds. Tokens are also managed in **Settings › Manage Illizeo › API Tokens**.

### Let Flex Office go to calendars

1. In the **Calendars** block, turn on the switch for Google, for Outlook, or both.
2. The message “Sync saved” confirms the setting.

The same setting is called **Sync Flex Office** in the company calendar connector, in the app store. It is off by default: as long as it is off, no Flex Office booking, meetings included, goes to that provider.

## Your bookings in your calendar

Each person receives their own Flex Office bookings in their work calendar, and only their own, on three conditions:

- the company has turned on Flex Office sync for that provider (Google or Outlook);
- the person has connected their Google or Microsoft calendar to Illizeo (personal settings, **My calendars** tab). If the company has opened the “Outlook calendars” application, Flex Office goes straight to everyone's Outlook calendar, with nothing to connect;
- the person has ticked that type of booking in the **Calendar** block of the Flex Office calendar preferences (everything is ticked until they choose).

The six types:

- **My office days**: full day or half day, with the location and, if booked, the floor, zone and desk;
- **My remote work days**: full day, “Remote work”;
- **My meetings in a room**: at the time of the meeting (see below);
- **My parking spaces**;
- **My meals**: at the time of the service;
- **The visits I host**: for the host, with the number of visitors and the reception location.

A booking awaiting approval, or a meal on the waiting list, is sent as provisional, marked “[Pending]”; it is updated at the decision and removed if refused. The event follows changes to the booking and disappears when it is cancelled. It is written in each person's language and never carries the dish, the licence plate, the comment, the reason or a visitor's name.

### Meetings in your calendar

A room meeting is sent to the calendar of the organiser and of each participant who has not declined it, on the same conditions:

- the event is created at booking and at invitation;
- it is updated when the room, the day, the times or the video-conference link change;
- it is removed when the meeting is cancelled or the room is released, when the participant declines the invitation or is removed from the meeting;
- it carries the room, the location, the day, the times and the video-conference link, in each person's language; never the subject of the meeting;
- each person receives their own event, without a calendar invitation: you reply to an invitation in Illizeo, not from your calendar.

A person who has not connected their calendar sees the meeting in Illizeo and receives it by email. A meeting in a series gives one event per occurrence.

### Apple and other calendars

When the company has turned on sync for at least one provider, everyone can also subscribe by link: in the **Calendar** block of the preferences, **Subscribe** opens “Subscribe to the calendar” with the “My Flex Office bookings” category ticked. It is a fallback, not a sync: the calendar re-reads the link at its own pace, so a booking can take several hours to appear. It requires the “Export the calendar” permission.

## Data that goes out and comes in

- **Public API**: another system (badge reader, kiosk, booking tool) reads and writes Flex Office with a key. See [Creating and managing API tokens](https://illizeo.com/en/centre-aide/api-managing-tokens/).
- **CSV exports** from the [dashboard](https://illizeo.com/en/centre-aide/flex-office-dashboard/): occupancy (anonymous) and per-person attendance (named).
- **System reports** in People Analytics: “Occupancy by site”, “On-site presence per employee” and “Meals and parking per day”. Each one can be deposited regularly on an SFTP server with **Schedule an SFTP deposit**. The deposit is calculated with the permissions of the person who scheduled it.
- **CSV imports** of zones, desks, meeting rooms, parking spots, profile members and rules, restaurants, services and menus. See [Imports](https://illizeo.com/en/centre-aide/flex-office-data-imports/).

## Good to know

- In the calendar, the **Preferences** window holds each person's **Calendar** block: the status of their calendars and the types they send there. See [Flex Office calendar](https://illizeo.com/en/centre-aide/flex-office-calendar/).
- Switching the module off, or removing it from a person, stops the sync; it resumes when the module is reactivated.
- A meeting event deleted by hand in the calendar is recreated at the next change to the meeting.

## See also

- [Flex Office settings](https://illizeo.com/en/centre-aide/flex-office-settings/)
- [Meeting rooms](https://illizeo.com/en/centre-aide/flex-office-meeting-rooms/)
- [Notifications](https://illizeo.com/en/centre-aide/flex-office-notifications-and-emails/)
- [Imports](https://illizeo.com/en/centre-aide/flex-office-data-imports/)
- [Dashboard](https://illizeo.com/en/centre-aide/flex-office-dashboard/)
- [Creating and managing API tokens](https://illizeo.com/en/centre-aide/api-managing-tokens/)
- [Flex Office: module overview](https://illizeo.com/en/centre-aide/flex-office-overview/)

### *Similaire*