Role Overview

This page introduces the concept of Roles in Revvy and explains their purpose in the Role-Based Access Control (RBAC) model.

Overview

Roles in Revvy define the permissions and access levels that can be assigned to users through groups. Instead of directly granting permissions to individual users, administrators create roles that represent a set of privileges aligned to a specific responsibility, such as System Administrator.

This layered model ensures governance, scalability, and consistency across the platform. By assigning roles to groups, and groups to users, Revvy enforces permissions in a structured way that supports both small teams and enterprise environments.

Roles Page

You can view all roles from the Roles page at https://global.revvy.io/roles.

The Roles page displays:

• Role name – A unique identifier for the role.

• Description – A summary of the permissions and intended use.

• Created/Updated timestamps – When the role was created and last modified.

From this page, administrators can:

• Create new roles

• Edit existing roles

• Delete roles that are no longer needed

This makes the Roles page the central hub for permission configuration in Revvy.

Why Roles Matter

• Centralized control – Manage permissions in one place.

• Least privilege enforcement – Only grant users what they need.

• Scalability – Add or update roles as team structures evolve.

• Compliance – Maintain auditable, consistent access policies.