Implement PostgreSQL Row Level Security policies and session variables in GLAPI multi-tenant services.
npx skills add https://github.com/adteco/glapi --skill glapi-rls-guide
Please help me install this Agent Skill. Skill: glapi-rls-guide Source: https://github.com/adteco/glapi/tree/main/.claude/skills/glapi-rls-guide Command: npx skills add https://github.com/adteco/glapi --skill glapi-rls-guide
GLAPI's multi-tenant databases need reliable Row Level Security and contextual session variables so that organization-specific queries cannot leak data between tenants, especially when repositories or services might inadvertently use global connections.
app.current_organization_id before executing queries, ensuring policies compare organization_id values accurately even across inserts, selects, updates, and deletes.db, follow the ctx.db path, and include debug patterns for diagnosing new row violates row-level security policy errors, illustrating how to add RLS for new tables while keeping migrations aligned.Use the GLAPI RLS guide to outline the steps for enabling PostgreSQL session variables, RLS policies, and contextual database connections when adding a new multi-tenant table.
High-intent search queries and answers about installing and using this skill.
PostgreSQL row level security for multi-tenant isolation requires setting session variables like `app.current_organization_id` on contextual database connections. RLS policies compare this variable against the table's organization_id column to prevent cross-tenant data leakage across inserts, selects, updates, and deletes.
A `new row violates row-level security policy` error occurs when the database connection lacks the required session variable or the RLS policy restricts the insert. Debugging involves verifying contextual session variable initialization and ensuring the repository uses the contextual `ctx.db` connection.
Authenticated tRPC middleware enforces row level security by creating RLS-aware contextual database connections. The middleware validates organization UUIDs, sets the required session variables before executing queries, and safely releases the database client at the end of each request.
You need to enable row level security on every new multi-tenant table to maintain data isolation. This requires adding RLS policy definitions and updating migration files to ensure policies compare the session variable against the new table's organization_id column.
Global database connections bypass row level security policies and risk cross-tenant data leakage. Repositories and services must instead accept a contextual `db` object following the `ctx.db` path to ensure queries execute within the authenticated session variable context.
ValyntAutomate creation, auditing, and enforcement of PostgreSQL row-level security policies.
theeabrarrrEnforce RLS policies with tenant_id guards across database and application layers.
PremModhaOfficialImplement tenant-scoped PostgreSQL CRUD with pgxpool and search_path.
zinohomeEnforce PostgreSQL Row Level Security policies for multi-tenant data isolation.