Overview
Office 365 Calendar is designed to work hand in hand with the Communications module within Salpo. Once the calendar integration is enabled, scheduled Communications will automatically sync with the user's Office 365 Calendar account.
As long as a user is signed into a Microsoft Account, the user will receive web notifications for any scheduled Communication saved in Salpo, even if the user is not signed in to Salpo.
Activation
To activate the Office 365 Calendar integration for system users, navigate to the Control panel > click on Integrations in the Admin section > select the More Details hyperlinked text within the Office 365 Calendar badge. Click on the activation button to enable the feature.
Setting up
Each user will need to set up his/her own individual calendar sync. To set up the Office 365 Calendar sync, click on the Username drop-down and then click on Integrations.
Click on 'Connect' and the page will navigate to sign into a valid Microsoft account. Input the user's associated Microsoft email address to confirm and the set up is complete!
Using Calendar 365
Office 365 Calendar is integrated with Salpo's Communications module and only applies to scheduled Communications.
When creating a scheduled Communication, the option to sync the activity into Office 365 is available at the left bottom of the Communication modal. The checkbox option defaults as select. To keep the activity out of Office 365, de-select this checkbox. When syncing a Communication into Office 365, any Contacts included in the calendar invite will receive a calendar invitation.
Once the scheduled Communication is saved in Office 365, any edits made to the Communication within Salpo will automatically reflect in the Office 365 event. This sync works both ways, so any changes made to the event in Office 365 will update the Communication within Salpo.
As the sync is only available for scheduled Communications, the 'Save to Office 365 Calendar' option will be greyed out when creating Salpo standard Communications.
Comments
0 comments
Article is closed for comments.