<!-- Generated from models/_canonical by scripts/build-model-variants.js. Edit the canonical source, not this file. Behavioural profile for Sarvam: scripts/model-profiles.json -->

#Locale

Examples use Indian conventions: ₹ amounts, IST, dd/mm/yyyy, Aadhaar and DPDP Act where a standard mentions identity or privacy law. Keep them when you copy an example.

---

#Purpose

Rules for enforcing who may do what, in a backend service. Authentication establishes identity (Backend/authentication); authorization decides what that identity may do. Policy modelling is Security/authorization; this package is about where the check lives and how it does not get skipped.

The dominant failure is not a wrong policy. It is a missing check on one endpoint — an authenticated request that returns somebody else's row.

---

#Scope the query; do not check afterwards

ts
// Broken — authenticated, authorized for nothing in particular
const order = await db.order.findUnique({ where: { id: req.params.id } });
if (order.tenantId !== req.auth.tenantId) return res.sendStatus(403);  // one refactor from gone

// Correct — the scope is part of the query
const order = await db.order.findFirst({
  where: { id: req.params.id, tenantId: req.auth.tenantId },
});
if (!order) return res.sendStatus(404);

Filtering in the WHERE clause means there is no window in which the wrong data exists in the process, and no branch to forget. Make it structural: a repository layer that requires a tenant scope, or row-level security in the database, so an unscoped query cannot be written.

sql
-- Postgres RLS: the database refuses to return another tenant's rows
ALTER TABLE orders ENABLE ROW LEVEL SECURITY;
CREATE POLICY tenant_isolation ON orders
  USING (tenant_id = current_setting('app.tenant_id')::uuid);

Return 404 rather than 403 for objects the caller may not see — a 403 confirms the object exists. → API/api-security

---

#One layer owns the decision

Authorization belongs in the service layer, where the domain objects are, not scattered across controllers and templates.

The UI hiding a button is a usability improvement. The request it would have made is still available to anyone with curl.

Centralise the policy so it can be read in one place:

ts
// One function, exhaustively tested, used everywhere
export function can(actor: Actor, action: Action, resource: Resource): boolean;

Scattered if (user.role === "admin") checks cannot be audited, and they drift. Note also that a role check is not a permission check — admin on one tenant is not admin on another.

---

#Model: roles, then attributes

Start with RBAC: roles carry permissions, users hold roles, scoped to a tenant. It covers most systems and is easy to reason about and to display.

Add ABAC/ReBAC only for rules RBAC cannot express — "the owner of the document or a member of its project", "only during business hours", "only below €10,000". Represent them as explicit policy rather than nested conditionals.

For genuinely complex relationship graphs, a dedicated engine (OpenFGA, SpiceDB, Cedar, OPA) is worth the operational cost. Below that, a single well-tested can() function is simpler and faster.

Rules that hold regardless of the model:

• Deny by default. An action with no matching policy is denied.
• Least privilege. New roles start with nothing.
• Check every time, on every request. A permission cached in a JWT is stale the moment access is revoked.
• Field-level too. Reading an order does not imply reading its costBasisCents. Project explicit fields.

---

#The checks people forget

A background job acting on behalf of a user must carry that user's scope, not run unrestricted.

---

#Test denial, not just permission

Authorization tests that only assert the happy path prove nothing. The valuable assertion is that a request fails.

ts
test("a member of tenant B cannot read tenant A's order", async () => {
  const res = await request(app).get(`/v1/orders/${tenantAOrderId}`)
    .set("Cookie", sessionFor(tenantBUser));
  expect(res.status).toBe(404);
});

• One denial test per protected resource type, at minimum.
• A test that enumerates every route and asserts an unauthenticated request is rejected catches the new endpoint someone forgot to protect. Make it fail closed: new routes must be added to an explicit public allowlist.
• Log every denial with actor, action, resource and source IP — a spike is either an attack or a broken deploy. → Security/audit-log

---

#Anti-patterns

---

#Checklist

• Verify: Every data access is scoped to the caller inside the query
• Verify: Tenant scope comes from the session and never from client input
• Verify: Repository or row-level security makes an unscoped query impossible
• Verify: Hidden resources return 404, not 403
• Verify: One central policy function owns every decision
• Verify: Default is deny; new roles start with no permissions
• Verify: Permissions are evaluated per request, not cached in a token
• Verify: Field-level authorization protects sensitive properties
• Verify: Mutations check authorization, not only reads
• Verify: Bulk operations check every element
• Verify: Nested resource paths are verified end to end
• Verify: Background jobs run with an explicit scope
• Verify: Exports and reports are tenant-scoped
• Verify: Admin tooling is authenticated and network-restricted
• Verify: Denial tests exist for every protected resource type
• Verify: A fail-closed test asserts new routes are protected by default
• Verify: Every denial is logged with actor, action, resource and source