> 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/integrations/productivity-and-collaboration/slack-integration.md). # Slack PeakCommerce connects to **Slack** so your team can work with commerce data without leaving their workspace. Slack becomes a thin, governed surface over the same commerce logic that runs in the app, not a separate set of rules. ## What it is Slack is a team messaging workspace. Connected to PeakCommerce, it gives your staff a **command surface**: slash commands that resolve against PeakCommerce's real engines — the same identity, permissions, and billing data the app itself uses. ## What you can do today The **`/peak change-plan`** slash command brings the change-plan workflow into Slack: * Run `/peak change-plan` and a dialog opens with an **account picker**, scoped to your territory — you see exactly the accounts you could work in the app, no more. * Pick an account and the dialog shows its **current plan**, the **available plans** it could move to, and the **add-ons** on offer. * What appears is gated by **your own profile**: sections your profile can't act on — say, plan changes you aren't permitted to make — are simply omitted, exactly as they would be hidden in the app. ## How identity and governance work There is no separate "Slack permission model". Your Slack user is **linked to your PeakCommerce user**, and every command runs *as* that user: * Your Slack workspace is mapped to your PeakCommerce tenant; your Slack account is linked to your PeakCommerce account. If you use the command before you're linked, it tells you so rather than failing silently. * Once resolved, the request flows through the **same permission engine as the app** — your profile, your territory scope, your allowed actions. A thing you can't do in the app, you can't do from Slack. * **Every Slack API call is visible in API Call Stats**, alongside your other integration traffic, so failures are diagnosable rather than invisible. * **Every action rides the same audit trail as the web app** — opening a change-plan dialog from Slack is recorded just as it would be in the browser. ## Getting connected Workspace connection is currently **provisioned with PeakCommerce assistance** — contact your PeakCommerce representative to have your Slack workspace connected to your tenant. User linking (Slack account ↔ PeakCommerce account) is set up during that provisioning. ## Coming next Planned, but not available yet: **committing** a plan change directly from Slack (previewing and confirming the change without switching to the app), **event notifications** posted to your channels, and **approval routing** for actions that need sign-off. Until then, Slack is a read-and-explore surface — the change itself is completed in the app. ## Who and when Most useful for support, sales, and revenue teams who live in Slack and need a fast look at an account's plan position — current plan, upgrade options, add-ons — while staying inside policy. ## Gotchas Slack inherits PeakCommerce's permissions: a user can only see in Slack what their profile already allows, for the accounts in their own territory. If the account picker looks smaller than a colleague's, that's your territory scope working as intended. See also: [Productivity and collaboration integrations](/integrations/productivity-and-collaboration/productivity-and-collaboration.md). --- # 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/integrations/productivity-and-collaboration/slack-integration.md?ask=&goal= ``` `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.