docs(4838ca3b-09dd-418e-ae65-da2141b5b1b5): Document OAuth connection privacy controls for FGA organizations by claude[bot] · Pull Request #832 · RelevanceAI/relevance-docs

claude · 2026-09-22T09:41:01Z

Summary

Expands the "Privacy and account visibility" section in user-level-authentication.mdx with a new #### subsection covering FGA-specific OAuth connection privacy controls
Documents that new connections in FGA organizations default to "Private to you", with explicit per-card status labels and a "Share with project" action
Adds a <Warning> callout that sharing is permanent and irreversible without removing and reconnecting
Notes that non-FGA organizations are unaffected

Test plan

Verify heading capitalization (sentence case)
Verify <Warning> callout is a single paragraph with no bullets or bold labels
Verify all internal links still resolve
Confirm no banned words introduced

Relates to: https://linear.app/relevance/issue/4838ca3b-09dd-418e-ae65-da2141b5b1b5/

mintlify · 2026-09-22T09:41:08Z

Preview deployment for your docs. Learn more about Mintlify Previews.

Project	Status	Preview	Updated
relevanceai	🟢 Ready	View Preview	Oct 16, 2026, 5:16 AM

💡 Tip: Enable Automations to automatically generate PRs for you.

vercel · 2026-09-22T09:41:08Z

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated
relevance-docs	Ready	Preview	Oct 16, 2026 5:18am UTC

linear · 2026-09-22T09:41:13Z

TSP-1467

github-actions · 2026-09-22T09:43:42Z

🎯 Vibe check

Reviewed: 1 file (1 with issues, 0 clean)

Scores

	Dimension	Score	What's holding it back
🟡	Consistency	6/10	Five Card titles in the "Why use" section use title case instead of sentence case; heading at line 90 inconsistently lowercases the feature name; "seamless" (line 116) is a form of banned "seamlessly"
🟡	Technical clarity	7/10	Anchor link `/enterprise/rbac#permissions` is ambiguous (three `### Permissions` headings in rbac.mdx); setup steps (lines 100–102) use vague navigation language ("Head into", "Head to") rather than exact UI element names
🟢	Non-technical clarity	9/10	Feature is well-defined before instructions begin; limitations and unsupported cases are clearly called out; FAQ covers the likely questions
🟡	Structure	7/10	`<Warning>` at line 87 has a bold label inside it (violates CLAUDE.md callout rules); `<Columns>` component is not standard Mintlify and not seen elsewhere in the repo; no closing CTA for what is primarily a concept page

Score key: 🟢 9–10, 🟡 6–8, 🔴 1–5.

✨ Overall vibe: Solid content that covers the feature thoroughly with a good FAQ — the FGA privacy controls section in particular is well-detailed. Main cleanup needed is the title-case slip in the "Why use" card group, a callout formatting violation, and an unverified <Columns> component that should be swapped for standard <CardGroup> if it isn't confirmed valid.

🔧 Issues (8)

user-level-authentication.mdx:36 — Card title "Enhanced Security" → "Enhanced security" (title case, not sentence case)
user-level-authentication.mdx:39 — Card title "Privacy Protection" → "Privacy protection"
user-level-authentication.mdx:42 — Card title "Access Control" → "Access control"
user-level-authentication.mdx:45 — Card title "Simplified Management" → "Simplified management"
user-level-authentication.mdx:48 — Card title "Audit Trail" → "Audit trail"
user-level-authentication.mdx:90 — Heading ## Setting up user level authentication inconsistently lowercases the feature name — every other heading on this page capitalizes it as a proper noun: ## Setting up User Level Authentication
user-level-authentication.mdx:107 — Anchor /enterprise/rbac#permissions is ambiguous: rbac.mdx has three separate ### Permissions headings (org-level, project-level, asset-level). Mintlify will likely resolve to the first (org-level), which isn't what this note means. Link to /enterprise/rbac or find the correct per-section anchor.
user-level-authentication.mdx:116 — "seamless and intuitive" — "seamless" is a form of banned "seamlessly". Rewrite: "the authentication flow is straightforward" or "users are prompted once and credentials are saved automatically."

🧩 Component suggestions (2)

user-level-authentication.mdx:16,35,72 — <Columns cols={N}> wrapping <Card> components is not seen elsewhere in this repo (sibling pages use <CardGroup cols={N}>). <Columns> is not a documented standard Mintlify layout component — flag for verification or replace with <CardGroup cols={2}> / <CardGroup cols={3}> which is confirmed to work.
user-level-authentication.mdx:87 — <Warning> contains a bold label (**Embedded chat is NOT currently supported.**). CLAUDE.md prohibits bold labels inside callouts. Drop the bold and let the callout type carry the weight: Embedded chat is not currently supported. Users who embed agents via the embed widget cannot use User Level Authentication — use a shared account for those integrations instead.

🏗️ Page structure (1)

user-level-authentication.mdx — No closing CTA. This is a concept + how-to page that introduces a meaningful Enterprise feature; readers finishing the FAQ need somewhere to go. Suggest a short ## Learn more section with links to /enterprise/rbac (permissions model) and /enterprise/integration-controls (enabling the integrations that ULA applies to).

⚠️ Contradictions (0)

No contradictions found. The claims about which roles can add personal OAuth accounts (line 124, 141, 172) align with the permission table in rbac.mdx (line 117). The note about shared accounts remaining admin-managed matches rbac.mdx (line 135).

🔋 Credit usage

Item	Count
Files reviewed	1
Context pages read	2
Total lines processed	~615

Files read: enterprise/user-level-authentication.mdx (233 lines), enterprise/rbac.mdx (382 lines), enterprise/integration-controls.mdx (42 lines)

… privacy controls for FGA organizations Expand the "Privacy and account visibility" section to cover the new explicit privacy controls available to Fine-Grained Access (FGA) orgs: default-private connections, per-card status labels, the Share with project action, post-connect nudge, and the irreversibility warning. Non-FGA behavior is unchanged and noted explicitly. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

github-actions · 2026-10-08T02:22:31Z

🎯 Vibe check

Reviewed: 1 file (1 with issues, 0 clean)

Scores

	Dimension	Score	What's holding it back
🟡	Consistency	7/10	5 card titles use title case ("Enhanced Security", "Privacy Protection", "Access Control", "Simplified Management", "Audit Trail"); heading capitalization is inconsistent for "user level authentication"; "seamless" at line 116 is functionally the same as banned "seamlessly".
🟡	Technical clarity	7/10	Anchor link `/enterprise/rbac#permissions` (line 107) resolves to the org-level permissions table — ambiguous since "Permissions" appears three times in rbac.mdx — and the link text says "asset-level authentication controls," which is actually documented at `/enterprise/asset-controls`.
🟢	Non-technical clarity	9/10	Well scoped, concrete examples (Google Drive, Slack, HubSpot), and the step-by-step first-authentication flow is clear. Minor: "seamless and intuitive" at line 116 adds no information.
🟡	Structure	7/10	`<Columns>` is not a standard Mintlify component — sibling pages use `<CardGroup cols={N}>` for the same pattern. Bold label inside `<Warning>` at line 87 violates callout rules. Missing closing CTA for an enterprise feature page.

