--- sourceDocument: Australia Conversational Interfaces sourceDocumentLink: https://www.servicenow.com/docs/r/australia/conversational-interfaces Release : - australia ft:locale : - en-US ft:publication_title : - Australia Conversational Interfaces ft:clusterId : - convint bundleId : - convint workflow : - Platform --- # Sidebar and Slack # Sidebar and Slack {#ariaid-title1} Release version: Australia Updated March 12, 2026 ![](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 The Sidebar and Slack integration enables seamless communication between Sidebar users and Slack users directly from their respective platforms. This integration requires at least one participant to be an external-only user (a user without a corresponding sysuser record in ServiceNow). It allows messages, attachments, emojis, and links to be exchanged, enhancing collaboration across ServiceNow and Slack environments. Show full answer Show less ## Key Features * **User Authentication:** Sidebar users must have a Slack account to communicate with Slack users. Slack authenticates each Sidebar user to ensure the creation of private channel chats including the Sidebar user's Slack account. * **User Differentiation:** Slack users are identified by a Slack icon next to their names in discussion windows and search results, helping users distinguish between Sidebar and Slack participants. * **Adding and Removing Users:** Sidebar users can add users by searching their names, and Slack users can add participants by adding them to Slack group chats. Removal of Slack users from discussions is reflected in both platforms, with notifications about user removals or departures. * **Message Types Supported:** The integration supports plain text, images, emojis, URLs, attachments, and ServiceNow record links. Replies in Slack appear as replies in Sidebar discussions. * **User and Participant Synchronization:** A synchronization job runs every 30 minutes to map Slack and Sidebar users based on matching emails. However, participant synchronization can be inconsistent if the integration is repeatedly changed. * **Message Validation and Security:** Messages sent from Slack to Sidebar are verified using Slack's signing secret to ensure authenticity. * **Message History:** When Slack group chat access is enabled for a user, only new messages sent after enabling are received; past Sidebar discussion history is not preloaded into Slack. * **ServiceNow Access to Slack Data:** ServiceNow accesses only those Slack group chats and messages generated through the Sidebar and Slack integration, maintaining strict data scope. * **Domain Separation Limitation:** Domain separation is not supported in Slack when integrated with Sidebar. The Slack setup option is disabled if domain separation is configured in ServiceNow. ## Key Outcomes * Enables efficient cross-platform communication between ServiceNow Sidebar users and Slack users without requiring duplicate user accounts. * Maintains clear identification of user origin to avoid confusion during discussions. * Supports rich message content and threaded replies, enhancing collaboration quality. * Provides controlled user management within discussions, with synchronized participant lists and clear notification of user changes. * Ensures secure and validated message exchange between platforms. * Limits message history exposure in Slack for compliance and privacy, only showing messages after group chat access is granted. * Supports enterprise organizational needs with clear constraints on domain separation and user synchronization behavior. 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 to be 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 logged in, they're prompted to log 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 need 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} Replies made to messages in Slack are displayed as replies to the corresponding message(s) in Sidebar. ## 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 receives only 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. 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.