Configure Supabase enterprise SSO, role-based access control, and organization management. Use when implementing SSO integration, configuring role-based permissions, or setting up organization-level controls for Supabase. Trigger with phrases like "supabase SSO", "supabase RBAC", "supabase enterprise", "supabase roles", "supabase permissions", "supabase SAML".
From supabase-packnpx claudepluginhub nickloveinvesting/nick-love-plugins --plugin supabase-packThis skill is limited to using the following tools:
references/errors.mdreferences/examples.mdreferences/role-implementation.mdreferences/sso-integration.mdGuides Next.js Cache Components and Partial Prerendering (PPR) with cacheComponents enabled. Implements 'use cache', cacheLife(), cacheTag(), revalidateTag(), static/dynamic optimization, and cache debugging.
Migrates code, prompts, and API calls from Claude Sonnet 4.0/4.5 or Opus 4.1 to Opus 4.5, updating model strings on Anthropic, AWS, GCP, Azure platforms.
Details PluginEval's skill quality evaluation: 3 layers (static, LLM judge), 10 dimensions, rubrics, formulas, anti-patterns, badges. Use to interpret scores, improve triggering, calibrate thresholds.
Enterprise RBAC for Supabase involves coordinating three systems: your Identity Provider (IdP) for authentication, Supabase's Row Level Security for data authorization, and your application middleware for API-level enforcement. Getting these layers aligned correctly is critical — a misconfigured RLS policy can either block legitimate users or expose data to unauthorized roles, so testing each role definition against real queries before going to production is essential.
Map organizational roles to Supabase permissions. Document each role's data access requirements, which tables they can read or write, and which operations require elevated privileges. Use Postgres roles to enforce separation at the database level.
Set up SAML or OIDC integration with your IdP. Ensure that the IdP passes the correct group or role claims in the token so Supabase can map them to the appropriate Postgres role at session start.
Add permission checks to API endpoints. Middleware should extract the user's role from the JWT and reject requests that attempt operations the role is not authorized for before they reach the database.
Track all access for compliance. Log the authenticated user, role, operation type, and timestamp for every data-modifying request so you have a complete audit trail for security reviews.
See ${CLAUDE_SKILL_DIR}/references/errors.md for comprehensive error handling.
See ${CLAUDE_SKILL_DIR}/references/examples.md for detailed examples.
Configure Supabase enterprise SSO, role-based access control, and organization management.