What is RBAC?

What is RBAC?

What is Role-based Access Control?

Role-Based Access Control (RBAC) is a feature that restricts system access among its users. Each role is defined by sets of permission that grants access to authorized users. This ensures users can only access information and system components relevant to do their job in terms of managing employee records, attendance, and payroll. This feature protects sensitive information to be modified by users without the necessary access permissions.

User Role

A User Role determines permissions that enable a user to perform specific groups of tasks. In Salarium, there are two types of User Roles that can be assigned to users:

System-defined Role
User-defined Role
  1. Default roles with varying user-level system access
  2. Ready-to-assign user role with a default set of permission
  3. Cannot be edited or deleted
  1. Roles with customized system access restriction
  2. The defined set of permissions for each role is relevant to the user's specific job requirements
  3. Can be edited or deleted

Permissions

Permission is the overlapping result of configured scope and action that defines a User Role. When creating custom roles, setting permissions are defined by configuring two aspects of control within a role:


Default Permissions under System-Defined Roles

The table below shows the list of system-defined user roles with default permissions. Each set of permission under each role enables and limits a user's access to certain pages in Salarium. These permissions cannot be edited nor deleted. User roles that do not display the same permissions as below fall under user-defined roles.



Defining Permissions when Creating a User-defined Role
Creating a user-defined role is defining a set of permission that authorizes a user to access the pages and information relevant to the job. To ensure a smooth process when creating a custom role, it is best to be guided with the following questions:


  1.  Role Name: Defining the Role Name says something about why a certain user should be created and for what purpose. Planning ahead and considering the necessity of creating the role helps streamline the scope and action the role should have.
  2. Company Scope: Selecting which companies that can be accessed by the role should be identified. 
  3. Other Scopes: Defining other scopes include allowing access to each company's Departments, Positions, Location, Payroll Group, and Teams.
  4. Actions: Defining a set of allowed function a role can perform within a specific scope