Approving leave requests in Microsoft Teams

The request and the decision in a Teams chat

When an employee submits a request, the approver gets a card in a private chat with the Tivero app. The card has Approve, Reject and Details buttons. The same permissions apply as in the app: someone who cannot approve a request in Tivero cannot approve it in Teams either.

• if the request has already been decided elsewhere, the card says so and does not allow a second decision;
• the employee is told about the decision in Teams;
• private types, such as sick leave, are shown as “Absence”;
• email notifications keep working, including for people who are not on Teams;
• in the My and Team tabs an employee sees their balance, their absences and team availability, and can submit a new request.

Absences in Outlook calendars

An approved absence appears in the employee’s Outlook calendar as an all-day “Out of office” event, usually within a few minutes. The event is private and has a neutral title — it does not show the absence type or any comment. When an approved request is cancelled, the event is removed.

The sync is one-way, from Tivero to Outlook. Changes made in Outlook do not come back to Tivero, and part-day absences are not synced.

People and managers from Entra ID

Instead of typing people in by hand, you can import them from your Microsoft Entra ID directory — together with their managers, who feed the approval path. Before anything is saved, Tivero shows a preview: new people, updates, conflicts and candidates for deactivation. Tivero only reads the directory and never changes anything in it.

You run updates by hand with “Sync now”. Scheduled directory sync and automatic deactivation of people removed from the directory are not available at the moment — a person always decides about deactivation.

What your administrator needs

The Microsoft 365 integration is part of the Growth plan and the 30-day trial. Setting it up involves a few roles on your side:

• an Administrator or Owner in Tivero connects the integration and turns on each feature;
• a Microsoft 365 administrator grants admin consent for each feature you turn on — the directory, the Outlook calendar and Teams. What the consent screen shows depends on your organisation’s policies and the app publisher’s current status;
• a Teams administrator uploads the Tivero app package to the organisation’s app catalogue, makes it available under your Teams app policies, and uploads it again for each new package version;
• people who should get notifications need to be imported from the directory and have an active Microsoft 365 account with a Teams licence.

The order to set it up in

Connect Microsoft 365 and import people first, because the calendar and Teams work for people from the directory. Then turn on the Outlook calendar, and finally publish the app in Teams and turn on notifications. Once the app is in your organisation’s catalogue and your Teams app policies allow it for a person, Tivero installs it for that person at their first notification — in most cases it does not have to be installed by hand for each employee. Tivero does not bypass your organisation’s policies: if consent or installation fails, follow the Help Center instructions or ask your Microsoft 365 administrator.