Score key: 🟢 9–10, 🟡 6–8, 🔴 1–5.

✨ Overall vibe: Solid, thorough page — covers requirements, scope, limitations, and the user flow in good detail. The main cleanup items are mechanical: swap <Columns> for <CardGroup>, fix the card title casing, and correct the anchor link in the Note at line 107.

🔧 Issues (8)

user-level-authentication.mdx:36 — title="Enhanced Security" → title="Enhanced security" (sentence case; "security" is not a proper noun)
user-level-authentication.mdx:39 — title="Privacy Protection" → title="Privacy protection"
user-level-authentication.mdx:42 — title="Access Control" → title="Access control"
user-level-authentication.mdx:45 — title="Simplified Management" → title="Simplified management"
user-level-authentication.mdx:48 — title="Audit Trail" → title="Audit trail"
user-level-authentication.mdx:90 — heading ## Setting up user level authentication uses lowercase; all other H2s treat "User Level Authentication" as a proper noun (e.g. line 12, 34, 53, 68). Pick one convention and apply it consistently across all headings.
user-level-authentication.mdx:107 — link [asset-level authentication controls](/enterprise/rbac#permissions) has two problems: (1) asset-level auth controls are documented at /enterprise/asset-controls, not rbac; (2) #permissions is ambiguous — it appears three times in rbac.mdx and will land on the org-level permissions table. Consider linking to /enterprise/asset-controls instead.
user-level-authentication.mdx:116 — "the authentication flow is seamless and intuitive" — "seamless" is the same marketing filler as banned "seamlessly". Replace with a factual description, e.g. "users are prompted inline and credentials are saved for future runs."

🧩 Component suggestions (2)

user-level-authentication.mdx:16,35,72 — <Columns cols={N}> is not a standard Mintlify component and does not appear anywhere else in the repo. The sibling rbac.mdx uses <CardGroup cols={2}> and <CardGroup cols={3}> for identical card-grouping patterns. Replace all three <Columns> usages with <CardGroup cols={N}>.
user-level-authentication.mdx:87 — <Warning> contains **Embedded chat is NOT currently supported.** as a bold lead-in label. CLAUDE.md requires callouts to be a single short paragraph with no bold labels inside. Remove the bold and fold the emphasis into the sentence: e.g. "Embedded chat is not currently supported. Users who embed agents on external sites via the embed widget must use a shared account for those integrations instead."

🏗️ Page structure (1)

user-level-authentication.mdx — no closing CTA. This is a concept/feature page for an enterprise feature that depends on two other features; readers finishing the FAQ have nowhere obvious to go. A short ## What's next? with links to /enterprise/asset-controls (asset-level auth controls, directly referenced in the body) and /enterprise/rbac (the permission system that governs who can add OAuth accounts) would round the page off.

🔋 Credit usage

Item	Count
Files reviewed	1
Context pages read	2
Total lines processed	~615

Files read: enterprise/user-level-authentication.mdx (233 lines), enterprise/rbac.mdx (382 lines), enterprise/asset-controls.mdx (43 lines)

Privacy labels and the share button render for every org (gated by oauth-connection-sharing-ux-fe at 100%), not just FGA orgs. FGA only controls whether new connections default to private; non-FGA orgs default to shared. Share is a button on the card in the customer layout, and the nudge copy matches the banner variant. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

github-actions · 2026-10-16T00:43:28Z

🎯 Vibe check

Reviewed: 1 file (1 with issues, 0 clean)

Scores

	Dimension	Score	What's holding it back
🟡	Consistency	7/10	Five card titles in title case instead of sentence case; seven-plus instances of "agent/agents" written lowercase when referring to the Relevance AI product feature; marketing adjective "seamless" on line 116 echoes the banned "seamlessly" pattern.
🟡	Technical clarity	8/10	The anchor `/enterprise/rbac#permissions` likely resolves to the org-level permissions table (rbac.mdx has three `### Permissions` headings, so `#permissions` hits the first one); the Chat project role limitation on ULA is documented in rbac.mdx but absent from the Limitations section here.
🟡	Non-technical clarity	8/10	"The authentication flow is seamless and intuitive" (line 116) is marketing copy that tells the reader nothing. The Note on line 107 drops "asset-level authentication controls" without a prior definition — non-technical readers won't know what that means.
🟡	Structure	7/10	`<Columns>` used to lay out `<Card>` elements is not seen elsewhere in this repo — `<CardGroup>` is the Mintlify-standard way to arrange cards. No closing CTA for what is a concept+setup page.

Score key: 🟢 9–10, 🟡 6–8, 🔴 1–5.

✨ Overall vibe: The content is thorough and well-structured — the step-by-step setup, the embedded demos, and the FAQ are all genuinely useful. The main drag is mechanical consistency: the "Why use" section's card titles all use title case, and "agent/agents" is written lowercase throughout a page that is entirely about the Relevance AI Agent product feature. Fix the caps and anchor link, and this ships cleanly.

🔧 Issues (14)

Card title capitalization (sentence case required)

site/content/docs/enterprise/user-level-authentication.mdx:37 — title="Enhanced Security" → "Enhanced security"
site/content/docs/enterprise/user-level-authentication.mdx:39 — title="Privacy Protection" → "Privacy protection"
site/content/docs/enterprise/user-level-authentication.mdx:43 — title="Access Control" → "Access control"
site/content/docs/enterprise/user-level-authentication.mdx:46 — title="Simplified Management" → "Simplified management"
site/content/docs/enterprise/user-level-authentication.mdx:49 — title="Audit Trail" → "Audit trail"

Agent capitalization (product feature = proper noun)

site/content/docs/enterprise/user-level-authentication.mdx:10 — "same shared agent" → "same shared Agent"
site/content/docs/enterprise/user-level-authentication.mdx:92 — "at the agent level" → "at the Agent level"
site/content/docs/enterprise/user-level-authentication.mdx:104 — "any agent using this tool" → "any Agent using this tool"
site/content/docs/enterprise/user-level-authentication.mdx:116 — "an agent in Chat" → "an Agent in Chat"
site/content/docs/enterprise/user-level-authentication.mdx:124 — "using an agent with dynamic authentication" → "using an Agent with dynamic authentication"
site/content/docs/enterprise/user-level-authentication.mdx:153 — "If an agent uses two Google Drive tools" → "If an Agent uses two Google Drive Tools"
site/content/docs/enterprise/user-level-authentication.mdx:157 — "accounts are used by agents" → "accounts are used by Agents"

Banned-word-adjacent / fluff

site/content/docs/enterprise/user-level-authentication.mdx:116 — "the authentication flow is seamless and intuitive" — remove or replace with a concrete description of what the user sees (e.g., "Users are prompted once per tool; subsequent runs proceed without interruption.")

Potentially broken anchor link

site/content/docs/enterprise/user-level-authentication.mdx:107 — Link /enterprise/rbac#permissions is ambiguous: rbac.mdx contains three ### Permissions headings (org-level, project-level, asset-level). The #permissions fragment will resolve to the first one (org-level), but the context here is asset-level controls. Use a more specific anchor or link to the asset-level section directly.

🧩 Component suggestions (1)

site/content/docs/enterprise/user-level-authentication.mdx:16–82 — <Columns> is used three times (cols={2}, cols={2}, cols={3}) to lay out <Card> elements. This component is not seen elsewhere in this repo; <CardGroup cols={N}> is the standard Mintlify way to arrange cards in a grid. Verify that <Columns> renders the cards correctly in the Mintlify preview. If it does not, replace all three instances with <CardGroup cols={2}> / <CardGroup cols={3}>.

🏗️ Page structure (2)

site/content/docs/enterprise/user-level-authentication.mdx — No closing CTA. This is a concept+setup page; readers who finish it need somewhere to go next. Add a ## What's next? section with links to /enterprise/rbac (for permission scoping) and /enterprise/quick-start-guide (for broader Enterprise onboarding).
site/content/docs/enterprise/user-level-authentication.mdx:84–88 — The Limitations section only mentions embedded chat. rbac.mdx documents that users assigned the Chat project role (distinct from the Chat interface) cannot use dynamic OAuth connections at all — they must be assigned a Member role in a dedicated project instead. This is a second, distinct limitation that belongs here so readers don't have to cross-reference.

✅ Clean files (0)

No files were fully clean in this PR.

🔋 Credit usage

Item	Count
Files reviewed	1
Context pages read	2
Total lines processed	~615

Files read: site/content/docs/enterprise/user-level-authentication.mdx (233 lines), site/content/docs/enterprise/rbac.mdx (382 lines)

- Members do see project-shared connections (visibility filter includes namespace=project); they just can't reconnect or remove ones others connected without the Editor or Admin project role. - Sharing (UpdateOAuthAccountNamespace) requires project editor. - Project Admins see others' private connections on the integrations page and can remove them, but tool/agent pickers filter to the user's own, so "only you can use" rather than "only you can see and use". Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

github-actions · 2026-10-16T00:49:06Z

🎯 Vibe check

Reviewed: 1 file (1 with issues, 0 clean)

Scores

	Dimension	Score	What's holding it back
🟡	Consistency	6/10	Five Card titles in title case instead of sentence case; one heading inconsistency (`## Setting up user level authentication`); "agent" used in lowercase in multiple places where it refers to the Relevance AI Agent product feature
🟡	Technical clarity	7/10	Anchor `/enterprise/rbac#permissions` is ambiguous (three `### Permissions` headings on that page) and likely resolves to the wrong section; plain numbered list used for setup steps instead of `<Steps>` in two places
🟢	Non-technical clarity	8/10	Feature is explained clearly and the setup flow is easy to follow. Minor marketing phrasing at line 116.
🟡	Structure	6/10	`<Columns>` is not the standard Mintlify card grouping component (should be `<CardGroup cols={N}>`); bold label inside a `<Warning>` callout violates CLAUDE.md rules; FAQ accordion contains a bullet list; no closing CTA on a feature overview page

Score key: 🟢 9–10, 🟡 6–8, 🔴 1–5.

✨ Overall vibe: Solid first draft — the content is thorough, well-scoped, and covers the right scenarios. The main drag is mechanical: five Card titles in title case, a non-standard layout component, and one likely-broken anchor link. Fix those and this will be in good shape.

🔧 Issues (11)

site/content/docs/enterprise/user-level-authentication.mdx:37 — Card title "Enhanced Security" → sentence case: "Enhanced security"
site/content/docs/enterprise/user-level-authentication.mdx:39 — Card title "Privacy Protection" → "Privacy protection"
site/content/docs/enterprise/user-level-authentication.mdx:41 — Card title "Access Control" → "Access control"
site/content/docs/enterprise/user-level-authentication.mdx:45 — Card title "Simplified Management" → "Simplified management"
site/content/docs/enterprise/user-level-authentication.mdx:48 — Card title "Audit Trail" → "Audit trail"
site/content/docs/enterprise/user-level-authentication.mdx:80 — Card description "When a workforce delegates to an agent" — both product features should be capitalized: "When a Workforce delegates to an Agent"
site/content/docs/enterprise/user-level-authentication.mdx:87 — Bold label **Embedded chat is NOT currently supported.** inside a <Warning> — CLAUDE.md explicitly bans bold labels inside callouts. Drop the bold; the Warning component itself signals severity.
site/content/docs/enterprise/user-level-authentication.mdx:90 — Heading ## Setting up user level authentication — "User Level Authentication" is the feature's proper name and should be capitalized even inside a sentence-case heading, the same way "Google Analytics" stays capped. → ## Setting up User Level Authentication
site/content/docs/enterprise/user-level-authentication.mdx:92 — "at the agent level" → "at the Agent level" (product feature)
site/content/docs/enterprise/user-level-authentication.mdx:104 — "any agent using this tool will require" → "any Agent using this Tool"
site/content/docs/enterprise/user-level-authentication.mdx:114 — "an agent in Chat that has User Level Authentication" → "an Agent in Chat"

🧩 Component suggestions (4)

site/content/docs/enterprise/user-level-authentication.mdx:16,35,72 — <Columns cols={N}> wrapping <Card> elements is not the standard Mintlify pattern (not seen elsewhere in this repo). The sibling page rbac.mdx uses <CardGroup cols={N}> for the same purpose. Swap all three instances to <CardGroup cols={2}> / <CardGroup cols={3}> to stay consistent and ensure correct rendering.
site/content/docs/enterprise/user-level-authentication.mdx:100–103 — Three sequential setup steps written as a plain numbered list. CLAUDE.md recommends <Steps> for sequential procedures — the same page already uses <Steps> correctly for the first-time authentication flow (line 126). Wrapping lines 100–103 in <Steps> would make the two setup procedures visually consistent.
site/content/docs/enterprise/user-level-authentication.mdx:160–163 — Same issue: two-step "Setting integration defaults" procedure written as a numbered list. Wrap in <Steps>.
site/content/docs/enterprise/user-level-authentication.mdx:216–223 — FAQ Accordion "Why can't I enable User Level Authentication on my tool?" contains a bullet list. CLAUDE.md says accordion content should use flowing sentences, not bullet lists. Convert to prose: "If you don't see the option, your tool likely uses API key authentication or a Python code step rather than OAuth. To use this feature you'll need a tool that authenticates via OAuth."

🏗️ Page structure (2)

site/content/docs/enterprise/user-level-authentication.mdx:107 — The <Note> links to /enterprise/rbac#permissions. The RBAC page has three separate ### Permissions headings (org-level, project-level, asset-level); Mintlify will resolve #permissions to the first one (org-level), not the asset-level controls section the note is actually about. A more accurate anchor would be /enterprise/rbac#asset-level-controls, or just link to /enterprise/rbac without a fragment if a specific anchor isn't confirmed.
site/content/docs/enterprise/user-level-authentication.mdx — No closing CTA. This is a feature overview page, so readers finishing it need somewhere to go next. A short ## What's next? section linking to /enterprise/rbac ("Set up role-based access controls") and /enterprise/integration-controls ("Manage which integrations your team can use") would round it off.

⚠️ Contradictions (1)

site/content/docs/enterprise/user-level-authentication.mdx:172 says "Reconnecting or removing a shared connection that someone else connected needs the Editor or Admin project role." — site/content/docs/enterprise/rbac.mdx:116 permissions table lists "Manage project-level API keys & OAuths" as Admin-only (Editor column is ❌). These two pages disagree on whether Editors can manage shared OAuth connections. One of them needs to be updated to match the intended behavior.

🔋 Credit usage

Item	Count
Files reviewed	1
Context pages read	2
Total lines processed	~657

Files read: site/content/docs/enterprise/user-level-authentication.mdx (233 lines), site/content/docs/enterprise/rbac.mdx (382 lines), site/content/docs/enterprise/integration-controls.mdx (42 lines)

GetOAuthUrl accepts any project role (chat or viewer and up), so connecting isn't tied to dynamic auth being on. Non-editors only see providers enabled via integration controls (ListProviderAccountsData). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

github-actions · 2026-10-16T01:12:11Z

🎯 Vibe check

Reviewed: 1 file (1 with issues, 0 clean)

Scores

	Dimension	Score	What's holding it back
🟡	Consistency	6/10	Five Card titles at lines 36–50 use title case instead of sentence case; heading at line 90 inconsistently lowercases the product name while all other headings capitalize it; "dynamic authentication" drops in at lines 111, 124, and 230 as an unintroduced synonym for "User Level Authentication".
🟡	Technical clarity	8/10	Role-permission contradiction with `rbac.mdx`: this page says Editor or Admin can reconnect/remove shared connections, but the RBAC permissions table lists only Admin for "Manage project-level API keys & OAuths".
🟡	Non-technical clarity	7/10	Line 172 is a 100-word paragraph that conflates who can connect accounts, what integration controls restricts, what admins can see, and what it takes to modify shared connections — all in one breath. Line 116 uses "seamless" (same spirit as banned "seamlessly").
🟡	Structure	7/10	No closing CTA on a concept/feature page. `<Warning>` at line 86 has a bold label inside, which CLAUDE.md prohibits. `<Columns>` is not seen elsewhere in this repo.

✨ Overall vibe: A well-intentioned page with good use of <Steps>, inline demos, and an FAQ that covers the real edge cases readers will hit. The main weaknesses are mechanical — card title capitalization is inconsistent throughout, a non-standard layout component that should be verified, and a one-line role-permission contradiction with the RBAC reference page that will confuse admins trying to figure out who can manage shared connections.

🔧 Issues (5)

site/content/docs/enterprise/user-level-authentication.mdx:36–50 — Five Card titles use title case instead of sentence case. Fix: "Enhanced Security" → "Enhanced security", "Privacy Protection" → "Privacy protection", "Access Control" → "Access control", "Simplified Management" → "Simplified management", "Audit Trail" → "Audit trail".
site/content/docs/enterprise/user-level-authentication.mdx:90 — Heading reads ## Setting up user level authentication with the product name all-lowercase. Every other heading on this page writes it as "User Level Authentication". Pick one and apply it everywhere; if it's a proper product name, capitalize it in the heading too.
site/content/docs/enterprise/user-level-authentication.mdx:111 — "dynamic authentication" appears here for the first time with no explanation that it's the same thing as User Level Authentication. It recurs at lines 124 and 230. Either pick one term and use it throughout, or introduce the synonym explicitly: "User Level Authentication (also called dynamic authentication in the platform UI)."
site/content/docs/enterprise/user-level-authentication.mdx:116 — "the authentication flow is seamless and intuitive" — "seamless" carries the same marketing weight as banned "seamlessly". Rewrite to describe what actually happens: e.g. "users are prompted inline without leaving the conversation."
site/content/docs/enterprise/user-level-authentication.mdx:172 — Dense 100-word paragraph that mixes four separate access-control concepts in one block: who can connect OAuth accounts, what integration controls restricts, what project admins can see, and which role can modify shared connections. Split into shorter sentences or a short bullet list. The current form is hard to parse for any reader.

🧩 Component suggestions (2)

site/content/docs/enterprise/user-level-authentication.mdx:16, 35, 72 — <Columns cols={N}> is not seen elsewhere in this repo; standard Mintlify layout for card grids is <CardGroup cols={N}>. Verify that <Columns> renders correctly in this deployment, or swap to <CardGroup cols={N}> to match the pattern used across the rest of the docs.
site/content/docs/enterprise/user-level-authentication.mdx:86–88 — <Warning> opens with a bold label: **Embedded chat is NOT currently supported.** CLAUDE.md says callouts must be a single short paragraph with no bold labels inside. Remove the bold and fold it into plain prose: "Embedded chat is not currently supported. Users who embed agents via the embed widget cannot use user level authentication — use a shared account for those integrations instead."

🏗️ Page structure (1)

site/content/docs/enterprise/user-level-authentication.mdx — No closing CTA. This is a concept/feature page and ends after the FAQ with no forward path for the reader. Consider a short ## What's next? section linking to: /enterprise/rbac (role permissions that govern who can manage connections), /enterprise/integration-controls (restricting which integrations are available), and /get-started/chat/introduction (where users will actually encounter the authentication prompt).

⚠️ Contradictions (1)

site/content/docs/enterprise/user-level-authentication.mdx:172 says "Reconnecting or removing a shared connection that someone else connected needs the Editor or Admin project role." — site/content/docs/enterprise/rbac.mdx:116 permissions table shows only Admin (not Editor) can "Manage project-level API keys & OAuths". These two pages give different answers about whether Editors can manage shared OAuth connections. Align them.

🔋 Credit usage

Item	Count
Files reviewed	1
Context pages read	2
Total lines processed	~615

Files read: site/content/docs/enterprise/user-level-authentication.mdx (233 lines), site/content/docs/enterprise/rbac.mdx (382 lines), site/content/docs/enterprise/integration-controls.mdx (42 lines)

- The sidebar entry and page header are "Connectors & API Keys" (useMainNav.ts, pages/integrations/[region]/[project]/index.vue). - Private connections can be shared with a single tool (OAuthAccountToolLink via AccountSelector, asset admins only), so they aren't strictly usable by the owner alone, and admins can pick others' private connections in a tool they've been shared with. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

github-actions · 2026-10-16T01:19:03Z

🎯 Vibe check

Reviewed: 1 file (1 with issues, 0 clean)

Scores

	Dimension	Score	What's holding it back
🟡	Consistency	7/10	Five Card titles in `## Why use User Level Authentication` use Title Case instead of sentence case; `<Warning>` at line 87 has a bold label inside it (prohibited by CLAUDE.md); heading at line 90 lowercases "user level authentication" while every other heading and all body text capitalizes it as a product feature name.
🟡	Technical clarity	7/10	Line 172 is a wall of text that mixes visibility rules, role requirements, and sharing flow into one paragraph — hard to scan. Setup steps (lines 100–103) are vague about exact UI labels ("the agent input setting, which is currently set to 'Set manually'"). "Dynamic authentication" introduced at line 110 and 124 as an apparent synonym for "User Level Authentication" with no equivalence stated.
🟡	Non-technical clarity	8/10	Intro and FAQ are clear. Line 116 falls back to marketing phrasing ("seamless and intuitive") instead of describing what actually happens. The dense privacy paragraph at line 172 would lose non-technical readers.
🟡	Structure	7/10	`<Columns>` wrapping `<Card>` elements appears three times (lines 16, 35, 72) — not a standard Mintlify component, unverified in this repo. Setup steps at lines 100–103 are a plain numbered list but describe a sequential procedure that warrants `<Steps>`. No closing CTA on a concept/setup page.

Score key: 🟢 9–10, 🟡 6–8, 🔴 1–5.

✨ Overall vibe: The page is thorough and well-organized — the FAQ is strong, the requirements section clearly separates supported from unsupported, and the first-time auth <Steps> flow is a good UX touchstone. Two things need fixing before merge: five Card titles in the "Why use" section are in Title Case instead of sentence case, and there's a direct contradiction with rbac.mdx about whether Editor-role users can share connections — both pages can't be right.

🔧 Issues (8)

site/content/docs/enterprise/user-level-authentication.mdx:36 — Card title "Enhanced Security" → sentence case: "Enhanced security"
site/content/docs/enterprise/user-level-authentication.mdx:39 — Card title "Privacy Protection" → sentence case: "Privacy protection"
site/content/docs/enterprise/user-level-authentication.mdx:41 — Card title "Access Control" → sentence case: "Access control"
site/content/docs/enterprise/user-level-authentication.mdx:44 — Card title "Simplified Management" → sentence case: "Simplified management"
site/content/docs/enterprise/user-level-authentication.mdx:47 — Card title "Audit Trail" → sentence case: "Audit trail"
site/content/docs/enterprise/user-level-authentication.mdx:87 — **Embedded chat is NOT currently supported.** is a bold label inside a <Warning> — CLAUDE.md prohibits bold labels inside callouts. The callout body should be plain prose: "Embedded chat is not currently supported. Users who embed agents on external sites via the embed widget cannot use user level authentication."
site/content/docs/enterprise/user-level-authentication.mdx:90 — Heading ## Setting up user level authentication lowercases "user level authentication". Every other heading on this page (lines 12, 33, 53, 68) and all body text treats "User Level Authentication" as a capitalized product feature name. Make line 90 consistent: ## Setting up User Level Authentication
site/content/docs/enterprise/user-level-authentication.mdx:116 — "the authentication flow is seamless and intuitive" — marketing phrasing. Describe what actually happens instead, e.g. "a pop-up prompts the user to connect their account on the first run; subsequent runs use saved credentials automatically."

🧩 Component suggestions (2)

site/content/docs/enterprise/user-level-authentication.mdx:16,35,72 — <Columns cols={N}> wrapping <Card> elements is not a standard Mintlify component (<CardGroup cols={N}> is). Not seen elsewhere in this repo — verify it renders as expected before merge.
site/content/docs/enterprise/user-level-authentication.mdx:100–103 — The three-step setup procedure is a plain numbered list, but the same pattern elsewhere on this page (lines 126–139) correctly uses <Steps>. Use <Steps> here for consistency and visual progress indicators.

🏗️ Page structure (2)

site/content/docs/enterprise/user-level-authentication.mdx — No closing CTA. This is a concept/setup page and readers finishing it need somewhere to go. A ## What's next? with two or three links would round it off: /enterprise/rbac (for access controls around who can use agents), /enterprise/integration-controls (for managing which integrations are available org-wide).
site/content/docs/enterprise/user-level-authentication.mdx:110,124 — "Dynamic authentication" is used as a synonym for "User Level Authentication" without introduction. Either state the equivalence once ("User Level Authentication — also referred to as dynamic authentication in the platform UI") or pick one term and use it throughout.

⚠️ Contradictions (1)

site/content/docs/enterprise/user-level-authentication.mdx:172,180 vs site/content/docs/enterprise/rbac.mdx:116 — The user-level-authentication page says sharing a private connection to the project and reconnecting/removing a shared connection "needs the Editor or Admin project role." The RBAC permissions table shows "Manage project-level API keys & OAuths" as Admin-only (Editor gets ❌). Both pages can't be right about whether Editor-role users can manage project-level OAuth connections. Resolve before merge — if Editors genuinely can now share connections, the RBAC table needs updating too.

🔋 Credit usage

Item	Count
Files reviewed	1
Context pages read	2
Total lines processed	~657

Files read: site/content/docs/enterprise/user-level-authentication.mdx (233 lines), site/content/docs/enterprise/rbac.mdx (382 lines), site/content/docs/enterprise/integration-controls.mdx (42 lines)

Only the Connectors drawer (FGA + sharing UX flag) and the tool-step AddAccountModal (FGA) send sharing_permission=user-private. Trigger setup, the Slack relay, error CTAs, signup and native migration send nothing, so the backend default applies: project, unless the org is on the oauth-account-user-controls allowlist. Hence "usually", with the card label as the source of truth. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

- Remove the integration-controls sentence: only the provider-list filter was confirmed, not that it's the list the UI connects from. - "Anyone with access" becomes "you don't need to be an admin". - Shared connections: "see and select", not "use" (Viewers can't run). - Non-FGA and other-path defaults: "may be shared", since the allowlist orgs' FGA status couldn't be confirmed. - Cards live in the integration drawer, so say "when you open an integration". Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

github-actions · 2026-10-16T05:11:14Z

🎯 Vibe check

Reviewed: 1 file (1 with issues, 0 clean)

Scores

	Dimension	Score	What's holding it back
🟡	Consistency	6/10	Five card titles in the "Why use" section use title case instead of sentence case; the feature name "User Level Authentication" is capitalized throughout but lowercased in one heading (line 90); one instance of marketing language
🟡	Technical clarity	7/10	Setup steps use informal "Head into / Head to" instead of specific UI navigation; the `/enterprise/rbac#permissions` anchor is ambiguous (multiple `### Permissions` sections in that page)
🟡	Non-technical clarity	8/10	Mostly accessible — good concept intro and analogy — but the privacy/account-visibility paragraph (line 172) packs too many role distinctions into one run-on sentence
🟡	Structure	7/10	`<Columns>` used where `<CardGroup>` is expected; bold label inside a `<Warning>` callout; bullet list inside an `<Accordion>`; no closing CTA

Score key: 🟢 9–10, 🟡 6–8, 🔴 1–5.

✨ Overall vibe: This page covers the feature thoroughly and its logical progression from "what is it" → "why" → "how to set up" → FAQ works well. The main friction is a cluster of title-case violations on the benefit cards and a few component misuses (bold in a <Warning>, bullets in an <Accordion>) that go against established CLAUDE.md conventions. One potential contradiction with the RBAC permissions table is worth resolving before ship.

🔧 Issues (9)

site/content/docs/enterprise/user-level-authentication.mdx:37 — <Card title="Enhanced Security"> → sentence case: "Enhanced security"
site/content/docs/enterprise/user-level-authentication.mdx:40 — <Card title="Privacy Protection"> → sentence case: "Privacy protection"
site/content/docs/enterprise/user-level-authentication.mdx:42 — <Card title="Access Control"> → sentence case: "Access control"
site/content/docs/enterprise/user-level-authentication.mdx:45 — <Card title="Simplified Management"> → sentence case: "Simplified management"
site/content/docs/enterprise/user-level-authentication.mdx:48 — <Card title="Audit Trail"> → sentence case: "Audit trail"
site/content/docs/enterprise/user-level-authentication.mdx:90 — heading ## Setting up user level authentication lowercases the feature name; every other heading on this page treats "User Level Authentication" as a proper noun. Should be: ## Setting up User Level Authentication
site/content/docs/enterprise/user-level-authentication.mdx:116 — "the authentication flow is seamless and intuitive" — marketing copy. "Seamless" is the adjective form of the banned word "seamlessly"; cut or replace with what the experience actually does (e.g., "Users are prompted to authenticate inline without leaving the conversation")
site/content/docs/enterprise/user-level-authentication.mdx:100–102 — "Head into your Agent and click Tools. Head to the Tool you want to set User Level Authentication on" — informal and imprecise. Reference exact UI element names as they appear in the product (e.g., "Open the agent, then click Tools in the left panel")
site/content/docs/enterprise/user-level-authentication.mdx:107 — link /enterprise/rbac#permissions is ambiguous: rbac.mdx has three separate ### Permissions tables (org-level, project-level, asset-level). Mintlify anchors on the first match, which is the org-level table — not the asset-level controls the Note is pointing to. Use a more specific anchor or link directly to the page without the anchor and describe where to look

🧩 Component suggestions (3)

site/content/docs/enterprise/user-level-authentication.mdx:16–29, 35–51, 72–82 — <Columns cols={N}> wrapping <Card> elements is not seen elsewhere in this repo. The Mintlify convention (and what CLAUDE.md prescribes) is <CardGroup cols={N}>. Either verify <Columns> renders identically and is intentional, or swap all three instances to <CardGroup>
site/content/docs/enterprise/user-level-authentication.mdx:86–88 — <Warning> opens with **Embedded chat is NOT currently supported.** — CLAUDE.md forbids bold labels inside callouts. Rewrite as a plain sentence: "Embedded chat is not currently supported. Users who embed agents via the embed widget must use a shared account for those integrations instead."
site/content/docs/enterprise/user-level-authentication.mdx:217–222 — The accordion "Why can't I enable User Level Authentication on my tool?" ends with a bullet list (- Your tool uses API key authentication / - Your tool uses a Python code step). CLAUDE.md requires accordion content to use flowing sentences. Rewrite: "If the 'Per-user authentication' option isn't available, your tool likely uses API key authentication or a Python code step — neither of which supports OAuth. Switch to an OAuth-based tool or use a shared account instead."

🏗️ Page structure (1)

site/content/docs/enterprise/user-level-authentication.mdx — no closing CTA. This is a concept+setup page; readers who finish it need somewhere to go next. A ## What's next? with links to /enterprise/rbac (to understand which roles can configure per-user auth) and /enterprise/integration-controls (to understand which integrations can be enabled) would round it off naturally.

⚠️ Contradictions (1)

site/content/docs/enterprise/user-level-authentication.mdx:180–181, 183 says "Sharing needs the Editor or Admin project role" and "Reconnecting or removing a shared connection that someone else connected needs the Editor or Admin project role." — site/content/docs/enterprise/rbac.mdx:116 shows only Admin (not Editor) can "Manage project-level API keys & OAuths". If Editors genuinely gained this capability with the User Level Authentication feature, update the RBAC permissions table to reflect it; if not, remove Editor from these claims.

🔋 Credit usage

Item	Count
Files reviewed	1
Context pages read	2
Total lines processed	~657

Files read: site/content/docs/enterprise/user-level-authentication.mdx (233 lines), site/content/docs/enterprise/rbac.mdx (382 lines), site/content/docs/enterprise/integration-controls.mdx (42 lines)

Drops the nudge copy and the separate heading. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

github-actions · 2026-10-16T05:12:51Z

🎯 Vibe check

Reviewed: 1 file (1 with issues, 0 clean)

Scores

	Dimension	Score	What's holding it back
🟡	Consistency	7/10	Five Card titles in title case ("Enhanced Security", "Privacy Protection", "Access Control", "Simplified Management", "Audit Trail"); heading inconsistency on line 90; marketing-adjacent "seamless" on line 116.
🟡	Technical clarity	7/10	Note at line 107 links to `/enterprise/rbac#permissions` to describe "asset-level authentication controls" — that feature has its own page (`/enterprise/asset-controls`) and the anchor may not exist in rbac.mdx. Dense, multi-condition paragraph in the privacy section (line 172).
🟢	Non-technical clarity	8/10	Intro is plain English, feature is defined before instructions begin. The Warning callout at line 87 has a bold label inside it, which CLAUDE.md prohibits.
🟡	Structure	7/10	`<Columns>` is not a standard Mintlify component (standard is `<CardGroup cols={N}>`); the first 4-card block describes a sequential process more naturally suited to `<Steps>`.

Score key: 🟢 9–10, 🟡 6–8, 🔴 1–5.

✨ Overall vibe: This page does solid work — it covers edge cases well (per-tool vs per-integration auth, embedded chat limitation, admin visibility of private connections), the FAQ is comprehensive, and the tone is appropriately technical without being dry. The main drag is mechanical: five Card titles in title case, a non-standard layout component to verify, and a Note that appears to link to the wrong page.

🔧 Issues (8)

site/content/docs/enterprise/user-level-authentication.mdx:36 — Card title="Enhanced Security" → sentence case: "Enhanced security"
site/content/docs/enterprise/user-level-authentication.mdx:39 — Card title="Privacy Protection" → "Privacy protection"
site/content/docs/enterprise/user-level-authentication.mdx:42 — Card title="Access Control" → "Access control"
site/content/docs/enterprise/user-level-authentication.mdx:45 — Card title="Simplified Management" → "Simplified management"
site/content/docs/enterprise/user-level-authentication.mdx:48 — Card title="Audit Trail" → "Audit trail"
site/content/docs/enterprise/user-level-authentication.mdx:87 — **Embedded chat is NOT currently supported.** is a bold label inside a <Warning>; CLAUDE.md says no bold labels inside callouts. Drop the bold — the Warning callout itself signals severity.
site/content/docs/enterprise/user-level-authentication.mdx:90 — Heading ## Setting up user level authentication uses lowercase while every other heading on the page treats "User Level Authentication" as a capitalized feature name. Pick one and apply it consistently across all headings.
site/content/docs/enterprise/user-level-authentication.mdx:116 — "the authentication flow is seamless and intuitive" — "seamless" is marketing-adjacent (near-synonym of the banned "seamlessly"). Describe the actual behavior: e.g. "users see a single prompt the first time, then the agent runs without interruption."

🧩 Component suggestions (2)

site/content/docs/enterprise/user-level-authentication.mdx:16–29 — The four cards "Builders configure / Users authenticate / Credentials persist / Defaults apply" describe a sequential process, not parallel navigable choices. Replace with <Steps> so readers understand the flow order. As cards, the sequence is invisible.
site/content/docs/enterprise/user-level-authentication.mdx:16,35,72 — <Columns cols={N}> is not a standard Mintlify component; standard Mintlify uses <CardGroup cols={N}>. Not seen elsewhere in this repo — verify it renders as expected, or replace with <CardGroup cols={2}> / <CardGroup cols={3}>.

⚠️ Contradictions (1)

site/content/docs/enterprise/user-level-authentication.mdx:107 — The <Note> links [asset-level authentication controls](/enterprise/rbac#permissions) to the RBAC page, but "asset-level authentication controls" is a distinct feature with its own dedicated page at /enterprise/asset-controls. The anchor #permissions also doesn't correspond to a heading visible in rbac.mdx. The link appears to point to the wrong page — should likely be /enterprise/asset-controls.

🔋 Credit usage

Item	Count
Files reviewed	1
Context pages read	2
Total lines processed	~323

Files read: site/content/docs/enterprise/user-level-authentication.mdx (233 lines), site/content/docs/enterprise/rbac.mdx (80 lines, first section), site/content/docs/enterprise/asset-controls.mdx (43 lines)

github-actions · 2026-10-16T05:14:56Z

🎯 Vibe check

Reviewed: 1 file (1 with issues, 0 clean)

Scores

	Dimension	Score	What's holding it back
🟡	Consistency	6/10	Five card titles with extraneous title-case words; "User Level Authentication" capitalized inconsistently across headings; "Workforce" lowercased as product name in two places.
🟡	Technical clarity	7/10	Chat role users can't use dynamic auth (per rbac.mdx) but the Limitations section doesn't mention this. The `/enterprise/rbac#permissions` anchor likely lands on the wrong section.
🟡	Non-technical clarity	7/10	"OAuth authentication only" is introduced as a hard requirement without any plain-English gloss for readers who don't know what OAuth is.
🟡	Structure	7/10	`<Columns>` wrapping `<Card>` not seen elsewhere in the repo — CLAUDE.md calls for `<CardGroup>` for icon feature lists. Bold label inside a `<Warning>`. No closing CTA for a concept+how-to page.

Score key: 🟢 9–10, 🟡 6–8, 🔴 1–5.

✨ Overall vibe: The content itself is solid — clear requirements, useful gotchas (per-tool vs per-integration auth), and well-structured steps. The issues are almost entirely mechanical: a batch of title-case card titles that didn't get sentence-cased, a component choice that deviates from house style, and one real content gap (the Chat role limitation is called out in rbac.mdx but silently absent from the Limitations section here).

🔧 Issues (9)

user-level-authentication.mdx:36 — Card title "Enhanced Security" → "Enhanced security" (sentence case; "security" is not a proper noun)
user-level-authentication.mdx:39 — Card title "Privacy Protection" → "Privacy protection"
user-level-authentication.mdx:42 — Card title "Access Control" → "Access control"
user-level-authentication.mdx:45 — Card title "Simplified Management" → "Simplified management"
user-level-authentication.mdx:48 — Card title "Audit Trail" → "Audit trail"
user-level-authentication.mdx:80,211 — "a workforce delegates" → "a Workforce delegates" (Workforce is a product feature; both the in-page card and the FAQ accordion lowercase it when they should capitalize)
user-level-authentication.mdx:12,33,53,68 vs 90,116 — "User Level Authentication" is capitalized in four headings as a product feature name, then suddenly lowercase in ## Setting up user level authentication (L90) and ## User experience in Chat body text (L116). Pick one treatment and apply it consistently throughout.

🧩 Component suggestions (4)

user-level-authentication.mdx:16,35,72 — <Columns> wrapping <Card> elements is not seen elsewhere in the repo. CLAUDE.md explicitly calls for <CardGroup cols={N}> for icon feature lists — swap all three <Columns> wrappers for <CardGroup> with the matching cols value (2, 2, and 3 respectively). Verify <Columns> renders as expected before keeping it.
user-level-authentication.mdx:86–88 — The <Warning> opens with a bold label (**Embedded chat is NOT currently supported.**) inside the callout body. CLAUDE.md says callouts must be a single short paragraph with no bold labels inside. Move the emphasis into the prose: <Warning>Embedded chat is not currently supported. Users who embed agents on external sites via the embed widget cannot use User Level Authentication — use a shared account for those integrations instead.</Warning>

🏗️ Page structure (2)

user-level-authentication.mdx — No closing CTA. This is a concept + how-to page; readers who just learned how to configure the feature need somewhere to go next. Add a ## What's next? section pointing to /enterprise/rbac (for managing who can use shared vs individual accounts) and /enterprise/asset-controls (for per-tool authentication controls at the asset level).
user-level-authentication.mdx:107 — The Note links to /enterprise/rbac#permissions. In rbac.mdx, the first heading that matches #permissions is the org-level Permissions table (L67) — not the asset-level controls the Note is describing. Either link to /enterprise/asset-controls directly, or target a more specific anchor like /enterprise/rbac#asset-level-controls.

⚠️ Contradictions (1)

user-level-authentication.mdx:84–88 (Limitations) says the only unsupported context is embedded chat. But rbac.mdx:172 explicitly states: "Dynamic (user-level) OAuth connections are not supported for Chat role users; if an agent requires dynamic authentication, assign the user a Member role in a dedicated project instead." The Limitations section here needs a second bullet covering the Chat project role. This is a real gap — a user assigned the Chat role who tries to use an agent with User Level Authentication will hit a silent failure with no guidance from this page.

🔋 Credit usage

Item	Count
Files reviewed	1
Context pages read	2
Total lines processed	~654

Files read: enterprise/user-level-authentication.mdx (230 lines), enterprise/rbac.mdx (381 lines), enterprise/asset-controls.mdx (43 lines)

Three passages (setup Info block, first-time auth, FAQ) said members can't view shared accounts and that they're admin-managed. Shared accounts are visible to everyone (visibility filter includes namespace=project), and Editors as well as Admins can reconnect or remove ones others connected (CanEditGlobalProjectAccounts = editor). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

github-actions · 2026-10-16T05:19:14Z

🎯 Vibe check

Reviewed: 1 file (1 with issues, 0 clean)

Scores

	Dimension	Score	What's holding it back
🟡	Consistency	7/10	Five Card titles in the "Why use" section use title case instead of sentence case (lines 36, 39, 41, 44, 47). Bold lead-in inside a `<Warning>` callout violates the no-bold-labels-in-callouts rule.
🟡	Technical clarity	7/10	"Dynamic authentication" appears three times as an apparent synonym for User Level Authentication but is never introduced or defined. One setup step uses a vague UI reference ("the agent input setting") rather than the exact label.
🟢	Non-technical clarity	9/10	The intro defines the feature plainly, the flow from concept → setup → user experience is logical, and the FAQ covers real edge cases well. Minor deduction for the undefined "dynamic authentication" alias.
🟡	Structure	7/10	`<Columns>` is not a documented Mintlify component — verify it renders or replace with `<CardGroup>`. The four-step how-it-works flow (lines 16–29) is sequential but presented as cards. No closing CTA on a feature/concept page that ends with FAQs.

Score key: 🟢 9–10, 🟡 6–8, 🔴 1–5.

✨ Overall vibe: Solid enterprise feature page — well-structured, appropriately thorough, and covers the edge cases that matter (OAuth vs. API key, embedded chat limitation, non-admin access). The main friction is mechanical: five Card titles in title case, a banned bold label inside a <Warning>, and a repeated undefined alias ("dynamic authentication") that will quietly confuse readers who haven't heard the term before.

🔧 Issues (6)

site/content/docs/enterprise/user-level-authentication.mdx:36 — Card title "Enhanced Security" → "Enhanced security" (sentence case; "Security" is not a proper noun)
site/content/docs/enterprise/user-level-authentication.mdx:39 — Card title "Privacy Protection" → "Privacy protection"
site/content/docs/enterprise/user-level-authentication.mdx:41 — Card title "Access Control" → "Access control"
site/content/docs/enterprise/user-level-authentication.mdx:44 — Card title "Simplified Management" → "Simplified management"
site/content/docs/enterprise/user-level-authentication.mdx:47 — Card title "Audit Trail" → "Audit trail"
site/content/docs/enterprise/user-level-authentication.mdx:87 — <Warning> opens with **Embedded chat is NOT currently supported.** — CLAUDE.md prohibits bold labels inside callouts. Fold the label into natural prose: "Embedded chat is not currently supported. Users who embed agents on external sites…"

🧩 Component suggestions (3)

site/content/docs/enterprise/user-level-authentication.mdx:16–29 — <Columns cols={2}> is not a standard documented Mintlify component; <CardGroup cols={2}> is the expected pattern. Flag to verify this renders correctly in production, or replace with <CardGroup>. Same applies to the <Columns> instances at lines 35–51 and 72–82.
site/content/docs/enterprise/user-level-authentication.mdx:16–29 — The four cards describe a sequential flow: builders configure → users authenticate → credentials persist → defaults apply. Cards imply parallel equal options; this is a process. Replace with a <Steps> block (four steps, same titles) so the order reads as intentional.
site/content/docs/enterprise/user-level-authentication.mdx:87 — The <Warning> covers a meaningful functional limitation. Once the bold label is removed, consider whether the tone is right: <Warning> is for risk/irreversible actions. A <Note> or <Info> with a clear first sentence ("Embedded chat does not support User Level Authentication") might be a better fit, unless the intent is specifically to warn builders who might ship embedded agents with this configured.

🏗️ Page structure (2)

site/content/docs/enterprise/user-level-authentication.mdx — No closing CTA. This is a concept + how-to page, and readers who just set up the feature need a next step. Suggested ## What's next? pointing to /enterprise/rbac (for broader access control context, already referenced inline) and /enterprise/sso-setup (the natural pairing for enterprise auth configuration).
site/content/docs/enterprise/user-level-authentication.mdx:111,124,228 — "Dynamic authentication" is used three times as an apparent alias for User Level Authentication but is never defined. Either introduce it once near the top ("…also referred to as dynamic authentication in the platform…") or replace all three occurrences with "User Level Authentication" for consistency.

⚠️ Contradictions (1)

user-level-authentication.mdx:73–75 lists Chat as a supported context and user-level-authentication.mdx:228 says "all team members can add their own OAuth accounts." rbac.mdx:172 states "Dynamic (user-level) OAuth connections are not supported for Chat role users" specifically in the MCP access context. The user-level-auth page makes no mention of this restriction. These may be intentionally different contexts (Chat interface vs. MCP mode for Chat-role users), but a reader who has a Chat-role user trying to use this feature will find no warning here. Either confirm the two contexts are truly separate and add a note, or align the scoping.

🔋 Credit usage

Item	Count
Files reviewed	1
Context pages read	2
Total lines processed	~613

Files read: site/content/docs/enterprise/user-level-authentication.mdx (231 lines), site/content/docs/enterprise/rbac.mdx (382 lines)

claude Bot added the docs-drafter Documentation drafted by Claude label Sep 22, 2026

claude Bot assigned jordanc-relevanceai Sep 22, 2026

mintlify Bot deployed to staging September 22, 2026 09:42

View deployment

vercel Bot deployed to Preview September 22, 2026 09:43

View deployment

jordanc-relevanceai force-pushed the TSP-1467/docs-update branch from e4e25e1 to 24fd93d Compare October 8, 2026 02:17

mintlify Bot deployed to staging October 8, 2026 02:18

View deployment

vercel Bot deployed to Preview October 8, 2026 02:19

View deployment

mintlify Bot deployed to staging October 16, 2026 00:39

View deployment

vercel Bot deployed to Preview October 16, 2026 00:42

View deployment

mintlify Bot deployed to staging October 16, 2026 00:46

View deployment

vercel Bot deployed to Preview October 16, 2026 00:47

View deployment

mintlify Bot deployed to staging October 16, 2026 01:09

View deployment

vercel Bot deployed to Preview October 16, 2026 01:11

View deployment

mintlify Bot deployed to staging October 16, 2026 01:14

View deployment

vercel Bot deployed to Preview October 16, 2026 01:16

View deployment

mintlify Bot deployed to staging October 16, 2026 05:07

View deployment

vercel Bot deployed to Preview October 16, 2026 05:09

View deployment

mintlify Bot deployed to staging October 16, 2026 05:10

View deployment

vercel Bot deployed to Preview October 16, 2026 05:11

View deployment

docs: fold default-privacy section into an Info block

9776a03

Drops the nudge copy and the separate heading. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

mintlify Bot deployed to staging October 16, 2026 05:12

View deployment

vercel Bot deployed to Preview October 16, 2026 05:14

View deployment

mintlify Bot deployed to staging October 16, 2026 05:16

View deployment

vercel Bot deployed to Preview October 16, 2026 05:18

View deployment

Conversation

claude Bot commented Sep 22, 2026

Summary

Test plan

Uh oh!

mintlify Bot commented Sep 22, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

vercel Bot commented Sep 22, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

linear Bot commented Sep 22, 2026

Uh oh!

github-actions Bot commented Sep 22, 2026

🎯 Vibe check

Uh oh!

github-actions Bot commented Oct 8, 2026

🎯 Vibe check

Uh oh!

github-actions Bot commented Oct 16, 2026

🎯 Vibe check

Uh oh!

github-actions Bot commented Oct 16, 2026

🎯 Vibe check

Uh oh!

github-actions Bot commented Oct 16, 2026

🎯 Vibe check

Uh oh!

github-actions Bot commented Oct 16, 2026

🎯 Vibe check

Uh oh!

github-actions Bot commented Oct 16, 2026

🎯 Vibe check

Uh oh!

github-actions Bot commented Oct 16, 2026

🎯 Vibe check

Uh oh!

github-actions Bot commented Oct 16, 2026

🎯 Vibe check

Uh oh!

github-actions Bot commented Oct 16, 2026

🎯 Vibe check

Uh oh!

This branch was successfully deployed

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

1 participant

mintlify Bot commented Sep 22, 2026 •

edited

Loading

vercel Bot commented Sep 22, 2026 •

edited

Loading