GEO draft: answer-first blocks, facts tables and FAQ for access requests and why-permit overview pages

[orweis]

Draft for Or / R&D review. Do not merge until reviewed. Part of the GEO/AEO docs answer-ready pass (plan: Action 1, geo-aeo-plan-2026-10-05). Opened by Content Bot on behalf of Or Weis.

Pages

• docs/overview/access-requests-and-approvals.mdx: answer block, facts table, new section "Log the user in to the elements in code" (an adapted permit.elements.login() frontendOnly snippet from embeddable-uis/element-login, the @permitio/permit-js install and the iframe form), FAQ.
• docs/overview/why-permit.mdx: answer block, facts table, a permit.check() code example, FAQ (build vs buy).

Where the facts come from

Repo docs (embeddable UIs, deployment options, differentiator checklist, SOC 2 Type II and HIPAA statements already on the page, Access Request MCP) and the pricing page above ("Embeddable Authorization Interfaces (e.g., User Management)" is listed in the Community plan).

Pricing facts and re-check

Free-tier values are copied from the live https://www.permit.io/pricing page (Community column of Compare Plans, labeled "Free Forever"), fetched 2026-10-05:
MAU 1000, Tenants 20, Authorization Queries No Limit, Environments 3, PDP Instances No Limit (also in the pages that say so: Roles 25, Resource Types 50, Logs Retention 14 days).

• TODO (reviewer): re-open the pricing page before merging and confirm these values still match. Each page has an MDX comment {/* GEO pass: ... */} next to the table naming the source and fetch date.

R&D, please double check

• The login() snippet is adapted from embeddable-uis/element-login.mdx (typed as TS, with a .catch added); it was not run against a live environment.
• Fit statements for access requests ("don't use when your app has no user sign-in or approvals must run entirely outside Permit") are editorial.

Style and checks

• No em or en dashes, no curly quotes, no filler words in added text. Answer-first blocks are 40 to 70 words (counted).
• Existing technical content and existing code samples are unchanged. New content is added under the answer block, in new sections, or before the Next steps section.
• npm run build (redirect-lint, relative links, private paths, Docusaurus build, hyperlink anchors, routes check, sidebar coverage) passed on a temporary branch with all six GEO branches merged.
• Fit statements ("use X when / don't use X when") are editorial. Please confirm they are acceptable.

[netlify]

✅ Deploy Preview for permitio-docs ready!

Name	Link
🔨 Latest commit	9ea11b3
🔍 Latest deploy log	https://app.netlify.com/projects/permitio-docs/deploys/6ac4a0cc2d14710008fa5b6d
😎 Deploy Preview	https://deploy-preview-666--permitio-docs.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify project configuration.