> For the complete documentation index, see [llms.txt](https://docs.jetadmin.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.jetadmin.io/faq-and-troubleshooting/how-to-connect-to-slack-channel.md). # How to Connect to Slack Channel Learn how to join our Slack workspace and access your dedicated channel. Our Slack channels are available for Pro and Enterprise plan users, including: * Internal Tool Pro * Internal Tool Enterprise * Customer Portal Pro * Customer Portal Enterprise Joining our workspace gives you direct access to our team. You can ask any questions related to your app in your dedicated channel. ### How to Join Slack #### Step 1: Join the Workspace 1. Click the **blue question mark** button in the bottom-right corner. 2. Select **Slack Channel** from the support options. 3. Follow the instructions to join the workspace. #### Step 2: Access Your Channel 1. Your Slack email may differ from your registered email; you can enter a different email if needed. 2. The default channel name is `jetadmin_`, but you can change it. 3. Once completed, you’ll be added to your specific Slack channel. ### Need Help? If you have any issues joining, reach out via live chat or email us at ****. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.jetadmin.io/faq-and-troubleshooting/how-to-connect-to-slack-channel.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.