Clarification on Requirements for sn_rpa_fdn.rpa_admin Role Issue Customer would like to understand why the ITIL role is required/associated with the sn_rpa_fdn.rpa_admin role in the ServiceNow RPA Foundation application. Requested Information:-OOTB role composition for sn_rpa_fdn.rpa_admin-ITIL dependency justification-Recommended best practice for least-privilege access Release Not specific to any release Cause Resolution OOTB Role Composition - sn_rpa_fdn.rpa_admin Out-of-the-box, sn_rpa_fdn.rpa_admin directly contains the following roles (via role hierarchy, not conditional logic): Contained Roles and its Purpose itil - Base platform ITSM role (Incident, Problem, Change, Request tables)sn_rpa_fdn.rpa_user - Base RPA Foundation user accesscmdb_read - Read access to CMDB (CI lookups for automation/process context)fd_read - Field discovery read accessThis is a flat, direct containment - rpa_admin inherits each of these roles individually; there is no multi-level chain involved. ITIL Dependency - Business/Technical Justification The ITIL role is included with rpa_admin to support scenarios where RPA administration intersects with ITSM processes - for example, where automated processes or bots need to create, update, or act on Incident, Problem, Change, and Request records as part of the RPA workflow. Since these tables are governed by the platform's standard ITIL-scoped ACLs, an RPA admin needs the itil role to interact with them directly (e.g., reviewing or managing tickets tied to RPA process exceptions or automation requests).It's worth noting that this is inherited access via role hierarchy - RPA Foundation's own application logic does not explicitly enforce or check for the itil role anywhere. It is included so that RPA administrators who need to extend into ITSM-related work have that access available without requiring a separate role assignment. Recommended Best Practice - Least Privilege Our recommendation is to leave the OOTB role composition as-is for general use, since it reflects the standard supported configuration. That said, if your organization wants to enforce stricter least-privilege access: You can create a custom role (cloned from rpa_admin, minus the itil containment) and assign it to specific users who only need RPA administrative capability without ITSM table access.This should be scoped to individual users/groups on a case-by-case basis, based on whether they genuinely need to work with Incident/Problem/Change/Request records as part of their RPA responsibilities. Note: We'd recommend testing this in a sub-production instance first, to confirm no RPA Foundation workflows in your environment rely on the inherited itil access before rolling it out broadly.