perplexity-enterprise-rbac

# Perplexity Enterprise RBAC ## Overview Control access to Perplexity Sonar API at the organizational level. Perplexity does not have built-in RBAC -- you implement access control through: separate API keys per team/environment, a gateway that enforces model and budget policies, and domain restrictions for compliance. ## Access Control Strategy | Layer | Mechanism | Perplexity Support | |-------|-----------|-------------------| | Authentication | API key per team | Yes (multiple keys) | | Model restriction | Gateway enforcement | Build yourself | | Budget cap | Per-key monthly limit | Via dashboard | | Domain restriction | `search_domain_filter` | Yes (per-request) | | Rate limiting | Gateway + key limits | Yes (per-key RPM) | ## Prerequisites - Perplexity API account with admin access - Separate API keys per team/environment - Gateway or middleware for policy enforcement ## Instructions ### Step 1: Create Per-Team API Keys Generate separate keys at [perplexity.ai/settings/api](https://www.perplexity.ai/settings/api): ``` Key: pplx-support-bot-prod → Budget: $200/mo, sonar only Key: pplx-research-team → Budget: $1000/mo, sonar + sonar-pro Key: pplx-data-team → Budget: $500/mo, sonar only Key: pplx-executive-reports → Budget: $300/mo, sonar-pro ``` ### Step 2: Gateway with Policy Enforcement ```typescript // perplexity-gateway.ts import OpenAI from "openai"; interface TeamPolicy { apiKey: string; allowedModels: string[]; maxTokensPerRequ...