import { Card, CardContent, CardHeader, CardTitle, CardDescription, } from "@/components/ui/card"; import { Button } from "@/components/ui/button"; import { Link } from "react-router-dom"; import { Lock, Users, GitBranch } from "lucide-react"; export default function DocsPartnerProposal() { return (

Partner Docs & Gated Area Proposal

This document outlines a proposal for a gated partner documentation area, intended for partners and external integrators who require more detailed API and integration guides than the public docs expose. The gated area will be accessible to approved partners after authentication and agreement to terms.

Scope Content that belongs in the gated partner area
  • Partner API endpoints and sample requests that include partner keys or elevated scopes.
  • Operational integration instructions (webhooks, role mappings, admin endpoints).
  • Deployment scripts, secrets management guidance (redacted for public), and verification flows.
  • Commercial and SLA information, onboarding steps for partner accounts.
Access & Workflow How partners request and receive access
  1. Partner signs NDA and registers interest via sales team.
  2. Docs team creates a partner account and assigns a partner role in Supabase.
  3. Partner gets access to the gated docs area (passwordless SSO or invite link).
  4. Partner changes and feedback are managed via Support or a private Builder space.
Security & Controls Minimum controls for gated content
  • Partner accounts are RBAC-limited and issued short-lived credentials for API testing.
  • Audit logs for partner doc accesses are retained and reviewed monthly.
  • Automation prevents copying internal operational docs into public pages; editors must follow the PR checklist.
Next steps
  • Implement partner role and gated content routing (Auth + middleware).
  • Create Builder space for partner docs drafts and approval workflow.
  • Update CI to only publish public docs from{" "} code/client/pages/docs and prevent internal docs from being included.
); }