User portal and RLS: what really breaks separation
> TL;DR: Even with RLS enabled, an employee portal can still expose too much if the business rules behind it stay incomplete.
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 AI agent 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 software vendors
CleanIssue specializes in security reviews for software handling sensitive data. If you're building a product, payroll tool, or ATS and want an external review of your exposure before a client audit or security questionnaire, see our offer for software vendors.
Key Takeaways
Building software? CleanIssue performs security audits for your product in real-world conditions, no source code access needed. For a first read of your exposure, start with an external review of your application.
Go further
Related articles
Three adjacent analyses to keep exploring the same attack surface.
Supabase: configuration mistakes that expose your sensitive data
The Supabase mistakes that matter in products that store sensitive data: 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.
Manager portal: what a manager can see about their team (and shouldn't)
Manager portals are often too permissive by default. Three access bugs to fix before a client audit.
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.