---
title: "Customer Central multi-tenant FDE access — Kiweely"
description: "Manage Tenant Access and OX security for multi-tenant FDE work in Customer Central."
url: https://kiweely.com/guides/multi-tenant-fde-customer-central-access
---

# Multi-Tenant FDE Access via Customer Central Manage Tenant Access

Customer Central Manage Tenant Access grants per-tenant users; Object Transporter still needs Migration Administrator and OX domain permissions in source and target.

-   **Checked** against Workday on November 18
-   Applies to **Customer Central and Object Transporter**
-   2 min read
-   Published November 18
-   By Kiweely

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**:

1.  Customer Central Users must have a valid, corresponding, **active** account in each tenant you grant.
2.  As a Customer Central Administrator, open **Manage Tenant Access**.
3.  Workday lists tenants enrolled in Customer Central; for each tenant, enter Users who need access.
4.  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.*
5.  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:

1.  Create a user-based security group named **Migration Administrator**.
2.  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**
3.  Add the Customer Central Users who will migrate to that group.
4.  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 |
| --- | --- |
| Person missing from tenant menus in Customer Central | Not listed in Manage Tenant Access, or no active matching account in that tenant |
| Catalog / OX blocked despite access | Account IDs differ across tenants |
| Access granted but migrate fails on security | Not 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.

## Sources checked

-   [Provide Tenant Access to Customer Central Users](https://doc.workday.com/admin-guide/en-us/manage-workday/tenant-configuration/implementation-tools/customer-central/set-up-customer-central-tenant-access/sxy1558446615573.html)
-   [Configure Object Transporter Security Permissions](https://doc.workday.com/admin-guide/en-us/manage-workday/tenant-configuration/implementation-tools/customer-central/object-transporter/loj1642437052331.html)
-   [Steps: Configure Access to Customer Central and Object Transporter](https://doc.workday.com/admin-guide/en-us/manage-workday/tenant-configuration/implementation-tools/customer-central/object-transporter/steps--configure-access-to-object-transporter.html)
-   [Steps: Set Up Customer Central Accounts](https://doc.workday.com/admin-guide/en-us/manage-workday/tenant-configuration/implementation-tools/customer-central/set-up-customer-central-accounts/xhv1558695752502.html)

## Related guides

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

-   [### Why the same account ID across tenants unlocks Object Transporter Configuration Catalog and Object Transporter require the same account ID on Customer Central, source, and target. Security Administrator names stay unique. Pair matching IDs with Migration Administrator on both tenants, then Manage Tenant Access.](https://kiweely.com/guides/workday-customer-central-same-account-id)
-   [### What Workday Customer Central is (and isn’t) for implementers Customer Central is a free separate tenant for Object Transporter and Configuration Catalog—not part of the Service, not Customer Data. Create Security and Central Administrator accounts with wd-tenantowner before that account deactivates at 60 days.](https://kiweely.com/guides/workday-customer-central-for-implementers)
-   [### Object Transporter migration workflow: pre-check, first 50, merge vs override Object Transporter blocks on source errors, then lists missing prerequisites—only the first 50 at a time. Clear Reference IDs or map instances, review the Pre-Migration Diff, pick Merge or Override for security policies, migrate, then use the Post-Migration Report or Tenant Compare.](https://kiweely.com/guides/workday-object-transporter-migration-workflow)
-   [### Workday Configuration Catalog packages: filter, test, then migrate Configuration Catalog groups Workday-provided content into packages you migrate with Object Transporter into Implementation or Sandbox at no cost. Filter by SKU or country, test thoroughly, and confirm regulatory fit before Production.](https://kiweely.com/guides/workday-configuration-catalog-packages)

### More guides on Integrations and APIs

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

-   [Configuration Catalog migrate blocked: fix the first 50 Object Transporter prerequisites](https://kiweely.com/guides/configuration-catalog-prerequisites-blocking)
-   [Tenant Compare after Object Transporter: when and how to run it](https://kiweely.com/guides/workday-tenant-compare-after-migration)
-   [How to find what Object Transporter can migrate](https://kiweely.com/guides/workday-object-transporter-supported-objects)
-   [Permission to launch a Workday integration: which domains Studio checks](https://kiweely.com/guides/permission-to-launch-workday-integration)
-   [What does Workday Studio “Content is not allowed in prolog” mean?](https://kiweely.com/guides/workday-studio-content-is-not-allowed-in-prolog)
-   [Why does Workday RaaS time out for non-admin users but work for admins?](https://kiweely.com/guides/workday-raas-timeout-non-admin-user)
-   [Why does a custom object update return 403 with escaped HTML in the body?](https://kiweely.com/guides/workday-custom-object-patch-403-escaped-html)
-   [Why does Create WCP API Client return 409 for an ISU?](https://kiweely.com/guides/workday-create-api-client-409-isu-already-has-client)

### From the blog on Integrations and APIs

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

-   [How to Reconcile Workday Payroll Feeds in Studio Without Days of Manual XML Diffs](https://kiweely.com/blog/reconciling-workday-payroll-studio-feeds-with-ai)
-   [Turning a Messy Client Spreadsheet into a Clean Workday EIB Load in One Conversation](https://kiweely.com/blog/messy-spreadsheet-to-workday-eib-load-with-ai)
-   [Workday REST API vs. SOAP Web Services: Why Setup Work Still Needs the Task Screen](https://kiweely.com/blog/workday-rest-api-vs-soap-coverage-gaps)

## 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.
