docs: consolidated Slack connection + auth docs (magic link + Builder/SuperGTM)#659
Draft
jordanc-relevanceai wants to merge 4 commits into
Draft
docs: consolidated Slack connection + auth docs (magic link + Builder/SuperGTM)#659jordanc-relevanceai wants to merge 4 commits into
jordanc-relevanceai wants to merge 4 commits into
Conversation
…perGTM Adds a new section and FAQ entry to the Builder Slack integration page clarifying the workspace-level bot token (Builder) vs per-user OAuth (SuperGTM) distinction. Updates the SuperGTM integrations page Slack accordion with the same context and cross-links between pages. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
…eams Documents the new /associate magic link consent flow from PR #15067. Adds a "Linking your account via magic link" section to both integration pages, plus troubleshooting entries and FAQs covering magic link expiry, wrong email addresses, and the equivalence of both connection methods. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
…slack-auth # Conflicts: # integrations/popular-integrations/slack.mdx
Contributor
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Workflows to automatically generate PRs for you. |
This was referenced Jun 3, 2026
docs(TSP-1265): add account linking consent flow documentation for Slack and Teams integrations
#652
Closed
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
1 participant
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.
This PR consolidates 2 drafter PRs that both add Slack connection/authentication documentation to the same page. Opened as draft for review before the source PRs are closed.
Source PRs (being closed in favor of this one)
Why consolidated
Both edit
integrations/popular-integrations/slack.mdxand both add Slack-auth sections plus new FAQ accordions to the same FAQ group — so they conflicted on merge. Together they tell one coherent Slack-connection story (how to connect via magic link, and why the connection differs between Builder and SuperGTM).Changes by source PR
#652 — TSP-1265
slack.mdx— new "Linking your account via magic link" section, a Troubleshooting section (magic link expiry, wrong email), and three magic-link FAQ entries.microsoft-teams.mdx— same magic-link consent flow documented for Teams (new section + two troubleshooting entries + three FAQs).#622 — TSP-1236
slack.mdx— new "Understanding Slack connections in Relevance AI" section (workspace bot token for Builder vs per-user OAuth for SuperGTM) and a FAQ entry: "Why does Slack work in SuperGTM but not in Builder (or vice versa)?".get-started/chat/super-gtm/integrations.mdx— notes SuperGTM uses per-user OAuth, with a cross-link to the Builder Slack docs.Reconciliation note