How Pam Pod isolation works

Understand tenant boundaries and data separation.

Supabase row-level security enforces pod_id on every tenant table. API keys are scoped to a single Pam Pod. Cross-Pam Pod queries are denied at the database layer.

Expected result

Operators and integrations can access only the Pam Pod tied to their session or API key.

If something goes wrong

If you suspect a cross-tenant issue, stop using the affected key and report details to cs@pamphlet.io immediately.

Contact support · Documentation · Status

Was this page helpful?