> For the complete documentation index, see [llms.txt](https://docs.bugbase.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bugbase.ai/integrations/slack/managing-integration.md).

# Managing Integration

Pre-requisites

* A Slack Workspace with alteast one public channel
* BugBase Company Account with an Active Program
* Slack Integrated with a BugBase Program

**Helpful Links**

{% content-ref url="/pages/DvOtt3DhiAaTGQuQc1Xq" %}
[Slack](/integrations/slack.md)
{% endcontent-ref %}

### Replacing or Updating the configured Slack Channel

1. Navigate to the integrations tab located in the settings page of your BugBase Program. 
2. Click on the `Manage` button on the Slack Integration Card.
3. A modal asking you to `Select a New Channel` will appear.
4. Choose the new channel you want the BugBase Bot to post from the dropdown to and click on `Save`

> Editing a Channel will remove the Slack Bot from the old channel and add it to the new channel.

### Disconnecting or Removing the Slack Integration

1. Navigate to the integrations tab located in the settings page of your BugBase Program.
2. Click on the `Disconnect` Button on the Slack Integration Card
3. A popup will appear asking you to confirm that you want to disconnect the Slack Integration.
4. Click on `Disconnect` to remove the integration from your Workspace.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.bugbase.ai/integrations/slack/managing-integration.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.