### Author:  [@Discourse](https://meta.discourse.org/u/Discourse)
#### Post date: [July 20, 2017, 3:52pm UTC](https://meta.discourse.org/t/discourse-chat-integrations/66522/1 "2017-07-20T15:52:39Z")
> ℹ **Chat Integration** is for using an _external_ chat system together with Discourse — you may be looking for **[Discourse Chat](https://meta.discourse.org/t/discourse-chat/230881)** which adds Chat functionality directly to Discourse.
| | |
| --- | --- |
| :discourse2: | **Summary** |
| 📖 | **Install Guide** |
> [@](#):
>
> :discourse2: As this is an #official plugin maintained by the Discourse team, #Support, #Contribute > Bug, #Contribute > UX, and #Contribute > Feature requests can be made in the respective categories here on Meta, and tagged with the appropriate plugin tag. Click on a link below to get one started. 👍
>
> [❓ **Support**](https://meta.discourse.org/new-topic?category_id=6&body=%3E%20Before%20asking,%20did%20you%20search%20first%3F%20Press%20%F0%9F%94%8D%20at%20the%20upper%20right%20to%20search.&tags=chat-integration "Ask for support on configuring and using Discourse Chat Integration") [🐛 **Bug**](https://meta.discourse.org/new-topic?category_id=1&tags=chat-integration "A bug report means something is broken, preventing normal/typical use of the plugin") [👀 **UX**](https://meta.discourse.org/new-topic?category_id=9&tags=chat-integration "Discussion about the user interface of Discourse Chat Integration, and how features are presented (including language and UI elements)") [💡 **Feature**](https://meta.discourse.org/new-topic?category_id=2&tags=chat-integration "Discussion about how existing Discourse Chat Integration features can be improved or enhanced, and how proposed new features could work")
The Discourse Chat Integration plugin lets you send messages in your preferred chat platform when something happens in Discourse.
Messages can be triggered by:
- New topics
- New replies
- Messages to a group
- Mentions of a group
## Functionality by provider
| Provider | Notifications | Slash Commands | Post Transcripts | Threaded Replies |
| --- | --- | --- | --- | --- |
| Slack | ✅ | ✅ | ✅ | ✅ |
| Telegram | ✅ | ✅ | | |
| Discord | ✅ | | | |
| Mattermost | ✅ | ✅ | | |
| Google Chat | ✅ | | | |
| Matrix ([element.io](http://element.io)) | ✅ | | | |
| Zulip | ✅ | | | |
| Rocket.Chat | ✅ | | | |
| Gitter | ✅ | | | |
| Stride | [Docs](https://confluence.atlassian.com/get-started-with-stride/get-started-with-stride-937168092.html) | | | |
| Microsoft Teams | ✅ | | | |
| Basecamp | [Docs](https://github.com/basecamp/bc3-api) | | | |
| IRC Cloud | [Docs](https://github.com/irccloud/irccloud-tools/wiki/API-Overview) | | | |
| Flock | [Docs](https://dev.flock.com/) | | | |
| Webex | ✅ | | | |
> ⚠ Before you enabling Slash Commands for your provider, make sure to read the **Security/Permissions** section below!
## Configuration
There are three key concepts in this plugin:
- **Providers:** The chat platform that you’re connecting to (e.g., Slack, Discord, etc.).
- **Channels:** A single chat area in your platform (e.g., channel, group chat, room, etc.). Each provider can have multiple channels.
- **Rules:** The instructions for when and how Discourse should send a message to a channel. Each channel can contain multiple rules.
### Configuring providers
1. Go to **Admin \> Installed Plugins** and ensure that the **Chat Integrations** plugin is enabled.
2. Click Settings.
3. Choose the chat platform that you’d like to connect to Discourse.
1. For some providers (e.g., Discord), you’ll be directed straight to the next step (channel configuration). Others will ask for special information, which you’ll need to get from your chat platform.
> **Dedicated setup instructions for chat platforms**
>
> - **Slack** : [Set up Slack notifications using the discourse-chat-integration plugin](https://meta.discourse.org/t/set-up-slack-notifications-using-the-discourse-chat-integration-plugin/66730)
> - **Discord** : [https://meta.discourse.org/t/discord-chat-integration-discord-notifications/171136](https://meta.discourse.org/t/discord-chat-integration-discord-notifications/171136)
> - **Microsoft Teams** : [Set up Microsoft Teams notifications using the discourse-chat-integration plugin](https://meta.discourse.org/t/set-up-microsoft-teams-notifications-using-the-discourse-chat-integration-plugin/159193)
> - **Telegram** : [Set up Telegram integration using the discourse-chat-integration plugin](https://meta.discourse.org/t/set-up-telegram-integration-using-the-discourse-chat-integration-plugin/66603)
> - **Google Chat** : [Set up Google Chat notifications using the discourse-chat-integration plugin](https://meta.discourse.org/t/set-up-google-chat-notifications-using-the-discourse-chat-integration-plugin/177362)
> - **Matrix** : [Set up Matrix (element.io) notifications using the discourse-chat-integration plugin](https://meta.discourse.org/t/set-up-matrix-element-io-notifications-using-the-discourse-chat-integration-plugin/66944)
> - **Zulip** : [Set up Zulip notifications using the chat integration plugin](https://meta.discourse.org/t/set-up-zulip-notifications-using-the-discourse-chat-integration-plugin/68501)
> - **Mattermost** : [Set up Mattermost notifications using the discourse-chat-integration plugin](https://meta.discourse.org/t/set-up-mattermost-notifications-using-the-discourse-chat-integration-plugin/66811)
> - **Gitter** : [Set up Gitter notifications using the discourse-chat-integration plugin](https://meta.discourse.org/t/set-up-gitter-notifications-using-the-discourse-chat-integration-plugin/69220)
> - **Rocket.Chat** : [Set up Rocket Chat notifications using the discourse-chat-integration plugin](https://meta.discourse.org/t/set-up-rocket-chat-notifications-using-the-discourse-chat-integration-plugin/68633)
> - **GroupMe** : [Configure Groupme provider with the discourse-chat-integration plugin](https://meta.discourse.org/t/configure-groupme-provider-with-the-discourse-chat-integration-plugin/158129)
> - **Webex Teams** : [Set up Webex notifications using the discourse-chat-integration plugin](https://meta.discourse.org/t/set-up-webex-notifications-using-the-discourse-chat-integration-plugin/173026)
>
> ###
### Configuring channels
Once you have configured a provider, you can now configure channels for that provider. From the Chat Integration plugin page, click Add channel and provide the requested information — typically a webhook URL and/or channel name, depending on the provider.
### Configuring rules
After your channel is connected, you can click Create rule to create a new rule for when your community should send a message to your provider channel.
The main components of a rule are:
- **Type:** What type of community content should trigger a chat message?
- `Normal`: Send chats for topics in the selected category.
- `Group message`: Send chats when a PM is sent to the selected group.
- `Group mention`: Send chats when the selected group is mentioned.
- **Filter:** You can optionally filter the rule so that it only sends chats in certain situations.
- `All posts with threaded replies`: Send chats for all posts matching this rule, with replies threaded in the chat platform. _This option is not available for all integrations._
- `All posts and replies`: Send chats for all posts and replies that match this rule.
- `First post only`: Only send chats for the first post in a topic or message that matches this rule.
- `Tag added to topic`: When the `create post for category and tag changes` site setting is enabled, send a chat when someone adds adds a tag to a topic.
- `Mute`: Do not send chats that match this rule. This is useful for carving out an exception to another broader rule.
- **Group:** If you selected `Group message` or `Group mention` as the **Type** , select the group whose received PMs / mentions should trigger the chat.
- **Category:** If you selected `Normal` as the **Type** , optionally select the category that a topic must be posted in to trigger the chat.
- **Tags:** Optionally select one or more tags that matching topics must have _at least one of_ to trigger the chat message.
#### What happens when there are multiple rules?
Rules are sorted first by **type** then by the **filter:**
1. Group mentions
1. Mute
2. All posts and replies
3. First post only
2. Group messages
1. Mute
2. All posts and replies
3. First post only
3. Normal (i.e. topics)
1. Mute
2. All posts and replies
3. First post only
If a post matches multiple rules, the plugin will trigger the first matching rule in the list.
For example, with the following rules
| Filter | Category | Tags |
| --- | --- | --- |
| All posts and replies | Mentions of: `@team` | (all tags) |
| Mute | #Support | (all tags) |
| First post only | #Support | #unsupported-install |
| All posts and replies | (all categories) | (all tags) |
Notifications would be triggered for:
- A post in #Customization > Plugin ✅
- A post in #Support mentioning `@team` ✅
…but not for:
- A post in #Support ❌
- A post in #Support with tag #unsupported-install ❌
## Security / Permissions
By default the `system` account is used, which means that there is no restriction on notifications sent.
To secure your notifications, you should create a non-staff user with appropriate access privileges, and enter its username in the `chat integration discourse username` setting.
> [@](#):
>
> ⚠ If you have Slash Commands enabled for your provider, and do not trust every member of the external Channel, it is **absolutely essential** that you set this up to avoid them having access to private categories on your forum.
## Slash Commands
If your provider supports slash commands, you can manage rules from within your chat interface. Each provider varies slightly in syntax, but in general they follow a similar structure. (Note that at this time, only the Slack integration implements threads.)
The commands available are
> [@](#):
>
> **New rule:** `/discourse [thread|watch|follow|mute] [category] [tag:name]`
> (you must specify a rule type and at least one category or tag)
>
> - **thread** – notify this channel for new topics, thread replies if possible
> - **watch** – notify this channel for new topics and new replies
> - **follow** – notify this channel for new topics
> - **mute** – block notifications to this channel
>
> **Remove rule:** `/discourse remove [rule number]`
> (`[rule number]` can be found by running `/discourse status`)
>
> **List rules:** `/discourse status`
>
> **Help:** `/discourse help`
## Posting a transcript
If your provider supports transcript posting, you can post your instant messaging history to discourse. This is currently only supported for the Slack provider. Note: You will need to be using the “Access Token” method of connecting to Slack.
Send `/discourse post` to see the interface. The plugin will try and “guess” where your current conversation starts, by looking for a gap in the message history of more than 3 minutes.
Alternatively, you can specify a number of posts after the command, or a URL to the first message.
[https://global.discourse-cdn.com/meta/original/3X/4/8/48ed362a57d59f70fd4c3632d1d0fcecc1d7d949.mp4](https://global.discourse-cdn.com/meta/original/3X/4/8/48ed362a57d59f70fd4c3632d1d0fcecc1d7d949.mp4)
To load a transcript for a Slack thread, you can use `/discourse post thread {url}`, where `{url}` is the permalink of the first message in the thread. For example:
```plaintext
/discourse post thread https://.slack.com/archives/C6029G78F/p1522952993000017
```
Alternatively, you can use `/discourse post` with a thread-specific permalink like this:
```plaintext
/discourse post https://foo.slack.com/archives/G49KKS6AX/p1523062012000911?thread_ts=1523091738.000088&cid=G49KKS6AC
```
In both cases the “first/last message” UI is skipped - the entire thread is included in the transcript.
## Adding new providers
**Option 1: Submit a PR implementing your provider:**
> [@Add a new provider to discourse-chat-integration](https://meta.discourse.org/t/adding-a-new-provider-to-discourse-chat-integration/68156):
>
> [discourse-chat-integration](https://meta.discourse.org/t/chatroom-integration-plugin-discourse-chat-integration/66522) abstracts away the boilerplate for integrating Discourse with external chatroom systems. There are three features which a provider implementation can support: Notifications, Slash Commands and Transcripts. There are two ways you can add a provider: in your own plugin, or by submitting a pull request to discourse-chat-integration. This post will detail the latter, but most of the information will work in either scenario. This post gives a general overview of how thing…
**Option 2: Use your own plugin:**
It is possible for third party plugins to register new “providers”. As an example, I’ve created a [provider which sends webhooks to IFTTT](https://github.com/davidtaylorhq/discourse-chat-ifttt). This could be used to automatically publish all posts in a category to facebook… or turn on your light when someone posts in #Contribute > Feature… or feed your fish whenever there’s a new #Customization > Plugin.
### CHANGELOG
### TODO
> Last edited by @lindsey 2026-04-21T21:14:15Z
>
> > **Check document**
> >
> > Perform check on document:
---
### Author:  [@sunjam](https://meta.discourse.org/u/sunjam)
#### Post date: [October 20, 2023, 11:56pm UTC](https://meta.discourse.org/t/discourse-chat-integrations/66522/296 "2023-10-20T23:56:57Z")
It would be interesting to add support for Discourse’s own [ActivityPub Plugin](https://meta.discourse.org/t/activitypub-plugin/266794) so that publishing could be triggered based on tags and other filters from chat integration.
---
### Author:  [@Aizada\_M](https://meta.discourse.org/u/Aizada_M)
#### Post date: [December 18, 2023, 3:28pm UTC](https://meta.discourse.org/t/discourse-chat-integrations/66522/297 "2023-12-18T15:28:23Z")
Hello, last year Telegram announced forums/topics (mini chats within group chats). I tried to connect each individual mini chat to one or another category of my site. But as I understand, topic addresses are not supported by the plugin? For example, in my case, each topic has an address as follows: @telegram\_topic **/1** , @telegram\_topic **/2** , @telegram\_topic **/3** …
If I insert a standard chat name into the line, for example @telegram\_chat, it works without problems.
It would be very convenient if the plugin had the ability to insert similar chat addresses (../1), then users would not have to be subscribers to many independent channels tied to certain categories of the site.
---
### Author:  [@sunjam](https://meta.discourse.org/u/sunjam)
#### Post date: [December 19, 2023, 3:32am UTC](https://meta.discourse.org/t/discourse-chat-integrations/66522/298 "2023-12-19T03:32:43Z")
> [@Aizada\_M](#):
>
> then users would not have to be subscribers to many independent channels tied to certain categories of the site.
Have you considered using tags to accomplish this?
---
### Author:  [@Aizada\_M](https://meta.discourse.org/u/Aizada_M)
#### Post date: [December 19, 2023, 5:00am UTC](https://meta.discourse.org/t/discourse-chat-integrations/66522/299 "2023-12-19T05:00:07Z")
🤔 I think using tags is not entirely suitable for my case. Because even with the help of tags, I wouldn’t want all notifications to go into one channel, creating information noise. At the same time, instead of having 20 channels for 20 categories/tags, I would prefer to have one group chat where I could organize several mini-themed chats (by category/tag) where each user can view the one they need minichat and the ability to look into other minichat. I’m so bothered because in my region (Asia) most people use WhatsApp and Telegram chats - forums are not popular. But I’m trying to find a compromise).
Ps. If I repeat myself often, don’t judge me, I’m just trying to convey my thoughts correctly, as I use Google translator.
---
### Author:  [@sunjam](https://meta.discourse.org/u/sunjam)
#### Post date: [December 19, 2023, 7:22am UTC](https://meta.discourse.org/t/discourse-chat-integrations/66522/300 "2023-12-19T07:22:02Z")
> [@Aizada\_M](#):
>
> I wouldn’t want all notifications to go into one channel, creating information noise.
You should be able to filter which tags would apply to which chats, at least as far as I am understanding you.
---
### Author:  [@Aizada\_M](https://meta.discourse.org/u/Aizada_M)
#### Post date: [December 19, 2023, 8:24am UTC](https://meta.discourse.org/t/discourse-chat-integrations/66522/301 "2023-12-19T08:24:07Z")
> [@sunjam](#):
>
> You should be able to filter which tags would apply to which chats, at least as far as I am understanding you.
It seems to me that we are talking about different things 🤔 I don’t have a question about filtering chats by tags/categories.
For context. Previously, Telegram had channels and chats (except for bots). These channels/chat rooms have a username, approximately @chat\_username or `@channel_username`.
Since last year, Telegram has had the opportunity to turn [chats into forums](https://innovation-village.com/how-to-organise-your-large-telegram-group-using-the-topics-feature/#:~:text=Telegram%20has%20feature%20called%20'Topics,to%20chat%20in%20any%20topic.) containing mini thematic chats like this. These mini chats have their own usernames, for example @chat\_username **/1** , @chat\_username **/2**. The convenience of such chats with minichat is that the user no longer needs to subscribe to several chats separate from each other, but just subscribe to one chat (for example, with the name of my site) and have access to many mini chats (in my case, each mini chat would target a specific category on the site) that are of interest to the user.
Now I want to connect these mini chats to this plugin, but it seems to me that the plugin does not support the mini chat username as `chat_username` **/1**.
---
### Author:  [@atwong](https://meta.discourse.org/u/atwong)
#### Post date: [January 4, 2024, 11:26pm UTC](https://meta.discourse.org/t/discourse-chat-integrations/66522/302 "2024-01-04T23:26:06Z")
Is there a way to create a rule where I can tag a new message and/or reply so it won’t post to target chat system (in this case Slack)?
---
### Author:  [@david](https://meta.discourse.org/u/david)
#### Post date: [January 11, 2024, 10:39am UTC](https://meta.discourse.org/t/discourse-chat-integrations/66522/304 "2024-01-11T10:39:40Z")
Hey Albert, if we’re talking about normal Discourse tags, you can set up a [‘mute’ filter](https://meta.discourse.org/t/discourse-chat-integration/66522#configuring-rules-4) to prevent topics with that tag triggering notifications in Slack.
But in terms of individual posts, there is no way to filter them out.
---
### Author:  [@ErlendMS](https://meta.discourse.org/u/ErlendMS)
#### Post date: [January 18, 2024, 10:25am UTC](https://meta.discourse.org/t/discourse-chat-integrations/66522/305 "2024-01-18T10:25:27Z")
I think I have the same _want_ as you, Aizada:
I’d love to be able to have a Telegram group chat, with _topics_ enabled (that somewhat correspond to the categories on Discourse), and then, in the Discourse/Chat integration settings, specify which topic it should post to.
I’ve tried to create a group chat with topics now (with just the bot and me), but when I type `/help` within a topic, the bot answers in the _general chat_.
**Have you looked into this @david?** I found [this Stack Overflow thread](https://stackoverflow.com/questions/74773675/how-to-get-topic-id-for-telegram-group-chat), that shows how to get the `message_thread_id` (which is the topic id) and says that the bot API got support for this in 6.3.
Thanks for your work anyway! 🫶🏻
---
### Author:  [@david](https://meta.discourse.org/u/david)
#### Post date: [January 18, 2024, 10:33am UTC](https://meta.discourse.org/t/discourse-chat-integrations/66522/306 "2024-01-18T10:33:40Z")
Hi @ErlendMS 👋. We don’t have any enhancements for this plugin on our roadmap at the moment, but if someone would like to add ‘threading’ (aka topic) support for the telegram integration that would likely be #pr-welcome.
We do have some threading support in the slack integration, so it should be possible to reuse some of that logic.
---
### Author:  [@PeakProsperity](https://meta.discourse.org/u/PeakProsperity)
#### Post date: [June 11, 2024, 12:29am UTC](https://meta.discourse.org/t/discourse-chat-integrations/66522/307 "2024-06-11T00:29:14Z")
Is it possible to use this plugin to get notifications in Slack whenever a post is flagged for review? Thanks.
---
### Author:  [@BrainFried](https://meta.discourse.org/u/BrainFried)
#### Post date: [June 22, 2024, 6:31am UTC](https://meta.discourse.org/t/discourse-chat-integrations/66522/308 "2024-06-22T06:31:52Z")
Does this plugin expose additional API functions?
---
### Author:  [@crossheadscrewdriver](https://meta.discourse.org/u/crossheadscrewdriver)
#### Post date: [July 30, 2024, 2:05pm UTC](https://meta.discourse.org/t/discourse-chat-integrations/66522/309 "2024-07-30T14:05:37Z")
Where do I request a PR review? I’ve submitted this PR late last week to add a new provider and it is still pending a reviewer. I’ve looked around different developer guides on meta and couldn’t find one for proper PR requests.
Here’s my PR: [FEATURE: Added Power Automate as a new provider by benoitdesnoyers · Pull Request #204 · discourse/discourse-chat-integration · GitHub](https://github.com/discourse/discourse-chat-integration/pull/204)
Thanks,
---
### Author:  [@gabriel](https://meta.discourse.org/u/gabriel)
#### Post date: [August 13, 2024, 6:46pm UTC](https://meta.discourse.org/t/discourse-chat-integrations/66522/310 "2024-08-13T18:46:58Z")
Hello guys! we’ve just merged this [pr](https://github.com/discourse/discourse-chat-integration/pull/208) for chat integration plugin
This change aims to remove the `tags_changed` option from the rule filtering from chat integration–we are doing this change because we are [removing](https://github.com/discourse/discourse/pull/28321) the `Creation of a small action post when a topic's category or tags change` setting.
But the functionality will remain the _same_, if you have [discourse automation installed](https://meta.discourse.org/t/discourse-automation/195773). The next time you run the migrations for this plugin, it will add a script to the [discourse automation plugin](https://meta.discourse.org/t/discourse-automation/195773) that will run similarly to what we currently have.
This is an example of automation that will be created:
It will be sent to my channel based on the categories and watching tags that I have.
`${ADDED_AND_REMOVED}` is the default text; it will behave the same as the rule would.
We have also added for this script option a few options that can be used in the message:
> - `${TOPIC}` for the topic name
> - `${REMOVED_TAGS}` for the removed tags
> - `${ADDED_TAGS}` for the added tags
> both removed and added will only trigger if they _have_ a tag in them.
> For example: `added: ${ADDED_TAGS}` message will only trigger if there are added tags
---
### Author:  [@gabriel](https://meta.discourse.org/u/gabriel)
#### Post date: [September 11, 2024, 3:28pm UTC](https://meta.discourse.org/t/discourse-chat-integrations/66522/311 "2024-09-11T15:28:18Z")
We had an issue with the other PR(users who used other providers could not use the automation when topic tags changed), so to address it, we have made this new [PR](https://github.com/discourse/discourse-chat-integration/pull/216), where we account for _every_ provider.
The `Creation of a small action post when a topic's category or tags change` setting will not appear in chat integration.
If you have `discourse automation` installed the next time you run the migrations for this plugin, it will add a script to the discourse automation plugin that will run similarly to what we currently have.
* * *
Your automations will look something like this:
And your providers are the `enabled` providers.
For example, I have `Discord`,`Slack`, `Telegram` and `Google Chat` enabled
Your `channel name` is the name you gave it in the chat integration settings.
For example, the name here is `Spidey`
---
### Author:  [@gabriel](https://meta.discourse.org/u/gabriel)
#### Post date: [October 9, 2024, 3:19pm UTC](https://meta.discourse.org/t/discourse-chat-integrations/66522/312 "2024-10-09T15:19:21Z")
We have a new batch of changes for the Automation/chat-integration
In this new batch, notable changes are:
- We added `Trigger with PMs`, which lets you control whether this automation should be triggered even on private messages.
- Solved an issue where `Topic tags changed` trigger automation was being triggered during topic creation.
---
### Author:  [@gabriel](https://meta.discourse.org/u/gabriel)
#### Post date: [November 6, 2024, 12:31pm UTC](https://meta.discourse.org/t/discourse-chat-integrations/66522/313 "2024-11-06T12:31:21Z")
As mentioned before – [here](https://meta.discourse.org/t/discourse-chat-integration/66522/311)
The `create post for category and tag changes` site setting currently can leak private tags/categories; one way that we found to keep that feature was by moving it to whispers:
It works similarly to small posts, but now, you need to have `whisper allowed groups` with _some_ group to make it work.
I’ve merged a [PR](https://github.com/discourse/discourse/pull/29602) for core with this change and one for [chat-integration](https://github.com/discourse/discourse-chat-integration/pull/229), removing the usage of that setting; the automation feature added back should be 1:1 with the small action if anyone has any issue, please let us know!
---
### Author:  [@gabriel](https://meta.discourse.org/u/gabriel)
#### Post date: [January 6, 2025, 2:54pm UTC](https://meta.discourse.org/t/discourse-chat-integrations/66522/314 "2025-01-06T14:54:04Z")
I have some more updates to this plugin 🚂
We have added `trigger on` field for `Send Chat-Integration message` automation.
## What does it do?
It checks for when tags are:
- `Added and Removed` (default)
- `Added`
- `Removed`
Currently, this check is inclusive.
A good example is if I set it to `Added`; For this automation to run, it is going to be necessary for _any_ tag to be added to a topic.
When `Tags added` is set, the automation table looks like this:
| Added tag to topic | Removed Tag to topic | Has automation ran? |
| --- | --- | --- |
| ✅ | ❌ | ✅ |
| ✅ | ✅ | ✅ |
| ❌ | ✅ | ❌ |
When `Tags removed` is set, the automation table looks like this:
| Removed tag to topic | Added Tag to topic | Has automation ran? |
| --- | --- | --- |
| ✅ | ❌ | ✅ |
| ✅ | ✅ | ✅ |
| ❌ | ✅ | ❌ |
---
### Author:  [@wodeche](https://meta.discourse.org/u/wodeche)
#### Post date: [February 19, 2025, 1:10pm UTC](https://meta.discourse.org/t/discourse-chat-integrations/66522/315 "2025-02-19T13:10:37Z")
Subject: Unable to access Plugins section for Chat Integration setup
Hello,
I’m an administrator of the LXDAO forum and I’m trying to set up the Discourse Chat Integration plugin to connect with Telegram. According to the official documentation, I should be able to configure this in the Plugins section of the admin panel.
However, in my admin dashboard, I only have access to four sections: General, Moderation, Security, and Reports. The Plugins section mentioned in the documentation does not appear to be available.
Could you please help me understand:
1. Is the Chat Integration plugin already installed on our forum?
2. Do I need additional permissions to access the Plugins section?
3. If we’re using a hosted Discourse solution, are there any limitations regarding plugin installation/configuration?
As an administrator, what steps should I take to properly set up the Telegram integration for our community?
Thank you for your assistance!
[Next page](https://meta.discourse.org/t/discourse-chat-integrations/66522.md?page=2)