Articles on: Role Based Permissions (RBP)

RBP Reports

The RBP Reports module in CodeBot is a reverse-only module that works with a connected RBP workbook to extract and audit Role-Based Permissions (RBP) data from the system. The RBP Reports module only reads and audits existing RBP configurations and generates report outputs based on the filters defined in the RBP Config sheet. This KBA explains how the RBP Config sheet works and how each section controls report generation.


RBP Config Sheet – Section Breakdown


The configuration sheet is divided into multiple sections:


Audit Field Configuration


  • The Audit Field ID column defines a field to be evaluated during the audit. For example, a value like CUSTOM15 may represent a field such as Country or another employee-related attribute.


  • The Audit Field Value – Employee Belongs To column specifies the value that must match within that field. For instance, if CUSTOM15 corresponds to Country, the value could be USA. During execution, the system filters and extracts records where the selected field matches the defined value.


  • The “Fetch Audit Roles Filter Type” determines how role names are matched. For example, selecting “Fetch All That Contains” ensures that all roles containing a specific keyword (such as “HR”) are included in the audit.


  • Additional refinement can be applied using “Audit Filter Field ID” and “Audit Filter Value,” which allow filtering based on specific permission attributes within the selected roles. Similarly, “Fetch Audit Groups Filter Type” controls how groups are evaluated during the audit. If set to “Fetch All,” all relevant groups are included; otherwise, specific groups can be defined for selective auditing.



Role Permission Audit


  • The RBP Config sheet also allows date-based audit filtering. The “Role Permission Audit of Day(s)” field allows to define a numeric value representing the audit duration in days. A specific audit window can be defined using the “Role Permission Audit Start Date” and “Role Permission Audit End Date” fields. When these dates are provided, the system extracts role and permission changes that occurred within that timeframe.




User Permission


  • The “Select User Name” fields allow the audit to be executed from a specific user perspective. When usernames are entered, CodeBot evaluates permissions as assigned to those users. This helps validate effective access and detect discrepancies between role configuration and actual user permissions. If these fields are left blank, the audit runs purely at the role level without user-specific validation.



End-to-End Execution Flow


  • When execution begins, CodeBot reads all configured parameters from the RBP Config sheet. It applies audit field filters, and date filters as defined. It then connects to the RBP connected sheet and extracts the structured data accordingly.


  • The results are populated into the RBP Report worksheets such as:

 

Roles Audit by Country 1




Role Permissions Audit



User Permission



The RBP Config sheet acts as the control center for the RBP Reports module. By defining the audit parameters and date ranges, user can generate highly targeted and compliant RBP audit reports.


Note: If anything doesn’t appear as expected, check CodeBot execution logs and send us the Tracking Request ID via the chat box in the lower right-hand corner.

 

Thank you!


Updated on: 24/02/2026

Was this article helpful?

Share your feedback

Cancel

Thank you!