From 09d0b29d8fc6bdfcd8b2df9daa1514c3913c9160 Mon Sep 17 00:00:00 2001
From: Sergio Moya <1083296+smoya@users.noreply.github.com>
Date: Thu, 4 Jul 2024 12:13:42 +0200
Subject: [PATCH] docs: clarify jurisdiction of the CoC Committee regarding
 Slack external connections (#1286)

---
 code_of_conduct/coc-incident-resolution-procedures.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/code_of_conduct/coc-incident-resolution-procedures.md b/code_of_conduct/coc-incident-resolution-procedures.md
index 58341cf52..8a5b351a7 100644
--- a/code_of_conduct/coc-incident-resolution-procedures.md
+++ b/code_of_conduct/coc-incident-resolution-procedures.md
@@ -76,7 +76,7 @@ Once the report has been submitted, the AsyncAPI CoC Committee will confirm rece
 
 The Jurisdiction of the CoC Committee is as follows:
 - [AsyncAPI Initiative GitHub](https://github.com/asyncapi)
-- [AsyncAPI Slack](asyncapi.slack.com)
+- [AsyncAPI Slack](asyncapi.slack.com), including all external channels connected through [Slack Connect](https://slack.com/connect).
 - AsyncAPI social networks: [Twitter](https://twitter.com/AsyncAPISpec), [LinkedIn](https://www.linkedin.com/company/asyncapi), [YouTube](https://www.youtube.com/asyncapi), [Twitch](https://www.twitch.tv/asyncapi), and [Mastodon](https://fosstodon.org/@AsyncAPISpec)
 - AsyncAPI events: conferences, talks, workshops, etc.