Create a Role
This page explains how to create a new Role in Revvy to define permissions and control access across users and groups.
Overview
Creating a role allows administrators to define a set of permissions that can later be assigned to groups. By designing roles carefully, you can enforce standardized access patterns across your organization and keep your RBAC (Role-Based Access Control) model clean and scalable.
Roles can define:
License type (Full access or Read-only)
Common permissions such as pipeline execution or pull request contributions
Org-level permissions like Retrieve, Validate, and Deploy actions for specific Salesforce orgs
Steps to Create a Role
Navigate to the Roles page at https://global.revvy.io/roles.
Click Create in the top-right corner.
In the Create Role form:
Name: Enter a unique name for the role (e.g., ReleaseManager).
Description: Add a clear description of the role’s purpose.
Under the DevOps tab, configure permissions:
License: Choose Full access or Read-only.
Common permissions:
Pipelines → Pipeline executions or Manage & Execute pipelines
Pull Requests → Read (View only) or Contribute (Create and Comment)
Org permissions:
Click Add Organizations to select Salesforce orgs.
For each org, choose allowed actions: Retrieve, Validate, Deploy.
Review all selections carefully.
Click Create to finalize the role.
Example
For a Release Manager role, you may:
Set License → Full access
Allow Pipelines → Manage & Execute
Allow Pull Requests → Contribute
Add only staging/production orgs with Validate and Deploy permissions
Best Practices
Use descriptive names – e.g., SystemAdministrator, ReleaseManager, QAReviewer.
Start with least privilege – only assign higher permissions when needed.
Align with team functions – map roles to responsibilities (Dev, QA, Admin).
Audit regularly – review role definitions as your org landscape evolves.
Last updated
Was this helpful?
