Manager portal: what a manager can see about their team (and shouldn't)
> TL;DR: Manager portals are often too permissive by default. Three access bugs to fix before a client audit.
What sensitive data should managers never have access to?
The manager portal deserves its own review
In many products, a manager's scope is defined by a simple rule: "employees on my team". That rule is often enforced in the UI, not in the database.
For more — see our AI agent security review.
Typical mistakes
manager_id but doesn't prevent changing the filter.The test that surfaces it
Log in as a manager, try to read an employee outside your team via the API. If it works, the rule is in the wrong place.
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.
Multi-tenant: verifying that one client can't see another's data
Multi-tenant isolation bugs are the most expensive class in a SaaS product. Three quick tests before a client security review.
DPAE data leak: where the risks actually are
DPAE-related flows touch sensitive data and are often treated as plain operations, even though they also create access and traceability risk.
User portal and RLS: what really breaks separation
Even with RLS enabled, a user portal can still expose too much if the business rules behind it stay incomplete.
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.