Role Hierarchies

Role Hierarchies Overview

Role Hierarchies lets you structure authentication work so it stays readable, testable, and easy to scale. Instead of ad-hoc code, you follow a clear pattern that other developers can recognise immediately.

The key is to keep role hierarchies focused and predictable. Start from the minimal example here, then layer in only the complexity your feature actually needs.

function requireRole(role) {
  return (req, res, next) => {
    if (req.user?.role !== role) {
      return res.status(403).json({ error: 'Forbidden' });
    }
    next();
  };
}

app.delete('/users/:id', requireRole('admin'), deleteUser);

Authorization middleware checks the authenticated user's role before allowing an action.

Role Hierarchies Example

// verify the caller on every protected request
function authenticate(req, res, next) {
  const token = req.headers.authorization?.replace('Bearer ', '');
  req.user = verifyToken(token); // throws if invalid
  next();
}

• Start from a minimal Role Hierarchies example and grow it only as needed.
• Keep configuration explicit so Role Hierarchies behaves the same in every environment.
• Name things clearly so teammates understand your Role Hierarchies at a glance.
• Add tests around Role Hierarchies early to lock in expected behaviour.

Authentication Cheatsheet

Quick authentication reference related to role hierarchies.

How Role Hierarchies Works

Role Hierarchies is part of proving who a user is and what they are allowed to do. Authentication verifies identity, while authorization decides access — and role hierarchies plays a specific role in that flow.

Authorization middleware checks the authenticated user's role before allowing an action.

• Never store or log plain-text passwords or secrets.
• Prefer short-lived tokens with refresh over long-lived ones.
• Always send credentials over HTTPS.
• Fail closed: deny access when anything is uncertain.

Security Guidance for Role Hierarchies

Security is the whole point of role hierarchies. Small mistakes — weak hashing, tokens in localStorage, missing rate limits — are exactly what attackers look for, so follow proven defaults.

Common Mistakes

• Skipping error handling and edge cases when wiring up role hierarchies.
• Leaving role hierarchies untested, so regressions slip into production.
• Over-engineering role hierarchies before you actually need the extra flexibility.
• Ignoring documentation, which makes role hierarchies hard for the next developer to change.

Key Takeaways

• Role Hierarchies is a core part of working effectively with authentication.
• Start small and keep role hierarchies focused on a single responsibility.
• Apply consistent patterns so role hierarchies scales across your project.
• Test and document role hierarchies to keep it maintainable over time.