Enabled RLS does not mean correct separation
In an employee portal, failures usually come from weak perimeter modeling: company scope, manager role, employee history, or shared document logic.
For more — see our payroll software security review.
What needs testing
Can an employee see anything outside their own area? Can a manager cross a boundary? Can a document be retrieved outside the intended path?
For HR & Payroll vendors
CleanIssue specializes in security reviews for HR, payroll, and recruiting software. If you're building an HRIS, payroll tool, or ATS and want an external review of your exposure before a client audit or security questionnaire, see our offer for HR & Payroll vendors.
Go further
Related articles
Three adjacent analyses to keep exploring the same attack surface.
Supabase and HR software: configuration mistakes that expose payslips
The Supabase mistakes that matter in HR or payroll software: incomplete RLS policies, overly open buckets, and weak organization boundaries.
RLS mistakes: the 2026 guide for Supabase, PostgreSQL, and multi-tenant access control
The most expensive RLS mistakes in Supabase and PostgreSQL: incomplete policies, overpowered roles, fragile JWT assumptions, exposed service_role keys, and false confidence.
Supabase HRIS: the data-separation checklist
What to review in an HRIS built on Supabase: RLS policies, organization scope, document storage, and role logic.
Sources
Editorial analysis based on official vendor, project, and regulator documentation.
Related services
If this topic maps to a real risk in your stack, these are the most relevant CleanIssue audits.