The short answer
Tenant isolation means one customer cannot access another customer’s data or operations. Authentication identifies a user; tenant and resource authorization must still be enforced across requests, jobs, files, and exports.
In a business SaaS product, getting the login screen working is only the beginning. A user can be correctly authenticated and still receive a record that belongs to a different customer if the resource boundary is wrong.
PinCRM makes that boundary concrete: agencies have leads, private inventory, roles, and deal workflows. Being allowed to use the product does not mean being allowed to see every agency’s records.
Separate tenant membership from the user’s role
Two questions belong in an access decision: which tenant does this request belong to, and what may this user do inside it? An agent and a manager can belong to the same agency while having different permissions.
Filtering the interface is useful for the experience, but the server must enforce the rule. A record identifier should not be enough to retrieve or change a resource without checking the requesting user’s tenant and permission.
Which isolation model should a SaaS product use?
There is no single layout that fits every product. Pooled, siloed, and mixed approaches make different trade-offs in cost, operations, and separation. Choose the boundary around the data sensitivity, customer requirements, and operating model—not because one diagram looks more sophisticated.
AWS’s tenant-isolation guidance distinguishes those architectural models. The product still needs a consistent authorization policy whichever infrastructure pattern it uses.
Look beyond the main API request
Background jobs, exports, uploaded files, search results, and cached responses all need the right tenant context. A safe screen does not compensate for an export job that gathers another customer’s records.
- Try to access tenant B’s record while signed in to tenant A.
- Repeat the check for updates, downloads, exports, and search.
- Verify that background jobs carry the intended tenant context.
- Check that a role change affects the permissions that matter.
What is the useful architecture question?
Ask where the boundary is enforced and how you can demonstrate it. That turns “we support multi-tenancy” into a reviewable design and concrete checks.
This is a design checklist, not a complete security audit or a claim that a particular infrastructure pattern makes an application secure by itself.