Requirements for the Chat Service
The Heedify Chat Service is built natively on Microsoft Teams and the Microsoft Bot Framework, providing a seamless integration for enterprise communication. This model allows organizations to extend Teams capabilities with intelligent chat experiences powered by the Bot Framework, while maintaining the security and compliance of the Microsoft 365 ecosystem.
To ensure a successful deployment and smooth operation of the Heedify Chat Service, it is important to review and complete all required prerequisites. The following sections outline the environment considerations and setup requirements.
Administror role
To set up Heedify CX, an Azure Global Administrator is required. This role is needed to grant permissions to the Heedify Apps, assign licenses, and configure core settings. The Global Administrator handles tasks such as creating Azure Bot and adding the Chat application on the Organization Apps.
Resource-Specific Consent
Team permissions
| Permissions | Permission type | Description |
|---|---|---|
| ChannelMessage.Read.Group | Application | Read this team’s channel messages. |
| Member.Read.Group | Application | Read the members of this team’s channels. |
Chat Meeting permissions
| Permissions | Permission type | Description |
|---|---|---|
| ChatMessage.Read.Chat | Application | Read this chat’s messages. |
Microsoft Graph Permissions
Heedify Chat Service requires a set of permissions. Microsoft 365 tenant Admin should consent for each Heedify Cloud CX module.
Heedify Presence Application
| Permissions | Permission type | Description |
|---|---|---|
| Presence.Read.All | Application | Read presence information for all users |
Heedify Admin portal
| Permissions | Permission type | Description |
|---|---|---|
| User.Read | Delegated | Sign in and read user profile |
| User.Read.All | Delegated | Read all users’ full profiles |
Heedify Agent Console
| Permissions | Permission type | Description |
|---|---|---|
| Presence.Read | Delegated | Read presence information of all users in your organization |
| Presence.Read.All | Delegated | Read and write your presence information |
| Contacts.ReadWrite | Delegated | Allows the app to create, read, update, and delete user contacts. |
| Contacts.ReadWrite.Shared | Delegated | Allows the app to create, read, update, and delete contacts a user has permissions to, including their own and shared contacts. |
| OrgContact.Read.All | Delegated | Read organizational contacts |
| Calendars.Read | Delegated | Allows the app to read events in your calendars. |
| offline_access | Delegated | Maintain access to data you have given it access to |
| openid | Delegated | Sign in as you |
| profile | Delegated | View your basic profile |
| Teams.ManageChats | Delegated | Create, read, update, and delete 1:1 or group chat threads on behalf of the signed-in user. Read, send, update, and delete messages in chat threads on behalf of the signed-in user |
Heedify Reporting
| Permissions | Permission type | Description |
|---|---|---|
| User.Read | Delegated | Sign in and read user profile |
Refer to #calls-permissions for more informations about permission types (Delegated and Application)
Proxy settings
Verify that your Web Proxy settings allow outbound connections to :
- wss://*.signalr.net : websocket endpoinst on Microsoft SignalR instance used for real-time status updates on Heedify End-User apps.
- https://*.heedify.io : Heedify Cloud domain used for hosting all Heedify Core services.
Networking
For optimal call quality and performance, the Heedify Agent Console requires certain network configurations. Please refer to the network-requirements page for detailed guidance.