Role-Based Access Control (RBAC)

Roles implement Role-Based Access Control (RBAC), providing granular and flexible control over user permissions.

The RBAC (Role-Based Access Control) functionality in Fudo Enterprise allows system administrators to define precise roles with specific access permissions tailored to objects and operations. This enables the creation of roles designed for particular tasks, such as a role that grants permissions solely for user management—allowing the creation, editing, and deletion of users—without affecting other areas of the system.

Similarly, roles can be configured to manage other objects, such as Listeners, Pools, Servers, and Safes. Administrators can define role-based permissions for specific actions, including creating, modifying, exporting, deleting, or blocking these objects.

The access management mechanism supports both global and selective permissions. This means that a user can be granted access to view, modify, or delete all objects of a given type (e.g., Users, Accounts, or Servers) or only specific, selected objects. This flexibility ensures that access rights align with the organization’s security and operational requirements.

Note

To maintain compatibility with previous versions, six default roles—superadmin, admin, safes admin, operator, auditor, and session viewer—have been added. These roles can also be modified as needed.

• Transition to RBAC After Upgrade
  • Understanding Privileges and Capabilities
  • Predefined Roles as a Starting Point
• Creating Role
• Assigning Roles to Users
• Modifying Roles
• Deleting Roles
• Typical Role Scenarios and Required Privileges
  • Tab-Level Access Control Matrix
  • Dashboard Widgets Visibility
  • Sessions Tab Permissions
  • Downloads Tab Permissions
  • Safes Management
  • Discovery Tab Permissions
  • Access Request Permissions
  • Fudo Officer
  • Reports Tab Permissions