Repository navigation
docs(global): a person who connects slack has a page that says how to add, use and remove it - #280
Merged
Conversation
… add, use and remove it Connect Slack takes the shape of Connect Zoom: what you need, add, use, remove, get help. It says that a person connects as themselves through Slack's MCP server, with their own access, that a workspace taking only approved apps asks for the app to be requested first, and that a Slack app's bot is the `slack-api` provider. It gives the ask a person types, the Studio page and its ten-minute link, and what Slack shows where whoever runs Auto registered an app, where consent through Auto is on, and where neither is. It lists what a playbook can do with the scopes the `slack` entry asks, and says that the messages a call answers stay in the playbook's history unless the connection keeps only each answer's size. Removing Slack in Auto forgets the tokens without asking Slack to revoke them, since Slack's metadata for its MCP server names no revocation endpoint; under token rotation the access token ends within twelve hours. At Slack, a member revokes their own authorization, or the app is removed for the workspace, with the steps from Slack's help. What remains names the consent service's lines, those for Slack's notices that the app was removed among them. The docs index and the tools guide link both Connect pages, and the navigation lists Slack's after Zoom's. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What this changes
A person who connects their own Slack account to Auto has a page that says how: Connect Slack, under Guides, Connect data, in the shape of Connect Zoom.
slack-apiprovider.slackentry asks, as asks a business reader would type, and that the messages a call answers stay in the playbook's history for anyone who may read the playbook, who can then read messages Slack would not show them, unless the connection keeps only each answer's size.Connect Zoom gains the matching sentence about Zoom's removal notices, and the connections page says that Auto's own Slack app gives Slack the consent service's address for its notices, as the Zoom app does.
Both Connect pages are now linked from the docs index and from the Next list of Give a function tools.
Checklist
feat(reasoning): .... It becomes the squash commit and the changelog entry.pnpm checkpasses locally, with every file at 100% coverage.