Defining User Roles

The visitors of our virtual library can freely alter book information, delete books, or even add misinformation. Such unrestrained access can rapidly diminish the value and reliability of our platform. We need a system where users have distinct permissions, ensuring that content remains accurate, trustworthy, and valuable. In this lesson, we’ll define different roles in our virtual library.

In this lesson, we’ll define different roles in our virtual library and implement role-based access control into our virtual library, ensuring that every user action aligns with their designated privileges.

Role definition

In our virtual library, we distinguish between two critical user profiles. The first is the viewer, who can browse our extensive book catalog.

The second is the administrator. An administrator possesses all the capabilities of a viewer and expanded privileges, including creating, updating, and deleting book records.

Let’s define the enum representing these two profiles in the user.entity.ts file.