Back to Atlas

Access Control (RBAC)

Role-Based Access Control (RBAC) restricts network access based on a person's role within an organization. It ensures users access only the information they need to do their jobs.

Live Simulation

Alice
Bob
Charlie

Test Access for: Alice (Guest)

Public Page
Source Code
Production DB
Principle of Least Privilege: Users should only have access to what they strictly need.

Interactive: Change user roles (Guest, Developer, Admin) and see how their access permissions change instantly.

Key Principles

  • Least PrivilegeA user should be given only those privileges needed for it to complete its task. No more, no less.
  • Separation of DutiesCritical tasks should be divided among multiple people to prevent fraud or error. (e.g., The person who requests a payment shouldn't be the one to approve it).
  • ScalabilityInstead of managing permissions for every single user, you manage roles. When a new employee joins, you just assign them a role.

Implementation

Define RolesAnalyze job functions (e.g., HR, IT, Sales) and create corresponding roles.
Assign PermissionsMap resources (files, apps, databases) to the roles that need them.
Regular AuditsReview access rights periodically. Remove access when employees leave or change roles ("Access Creep").