MS Teams Integration Requirements

Overview

The WorkBoard App for Microsoft Teams allows seamless access to WorkBoard in the following ways:

• Adding WorkBoard Tabs to Team Channels​
• Individual chats with your colleagues​​
• Chatting Directly with the WorkBoard app​
  

Learn more about customizing WorkBoard in Microsoft Teams. 

Authentication and Interactions

WorkBoard uses Microsoft Teams guidelines in its tabs, messaging extension, and bot integration. 

The following sequence diagram talks about the unified integration sequence flow that a user needs to perform before the users start using the integrations. We recommend enabling the integration from the ​My Integration​ page. 

Click​ here​ to go to your integration page.

The authentication is OAuth2 and is triggered when you enable the integration in WorkBoard or interact with the integration in Microsoft Teams.

Interaction with the Microsoft Graph

WorkBoard's bot uses the​ ​Microsoft Bot framework​ ​that creates the Azure AD application registration with the default delegated permission' scopes (https://graph.microsoft.com/User.Read, openid, profile, email, offline_access). All the interaction to the Microsoft Graph happens through the​ ​Microsoft bot client​. 

Permissions Breakdown

 

WorkBoard’s Microsoft Teams integration includes features such as a Teams bot, in-channel notifications, static tabs, messaging extensions, and automated onboarding. The following Microsoft Graph and Teams permissions are required to deliver these capabilities securely and effectively.

Admin Consent
All users can authorize the WorkBoard Teams integration on their own.
 However, if your organization has Admin Consent Required enabled in Azure Active Directory, a Microsoft 365 administrator must approve the application once for your tenant.

Required Permissions:

Basic User Permissions
These scopes allow the app to authenticate users and access basic profile details:

• https://graph.microsoft.com/User.Read
• https://graph.microsoft.com/User.ReadBasics.All
• https://graph.microsoft.com/User.Read.All

Teams & Messaging Permissions
These enable the integration to interact with Teams channels, chats, and messages:

• https://graph.micosoft.com/Channel.ReadBasic.All
• https://graph.micosoft.com/Team.ReadBasic.All
• https://graph.micosoft.com/ChannelMessage.Send
• https://graph.micosoft.com/Chat.Create
• https://graph.micosoft.com/ChatMessage.Send

App Management Permissions
These scopes ensure smooth deployment and operation of the WorkBoard app within your Teams environment:

• https://graph.micosoft.com/AppCatalog.Read.All
• https://graph.micosoft.com/TeamsAppInstallation.ReadforUser
• https://graph.micosoft.com/TeamsAppInstallation.ReadWriteForUser

Authentication & Identity Scopes                                                                                                            Used for secure sign-in and background access to user data:

• openid
• profile
• email
• offline_access

Teams App Manifest Permissions
The WorkBoard Teams app manifest includes the following additional permissions:

• identity: Enables access to the user's Microsoft identity.

• messageTeamMembers: Allows the app to send messages to all team members

What These Permissions Enable
With these permissions, the WorkBoard integration can:

• Authenticate users securely

• Read basic user and directory profile

• informationAccess Teams channel names and messages

• Post automated updates or summaries in channels

• Send notifications in chats or create new chat threadsDeploy and manage the WorkBoard app across the organization

• Deliver personalized and team-based interactions via bot messages, tabs, and notifications.

•  

Scope Support
The integration supports both personal and team scopes, enabling it to function effectively in individual user chats, group chats, and shared team channels within Microsoft Teams.