> For the complete documentation index, see [llms.txt](https://docs.peakcommerce.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.peakcommerce.com/product/settings/developer-tools/slack.md).

# Slack

**Settings → Slack** is the admin console for PeakCommerce's Slack integration. From one page you connect Slack workspaces, map Slack users to PeakCommerce accounts, and control which slash commands your reps can run — so commerce work can happen in Slack without leaving the conversation.

Access requires the **Integrations → Read** permission (the page is gated the same way as **Integrations** and **Hosted Pages**).

## Why it matters

Reps live in Slack. Connecting a workspace lets PeakCommerce answer slash commands in your channels and attribute each request to the right person, while keeping the bot credentials and per-user mappings under an administrator's control rather than scattered across env files.

## Tabs

The page has three tabs — **Workspaces**, **User Links**, and **Commands**.

### Workspaces

The connected Slack workspaces, shown with their **Enabled** state, whether a **Bot token** is set, and whether a **Signing secret** is configured.

* **Connect workspace** opens a dialog asking for the **Slack Team ID** (for example `T0A1BCDEF`), a **Workspace name**, the **Bot token** (`xoxb-…`), a **Signing secret ref**, and an **Enabled** toggle.
* The **Bot token is stored write-only** — it is saved securely and **never shown again** after you save. To rotate it, edit the workspace and paste a new token; there is no way to read the stored value back out of the console.
* The **Signing secret ref** is the *name* of an environment variable holding the app-level Slack signing secret (shared across workspaces), not the secret value itself.
* The row menu lets you **edit** a workspace (including toggling **Enabled** to pause it without deleting it) or **remove** it.

### User Links

Maps a person's Slack identity to their PeakCommerce user, so a command run in Slack acts as the right account. Each row shows the **PeakCommerce user**, the **Slack user**, and the **Workspace**.

* **Add user link** asks for the **Slack Team ID**, the **Slack User ID** (for example `U0XYZ123`), and the **PeakCommerce user ID**.
* **Re-point link** (edit) moves an existing Slack user to a different PeakCommerce user — useful when someone changes accounts. You can also **remove** a link.

### Commands

The slash commands available to reps in Slack. The command catalog itself — labels and behavior — is **defined by PeakCommerce**; on this tab you control **whether each command is enabled** for your workspaces. Each row shows the **Command**, its **Description**, and an **Enabled** toggle.

* Toggling **Enabled** turns a command on or off for your tenant. A command with no override is **enabled by default**, so a fresh tenant has every command available until you turn one off.
* **Reset to default** clears your tenant's override for a command, returning it to the built-in default.

## Notes

* Enabling or disabling a **workspace** or a **command** takes effect immediately for the next Slack request; you do not need to reconnect.
* Because the bot token is write-only, treat a lost token as a rotation: generate a new one in Slack and paste it into **Edit 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.peakcommerce.com/product/settings/developer-tools/slack.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.