Export xml option is only available for admins. Can this export xml functionality be given to other users as well?Issue <!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: #000000; } span { font-size: 12pt; font-family: Lato; color: #000000; } h2 { font-size: 24pt; font-family: Lato; color: black; } h3 { font-size: 18pt; font-family: Lato; color: black; } h4 { font-size: 14pt; font-family: Lato; color: black; } a { font-size: 12pt; font-family: Lato; color: #00718F; } a:hover { font-size: 12pt; color: #024F69; } a:target { font-size: 12pt; color: #032D42; } a:visited { font-size: 12pt; color: #00718f; } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } You have observed that the 'Export to XML' option is only available for admins. Since you want to export reports or records, you would like to know if the "Export to XML" functionality will be given to other users like ITIL users. Release<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: #000000; } span { font-size: 12pt; font-family: Lato; color: #000000; } h2 { font-size: 24pt; font-family: Lato; color: black; } h3 { font-size: 18pt; font-family: Lato; color: black; } h4 { font-size: 14pt; font-family: Lato; color: black; } a { font-size: 12pt; font-family: Lato; color: #00718F; } a:hover { font-size: 12pt; color: #024F69; } a:target { font-size: 12pt; color: #032D42; } a:visited { font-size: 12pt; color: #00718f; } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } All Versions. Cause<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: #000000; } span { font-size: 12pt; font-family: Lato; color: #000000; } h2 { font-size: 24pt; font-family: Lato; color: black; } h3 { font-size: 18pt; font-family: Lato; color: black; } h4 { font-size: 14pt; font-family: Lato; color: black; } a { font-size: 12pt; font-family: Lato; color: #00718F; } a:hover { font-size: 12pt; color: #024F69; } a:target { font-size: 12pt; color: #032D42; } a:visited { font-size: 12pt; color: #00718f; } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } By default, the Export to XML functionality in ServiceNow is typically restricted to users with the admin role. You may question why the Export to XML feature in ServiceNow is restricted to admin users. --> Some processors like ExportUpdateSet explicitly check for the admin role in their scripts. This is a deliberate design choice to prevent unauthorized access to sensitive configuration data. --> Security and Data Integrity: Allowing non-admins to export this data could expose sensitive logic or enable unintended data manipulation since XML exports can include system-level metadata, such as: - Script includes - Business rules - ACLs - Update sets - Related lists and references --> The gs.hasRightsTo("ui/context_menu.export_xml/read", null) condition checks for internal rights, which are typically granted only to admins. These rights are not exposed in the UI and are enforced at the platform level. Drawbacks of Granting XML Export to Non-Admin Users: Risk AreaDetailsSecurity ExposureXML exports can include sensitive fields, such as internal IDs, system properties, and script logic. Non-admins might unintentionally or maliciously expose this data.Data Volume & PerformanceXML exports are not subject to the same export limits as CSV/Excel. Large exports (e.g., >10,000 records or attachments) can cause memory issues or node crashesBypassing ACLsXML exports may bypass field-level ACLs, allowing users to extract data they wouldn't normally see in the UIInconsistent BehaviorNon-admin users often face issues with dot-walked fields, related lists, or large datasets during export. For example, exports may truncate after 100 records or omit reference fieldsNo OOB ControlsThere is no out-of-box UI to manage export rights. Granting access requires modifying context menu conditions or processors, which can be risky and upgrade-unsafeAttachment HandlingExporting attachments via XML is technically possible but not supported for bulk operations. This can lead to incomplete exports or memory overloads Resolution<!-- /*NS Branding Styles*/ --> .ns-kb-css-body-editor-container { p { font-size: 12pt; font-family: Lato; color: #000000; } span { font-size: 12pt; font-family: Lato; color: #000000; } h2 { font-size: 24pt; font-family: Lato; color: black; } h3 { font-size: 18pt; font-family: Lato; color: black; } h4 { font-size: 14pt; font-family: Lato; color: black; } a { font-size: 12pt; font-family: Lato; color: #00718F; } a:hover { font-size: 12pt; color: #024F69; } a:target { font-size: 12pt; color: #032D42; } a:visited { font-size: 12pt; color: #00718f; } ul { font-size: 12pt; font-family: Lato; } li { font-size: 12pt; font-family: Lato; } img { display: ; max-width: ; width: ; height: ; } } Considering all these drawbacks, if your goal is to allow non-admins to export reports or data, a safer alternative is to use CSV/Excel exports with role-based ACLs. As per ServiceNow, it's not a recommended practice, and we can't provide an out-of-the-box solution considering the various security risks and drawbacks