---
title: "Why the same account ID across tenants unlocks Object…"
description: "Customer Central requires the same account ID across tenants for Configuration Catalog and OX. Security Admin IDs stay unique; Admins and Users must match."
url: https://kiweely.com/guides/workday-customer-central-same-account-id
---

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

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

To use **Configuration Catalog** or **Object Transporter**, Customer Central requires that an individual have the **same account ID across tenants**. Workday treats matching names as the same person: when you sign in to Customer Central, it attempts to authenticate to other tenants as that signed-in user.

Mismatched IDs are the silent reason someone can open Customer Central, see a tenant listed, and still cannot finish an OX migration.

## Matching vs unique: two different rules

| Role | Account ID rule | Suggested pattern (Workday) |
| --- | --- | --- |
|  **Customer Central Security Administrator** | Must be **unique** across tenants | `first.last-sec-admin` (implementer: `firstInitialLast-impl-sec-admin`) |
|  **Customer Central Administrator** | Must **match** source, Customer Central, and target | `first.last` (implementer: `firstInitialLast-impl`) |
|  **Customer Central User** | Must **match** source, Customer Central, and target | Same as Admin pattern |

Security Administrators manage a separate feature set (password rules, tooling access restrictions). Their uniqueness rule is intentional—do not “simplify” by reusing the Implementation login for that role.

## Access stack for a working migrator

1.  **Same account ID** on Customer Central, source, and target.
2.  **Active** corresponding account on every tenant you grant.
3.  **Migration Administrator** user-based security group on **both** source and target (**Create Security Group**, then **Maintain Permissions for Security Group** with View/Modify and Get/Put on **Special OX Web Services** and **OX for Non-implementers**; **Activate Pending Security Policy Changes**). Suspended status on Special OX Web Services until an OX session is normal.
4.  **Manage Tenant Access** in Customer Central: add the user on each non-admin grant. Central Administrators already reach all tenants—you do not re-add them.

Without step 3, Manage Tenant Access alone does not make OX legal. Without step 1, catalog and OX refuse the identity link even when security groups look right.

## Decisions on day one of an engagement

-   **Standardize the implementer ID scheme** before creating Sandbox and Implementation accounts (for example always `jsmith-impl` everywhere except Security Admin).
-   **Never rename mid-project** without updating every tenant and re-checking Manage Tenant Access—OX will treat the old and new IDs as different people.
-   **Partners:** customer-owned Central Administrator backups should still follow the match rule if those people will ever run OX themselves.
-   **Production OX:** same identity and Migration Administrator rules apply after Production access is enabled.

If OX or catalog access fails after security looks correct, compare the literal account ID strings across Customer Central and the target before debugging packages. Same ID is a hard product requirement, not a naming preference.

## Frequently asked questions

### Why can I see a tenant in Customer Central but OX still fails for a user?

Manage Tenant Access alone is not enough. The person needs a matching account ID on that tenant, an active account there, and—for OX—membership in the Migration Administrator security group on both source and target.

### Should Security Administrator use the same ID as Implementation?

No. Workday requires the Customer Central Security Administrator username to be unique versus other tenants. Use a distinct pattern such as first.last-sec-admin.

### What permissions does Migration Administrator need?

On each source and target tenant, create the user-based Migration Administrator group and grant View/Modify and Get/Put on Special OX Web Services and OX for Non-implementers, then Activate Pending Security Policy Changes.

## 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)
-   [Concept: Customer Central Account Naming Conventions](https://doc.workday.com/admin-guide/en-us/manage-workday/tenant-configuration/implementation-tools/customer-central/set-up-customer-central-accounts/mym1553527265572.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)
-   [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)

## Related guides

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

-   [### What Workday’s Deployment Agent Can and Cannot Do in Your Tenant Workday’s ASOR-enabled Deployment Agent reads tenant configuration in Implementation, Sandbox, Preview and Customer Central. It doesn’t run in Production, and edits configuration only in partner early access. Workday publishes no price; the Rate Card meters 5 credits per Ask interaction.](https://kiweely.com/guides/workday-deployment-agent-tenant-inspection)
-   [### Workday Object Transporter (OX) Errors: Prerequisites, Diffs, and What Moves Object Transporter runs a four-stage sequence before moving configuration between Workday tenants: error check, prerequisite check, pre-migration diff report, and migration. Here is how to fix missing Reference IDs, handle the 50-prerequisite cap, and choose Merge vs. Override for security.](https://kiweely.com/guides/workday-object-transporter-errors)
-   [### What are the types of tenant in Workday? Sandbox, Sandbox Preview, Implementation and Production compared Most Workday customers get four tenants: Production, Sandbox, Sandbox Preview and Customer Central. Implementation and demonstration tenants cost extra. Sandbox refreshes weekly from Production, Preview twice a year, Implementation on demand.](https://kiweely.com/guides/workday-tenant-types)

### More guides on Integrations and APIs

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

-   [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 Workday Customer Central is (and isn’t) for implementers](https://kiweely.com/guides/workday-customer-central-for-implementers)
-   [Object Transporter migration workflow: pre-check, first 50, merge vs override](https://kiweely.com/guides/workday-object-transporter-migration-workflow)
-   [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)

### From the blog on Integrations and APIs

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

-   [Why Shared Integration System Users (ISUs) Are a Security Risk for Employee AI Chatbots](https://kiweely.com/blog/why-integration-system-users-are-dangerous-for-workday-ai)
-   [Mapping Microsoft Teams, Slack, DingTalk, and Lark Identities to Workday Worker OAuth](https://kiweely.com/blog/mapping-teams-slack-lark-sso-identities-to-workday-workers)
-   [How Workday’s Twice-Yearly Releases Break In-House MCP Servers and REST Integrations](https://kiweely.com/blog/how-workday-twice-yearly-releases-break-custom-mcp-servers)

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