---
title: "Configuration Change Tracker Restricted vs Global auditor…"
description: "Assign Restricted domains for self-only CCT users and non-Restricted domains for global auditors and packagers."
url: https://kiweely.com/guides/workday-cct-restricted-vs-global-packager-security
---

# Configuration Change Tracker Restricted vs Global auditor and packager

Workday splits Configuration Change Tracker access into Restricted (self) and global domains. Auditors need View and Modify on the Change Management domain. Packagers need the Migrations domain. A user who creates Advanced packages needs both an auditor and a packager domain.

-   **Checked** against Workday on November 17
-   Applies to **Workday Configuration Change Tracker**
-   3 min read
-   Published November 17
-   By Kiweely

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 |
| --- | --- | --- | --- |
| Self auditor | Manage: Configuration Change Management - Restricted | View and Modify | Access Change Tracker; view and create their own reports |
| Global auditor | Configuration Change Management | View and Modify | Access Change Tracker; create their own reports; view others’ reports |
| Self packager | Manage: Configuration Change Management Migrations - Restricted | View and Modify | Create and edit their own Advanced configuration packages from Change Tracker |
| Global packager | Manage: Configuration Change Management Migrations | View and Modify | Create 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

1.  Sign on as a security administrator with the Security Configuration domain in the System functional area.
2.  Create Security Group for each population you need (self vs global).
3.  Maintain Permissions for Security Group. Add the domains from the table with View and Modify.
4.  To create Advanced packages, assign both an auditor domain and a packager domain to the same user. Workday states that requirement explicitly.
5.  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.
6.  Repeat domain setup in every tenant where the user will run Change Tracker.

## What each combination unlocks

| Auditor | Packager | Typical outcome |
| --- | --- | --- |
| Self | Self | Own reports; own Advanced packages |
| Global | Self | Can read others’ reports; still packages only own Advanced packages |
| Self | Global | Own reports; can edit others’ packages if your process allows that split |
| Global | Global | Full 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.

## Sources checked

-   [Configure Security for Configuration Change Tracker](https://doc.workday.com/admin-guide/en-us/manage-workday/tenant-configuration/implementation-tools/customer-central/configuration-change-tracker/configure-configuration-change-tracker-security.html)
-   [Concept: Configuration Change Tracker](https://doc.workday.com/admin-guide/en-us/manage-workday/tenant-configuration/implementation-tools/customer-central/configuration-change-tracker/concept--configuration-change-tracker.html)
-   [Migrate Configuration Changes with Configuration Change Tracker](https://doc.workday.com/admin-guide/en-us/manage-workday/tenant-configuration/implementation-tools/customer-central/configuration-change-tracker/migrate-obect-changes-by-specific-users-and-timefr.html)

## Related guides

[All guides](https://kiweely.com/guides)

-   [### How do I build a Configuration Change Tracker package by user and time? Configuration Change Tracker builds a change list for selected users and a timeframe. Package Ready to Migrate instances as an Advanced configuration package, run blank reference ID and exception audits, then launch Object Transporter. Advanced packages migrate only what you selected.](https://kiweely.com/guides/workday-configuration-change-tracker-how-to)
-   [### How do I limit a Configuration Change Tracker package to a change window? Time-bounded CCT packages start with From Moment and To Moment, then Filtered by Users. Narrow further with New Instances Only or Modified Instances Only when you create the Advanced package. Advanced packages migrate only selected instances, so the window you choose is the window you ship.](https://kiweely.com/guides/workday-configuration-change-tracker-time-bounded-packages)
-   [### Object Transporter or Configuration Change Tracker: which moves Workday config? Object Transporter migrates configuration you select, with dependents on standard packages. Configuration Change Tracker builds a change list by user and time, then hands an Advanced package to OX without auto-adding extra dependents.](https://kiweely.com/guides/workday-object-transporter-vs-configuration-change-tracker)

### More guides on Business processes and security

[All 27 guides](https://kiweely.com/guides#business-processes)

-   [Test Rule says Yes but the Workday BP step still skips: processing-user security](https://kiweely.com/guides/workday-test-rule-vs-processing-user-security)
-   [Current vs Proposed fields in Workday condition rules](https://kiweely.com/guides/workday-condition-rules-current-vs-proposed)
-   [Review security group changes an AI assistant suggested in Workday](https://kiweely.com/guides/review-ai-workday-security-group-changes)
-   [Explain a Workday business process in plain language, then configure the rule](https://kiweely.com/guides/ai-workday-business-process-design-plain-language)
-   [Turn a requirements note into a Workday business process](https://kiweely.com/guides/ai-brd-to-workday-business-process-design)
-   [Benefits Life-Event Intake That Starts the Right Workday Process](https://kiweely.com/guides/benefits-life-event-intake-workday-business-process)
-   [How do I document Workday configuration and business processes from a live tenant?](https://kiweely.com/guides/document-workday-configuration-and-business-processes)
-   [How to Run Role-Boundary Security Tests Across Employee, Manager, and HR Partner Personas](https://kiweely.com/guides/workday-role-boundary-testing-employee-manager-hr-partner)

### From the blog on Business processes and security

[All posts](https://kiweely.com/blog)

-   [The CISO Checklist for Connecting Claude, ChatGPT, or Gemini to Workday](https://kiweely.com/blog/ciso-security-review-checklist-connecting-llms-to-workday)
-   [Using Face ID and Fingerprint Unlock with Workday Single Sign-On for Deskless Workers](https://kiweely.com/blog/biometric-face-id-fingerprint-reauth-for-workday-mobile-apps)
-   [Pass-Through Workday Screens vs. Caching HR Portals: Security and Sync Tradeoffs](https://kiweely.com/blog/pass-through-workday-ui-vs-caching-hr-portals)

## Let Workday check the work.

Kiweely writes WQL and builds orchestrations in your own tenant, and Workday, not Kiweely, says whether they passed.

[Start for free](https://kiweely.com/download) [See how it works](https://kiweely.com/vine/how-it-works)

## Get the next guide in your inbox.

One email a month with new guides and one Extend tip. Nothing else.
