Full Groupware Integration using Microsoft Modern Authentication

Owned by Malissa Olofernes
Last updated: Apr 04, 2024

To download above documents:

  • Click on desired document to open it. Then, click on the cloud symbol in the top right corner of your screen to download, save, or print.

  • Click on the video above to see full demonstration.

Overview

Groupware gives you the ability to integrate Deem with Outlook and Google Calendar, below are how each are supported.

Outlook - Supported through Groupware Calendar Integration

Google Calendar - Supported through ICal

Why Integrate with Groupware Calendar Integration?

You can integrate Deem services such as booking travel with your groupware calendars and contacts. For example, as a user books travel, the service can automatically update enterprise or personal calendars with reservation details and changes. And if a travel delegate (arranger) books a trip for someone else, the trip information automatically appears on that person’s calendar.

This convenience provides the following benefits:

  • Eliminates the need for the user to manually enter and maintain reservation information

  • Ensures that the details are always immediately accessible

  • Users with calendars on their smartphones don't have to print out the information

  • Updates happen automatically

  • Saves time for a travel delegate or arranger who books a trip for someone else by eliminating the copying and pasting into the traveler's calendar

To enable Outlook through Groupware Calendar Integration please see attached documents

  • Groupware Calendar Integration with Deem

    • Exchange Servers (non-cloud based)

  • Check List_Groupware Integration - Modern Authentication

  • Client_ Instructions Guide_Deem_Groupware_Modern_Auth

    • Outlook365 or Exchange Servers using Modern Authentication

Does Deem ‘read’ a user’s calendar?

NO - While the permission needed in Outlook 365 is Calendar.ReadWrite, we will only 'write' to the user's calendar. When an event is created an EventID is assigned. If an event is to be modified or removed we simply send a cancel using the EventID we already have from the write. If the event is there, it is removed. If the event has been removed already the cancel merely does nothing. At no time do we need to know what is actually in the calendar itself other than what we have already written.

What this diagram above attempts to show is when we write to Office 365 and in no place is there a read.