Forward-deployed and implementer work that spans Implementation, Sandbox, Preview, and Production usually runs through Customer Central. This guide covers Manage Tenant Access plus the Object Transporter security Workday requires in every source and target. It complements the same-account-ID guide: matching account IDs are necessary for Configuration Catalog / OX, but access is still configured in two places.
- Checked against Workday on November 18, 2026
- Applies to Customer Central and Object Transporter
- 6 min read
Layer 1 — Manage Tenant Access
From Provide Tenant Access to Customer Central Users:
- Customer Central Users must have a valid, corresponding, active account in each tenant you grant.
- As a Customer Central Administrator, open Manage Tenant Access.
- Workday lists tenants enrolled in Customer Central; for each tenant, enter Users who need access.
- Match that user name to the individual’s account ID in other tenants. Workday: To use Configuration Catalog or Object Transporter, Customer Central requires that an individual have the same account ID across tenants.
- Customer Central administrators already have access to all tenants—do not add them here.
If a tenant was enrolled but does not appear, Workday directs you to a Production Support Request → Integration Tools → Customer Central case so EMS tags can be checked.
Layer 2 — Object Transporter security in each tenant
From Configure Object Transporter Security Permissions, perform these steps in every source and target tenant you will use with OX:
- Create a user-based security group named Migration Administrator.
- On Maintain Permissions for Security Group, grant that group View and Modify, plus Get and Put, on:
- Special OX Web Services
- OX for Non-implementers
- Add the Customer Central Users who will migrate to that group.
- Run Activate Pending Security Policy Changes.
Workday notes that Special OX Web Services may show as Suspended - Inactive for current session until an Object Transporter session runs—that is expected.
Users who need to migrate with OX must already be in Migration Administrator in both source and target (also stated on the Manage Tenant Access page).
Recommended setup order
Workday’s Steps: Configure Access to Customer Central and Object Transporter sequences create accounts → enable Customer Central access to tenants → optional Production access/sessions → configure OX security permissions. Keep account IDs identical across Customer Central, source, and target for administrators and users who will migrate (security-admin account names follow Workday’s unique-name rule—see the same-account-ID guide).
Failure patterns
| Symptom | Likely gap |
|---|---|
| SymptomPerson missing from tenant menus in Customer Central | Likely gapNot listed in Manage Tenant Access, or no active matching account in that tenant |
| SymptomCatalog / OX blocked despite access | Likely gapAccount IDs differ across tenants |
| SymptomAccess granted but migrate fails on security | Likely gapNot in Migration Administrator in both source and target, or OX domain permissions incomplete |
Grant Manage Tenant Access per tenant, keep the same account ID everywhere OX runs, then finish Migration Administrator permissions in each source and target before the first Configuration Catalog or package migration.
Frequently asked questions
Does Manage Tenant Access replace Migration Administrator?
No. Manage Tenant Access grants Customer Central visibility to tenants. Object Transporter still requires Migration Administrator with OX domain permissions in both source and target.
Do Customer Central administrators need Manage Tenant Access entries?
Workday says Customer Central administrators already have access to all tenants—you do not add them on Manage Tenant Access.