Configuration Change Tracker security is four domains, not one. Workday separates people who may only manage their own changes (Restricted) from people who may manage others’ changes (global). Configure each tenant where users run Change Tracker.
Domain map
| User role | Domain | Permissions | What they can do |
|---|---|---|---|
| User roleSelf auditor | DomainManage: Configuration Change Management - Restricted | PermissionsView and Modify | What they can doAccess Change Tracker; view and create their own reports |
| User roleGlobal auditor | DomainConfiguration Change Management | PermissionsView and Modify | What they can doAccess Change Tracker; create their own reports; view others’ reports |
| User roleSelf packager | DomainManage: Configuration Change Management Migrations - Restricted | PermissionsView and Modify | What they can doCreate and edit their own Advanced configuration packages from Change Tracker |
| User roleGlobal packager | DomainManage: Configuration Change Management Migrations | PermissionsView and Modify | What they can doCreate and edit their own and others’ Advanced packages |
Workday’s security topic says Restricted domains are for self auditors or packagers, and domains without Restricted are for global auditors or packagers. Consider separate user-based security groups for the two populations, for example Configuration Change Tracker Self and Configuration Change Tracker Global.
Setup steps
- Sign on as a security administrator with the Security Configuration domain in the System functional area.
- Create Security Group for each population you need (self vs global).
- Maintain Permissions for Security Group. Add the domains from the table with View and Modify.
- To create Advanced packages, assign both an auditor domain and a packager domain to the same user. Workday states that requirement explicitly.
- To migrate Advanced packages, also configure Object Transporter security and Customer Central tooling access, including OX Migration: Full Object Coverage on Maintain Access to Customer Central Tooling.
- Repeat domain setup in every tenant where the user will run Change Tracker.
What each combination unlocks
| Auditor | Packager | Typical outcome |
|---|---|---|
| AuditorSelf | PackagerSelf | Typical outcomeOwn reports; own Advanced packages |
| AuditorGlobal | PackagerSelf | Typical outcomeCan read others’ reports; still packages only own Advanced packages |
| AuditorSelf | PackagerGlobal | Typical outcomeOwn reports; can edit others’ packages if your process allows that split |
| AuditorGlobal | PackagerGlobal | Typical outcomeFull Change Tracker report and package administration |
Migrating the package still requires Object Transporter rights beyond these four domains.
Naming and operations tips
- Put implementers who only ship their own Sandbox window on Restricted auditor + Restricted packager.
- Put migration leads who assemble multi-user packages on global auditor + global packager.
- Do not grant global packager to every auditor. Packaging others’ change lists is a wider blast radius than viewing reports.
- Previously run reports remain reachable from Migrating Configuration Changes / Configuration Change Tracker history for users who retain access.
Frequently asked questions
Is View enough without Modify?
Workday’s Configure Security table specifies View and Modify for each of the four roles. Follow that pairing.
Does Restricted block Object Transporter?
No. Restricted only scopes Change Tracker reports and Advanced package editing to the user’s own objects. Migration still needs separate OX and Customer Central tooling permissions.
Customer Central administrator account?
Configure Security for Configuration Change Tracker lists a Customer Central security administrator account among the prerequisites for the broader tooling setup. Tenant CCT domains are still maintained with Create Security Group and Maintain Permissions for Security Group inside each tenant.