This article covers the process for integrating Chronus with your organization's enterprise Microsoft Teams account.
Table of Contents
- Integration Steps
- Enabling Teams Video Call Feature
- Access Levels for Administrators
- Removing Chronus Integration
1. An active Chronus & Microsoft Teams Enterprise account
2. A dedicated Microsoft account in the organization with administrative privileges
3. A user in Chronus must be a member of the organization's Enterprise account to be able to set up a Teams meeting within Chronus
In this step, you’ll set up the “link” between Chronus and Teams so they can communicate with each other.
1. The integration of Teams with Chronus has to be done from the dedicated account created for Chronus. This dedicated account will act as a host for all the meetings that are created from Chronus (refer to item 2 in the section above for additional context).
2. A global administrator in Chronus with Administrator Privileges in Teams logs in to Chronus and goes to Manage page at Global level. From there, click the Integrations icon.
3. On this page, integrations available to your organization will be listed. Click Teams to proceed.
Clicking on Integrate will cause the pop-up shown below to be displayed:
Click Accept—you have finished Integrating your enterprise Microsoft account with the Chronus Platform!
Enabling Teams Video Call Feature
Once the Integration is complete, you will need to add ‘Teams Video call’ as a meeting mode under the Permissions tab of the Program Settings tool in each track that the feature will be available for:
On enabling ‘Teams video call’ as a meeting mode option, participants will see the following interface when creating new meetings:
Access Levels for Administrators
Administrators will have control over the integration and removal of integration, as well as enabling Teams feature, to specific tracks within their instance, meaning administrators can pick and choose which programs will have access to create Teams meetings through Chronus.
Removing Chronus Integration
A global administrator can log in to Chronus and remove Teams from the Integrations tool on the global Manage page.
What kind of data will Chronus be able to access from customers’ Teams account?
Chronus will only have permission to view and manage all user meetings and view basic user information which is First Name, Last Name, Email, and Photo.
Would program participants need to authorize their Teams account?
No, the participants do not need to do any authorization on their end. Note, however, that users who are not part of the organization's enterprise account will not have the ability to create Teams meetings.
Can I extend Teams capabilities to only one/a selected list of programs in my organization?
Yes, track-level administrators and global administrators can enable or disable the ability to create Teams meetings in their specific program, under the Permissions tab in the Program Settings tool of each individual track.
Can the Administrator who authenticated Teams be removed from Chronus once the integration has been completed?
Yes, once completed, the administrator can be removed/deactivated.
How do I remove Teams integration to Chronus?
Global administrators will have the option to remove the integration from Chronus under the Integrations tool, found on the global Manage page.
Should a program participant be logged in to their Teams account if they want to create a meeting?
The user does not need to be logged in to Teams when they are creating the meeting, so long as their individual account is listed under the organization's Teams account.
Who will be the host of the meetings created?
By default, the host of the meeting will always be the dedicated account created for Chronus in the customer’s enterprise Microsoft account. Refer to item 2 under the Prerequisites section for more context.
Will the meetings be recorded and will Chronus have access to them?
No, Teams Integration API (Graph API) doesn’t support partner (Chronus) access to recordings. This is not something that Chronus has any control over.