To be a valid owner of a custom report, a user or Integration System User (ISU) must have the permission to modify it. This capability is controlled by the Custom Report Creation domain security policy. Granting the Integration System Security Group (ISSG) Modify access within the Report/Task Permissions table of this domain enables the associated ISU to create, edit, and therefore own custom reports. Without this Modify permission, the ISU is not considered a valid report writer and will not appear in the list of potential owners during a transfer.

B. Integration Permissions with Get access is for read-only web service operations (e.g., GetReports), not for managing report definitions.

C. View access in the Report/Task Permissions table only allows the ISU to run or view the report, not to edit or own it.

D. Integration Permissions with Put access is for web service write operations and is irrelevant to the task of managing report ownership within the Workday UI.

---

1. Workday Security Administration Documentation: The "Domain Security Policies" section explains that permissions for tasks and reports are configured in the Report/Task Permissions grid. The ability to create

edit

or delete an object (and thus be an owner) requires Modify access

whereas View access is for read-only purposes. The Integration Permissions grid is designated for controlling web service operations (Get/Put).

Reference: Workday Security Administration Guide

Chapter on "Domain Security Policies".

2. Workday Reporting and Analytics Training Manual: Course materials on custom reporting explicitly state that to create or edit a custom report

the user's security group must have Modify permission to the Custom Report Creation domain. This is a foundational requirement for any user

including an ISU

to be designated as a report writer or owner.

Reference: Workday Reporting & Analytics Courseware

Module on "Custom Report Security".

3. Workday Integrations Administration Documentation: When configuring an ISU for EIBs that use custom reports

the documentation specifies the required security. It highlights that for the ISU to own the report (a best practice)

its associated ISSG needs Modify access to the Custom Report Creation domain via the Report/Task Permissions policy.

Reference: Workday Integrations Administration Guide

Section on "Security for Integration System Users".