--- sourceDocument: Yokohama Conversational Interfaces sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/yokohama/conversational-interfaces Release : - yokohama ft:locale : - en-US ft:publication_title : - Yokohama Conversational Interfaces ft:clusterId : - convint bundleId : - convint workflow : - Platform --- # Sidebar and Slack # Sidebar and Slack {#ariaid-title1} Release version: Yokohama Updated January 30, 2025 ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 3 minutes to read Summarize ![AI sparkle icon](https://servicenow.com/docs/portal-asset/ai-sparkle-icon) Summarized using AI This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete. ## Summary of Sidebar and Slack Integration The Sidebar and Slack integration allows users on both platforms to communicate seamlessly. This integration requires that at least one participant is an external-only user without a corresponding ServiceNow sysuser record. It enables collaborative discussions by synchronizing users and messages between Sidebar and Slack. Show full answer Show less ## Key Features * **User Authentication:** Sidebar users must have a Slack account, and Slack authenticates these users to enable private channel chats including Sidebar users. * **User Differentiation:** Slack users are indicated by a Slack icon next to their names in discussion windows and search results, helping users distinguish between Sidebar and Slack participants. * **Adding Participants:** Sidebar users can add others by searching and selecting existing users. Slack users can add participants directly in Slack group chats, which automatically updates the Sidebar discussion. A limit of 250 users applies per Slack private channel. * **User Synchronization:** A synchronization job runs every 30 minutes to align Sidebar and Slack users based on matching email addresses. * **Message Validation and Types:** Messages sent from Slack to Sidebar are validated using Slack's signing secret. Supported message types include plain text, images, emojis, URLs, attachments, and links to ServiceNow records. * **Removing Users:** Sidebar users can remove Slack participants from discussions. Removed users can still view past messages in Slack but cannot participate. Notifications are shown when users leave or are removed. * **Message History:** When Slack group chats are enabled for a user, prior Sidebar discussion messages are not preloaded in Slack; only new messages after enabling are received. * **Access Control:** ServiceNow only accesses Slack messages generated through this integration, ensuring limited and secure message access. ## Important Considerations * **Participant Synchronization:** Repeated changes to the Sidebar-Slack integration can disrupt synchronization of discussion participants. * **Domain Separation:** Domain separation is not supported on the Slack instance integrated with Sidebar. As a result, the Slack setup button is disabled in ServiceNow settings when multiple domains exist, limiting Slack instance partitioning across domains. Sidebar's integration with Slack enables Sidebar users and Slack users to communicate with each other from their respective platforms. The base system Sidebar-Slack integration requires at least one participant is an external only user (a user that doesn't have a corresponding sys_user record). ## Authenticating Sidebar users in Slack {#sidebar-slack-overview__section_tdk_w3x_mvb} A Sidebar user must already have a Slack account to communicate with a Slack user. Slack authenticates each Sidebar user to confirm that they have a Slack account. This authentication verifies that Slack can create a private channel chat that includes the Sidebar user's Slack account. If the Sidebar user has a Slack account but isn't signed in, they're prompted to sign in. ## Differentiating between Sidebar and Slack users {#sidebar-slack-overview__section_ejb_hnf_dyb} To differentiate Sidebar users from Slack users, a Slack icon (![Slack icon.]()) displays next to the Slack users' names. This icon is visible in discussion windows and search results, but does not appear in the activity stream. {#sidebar-slack-overview__table_udj_t2t_dyb__entry__2} | | | |-|-| | Discussion window with Slack icon | | | All tab on the Discussion window with Slack icon | | | Discussion window with Slack icon next to search results | | | Discussion info window with Slack icon | | [Table 1. Examples with Slack icon] {#sidebar-slack-overview__table_udj_t2t_dyb} ## Adding users to a discussion {#sidebar-slack-overview__section_w5z_ykx_mvb} Sidebar users can enter the partial or full name of a user that they want to add to the discussion. If the user exists in the system, the user's name appears and can be selected to be added to the discussion. Users who have access to Slack but not ServiceNow can be identified by the Slack logo in their avatar image. Slack users can add participants to the discussion by adding them to the group chat on Slack. Doing this automatically adds those users to the discussion in Sidebar. Note: A maximum of 250 users can be added to a Slack private channel. ## Synchronizing Sidebar and Slack users {#sidebar-slack-overview__section_mx2_fjn_rdc} If Sidebar and Slack are integrated, a job runs every 30 minutes to synchronize the Sidebar and Slack users. If a Slack user's email matches a Sidebar user's email, the Slack user is mapped to the Sidebar user. ## Validating messages {#sidebar-slack-overview__section_a33_fkn_rdc} Messages that are sent from Slack to Sidebar are verified using Slack's signing secret. ## Sending messages between Sidebar and Slack {#sidebar-slack-overview__section_spw_p3x_mvb} After Sidebar and Slack are integrated, you can send these types of messages between the two applications: * Messages with plain text * Messages with images * Messages with emojis * Messages with URLs * Messages with attachments * Messages with links to ServiceNow records {#sidebar-slack-overview__ul_ml4_4jx_mvb} ## Removing users from a discussion {#sidebar-slack-overview__section_o1q_rcm_nvb} Sidebar users can remove a Slack user from a Sidebar discussion. When a Slack user is removed from a discussion, Sidebar and Slack users see a message that the user has been removed from the discussion. After a Slack user is removed from the discussion, they can still access the group chat on Slack and view past messages, but they can no longer participate in the discussion. If a Slack user leaves a discussion on their own, both Sidebar and Slack users see a message that the Slack user has left the discussion. ## Message history {#sidebar-slack-overview__section_lws_zg5_gwb} If the admin enables Slack group chats for a user, the message history of any Sidebar discussions that the user is already participating in aren't preloaded in the Slack group chat. In the Slack group chat, the user will only receive messages that are sent after the admin enables them to receive Slack group chats. ## ServiceNow's access to Slack messages {#sidebar-slack-overview__section_urh_m4t_pwb} ServiceNow's access to Slack group chats and messages is restricted to the ones generated as part of the Sidebar and Slack integration. ## Synchronizing of participants {#sidebar-slack-overview__section_rpj_fsh_hwb} The discussion participants aren't synchronized if the integration between Sidebar and Slack is changed multiple times. Figure 1. Synchronizing example ## Domain separation with Sidebar and Slack integration {#sidebar-slack-overview__section_k4j_fg5_gwb} If Sidebar is integrated with Slack, domain separation is not supported on the Slack instance. As a result, the Set up button for Slack is inactive on the Settings page. For example, if you've configured two domains on ServiceNow but use only one Microsoft Teams instance, you can't partition the Microsoft Teams instance to have part of it point to one domain and the other part to another domain.