Skip to content
KiweelyKiweelyKiweely

Holding Companies with More Than One Workday Tenant: One Bridge Policy or Many?

Workday separates tenants by URL and database. Kiweely Bridge, coming next, prices one plan per company and includes that company’s Production and non-production tenants. It does not say one tool policy is copied across every production tenant in a holding company.

  • By Kiweely
  • 4 min read
On this page
Holding Companies with More Than One Workday Tenant: One Bridge Policy or Many?

Many policies. One commercial plan only where the published pricing page is actually talking about one company.

Workday’s tenant primer defines a tenant as a unique instance. The database segregates data. Each tenant has its own URL, and you configure it for that business. A holding company that runs two production tenants is running two Workday databases. Security groups, domain policies, API clients, and audit history do not cross the URL.

Kiweely Bridge is coming next. Read the pricing sentence narrowly. It is one plan per company, by the employees that company licenses in Workday. A plan includes Production and every non-production tenant (Sandbox, Sandbox Preview, and implementation tenants). A company still implementing Workday pays its band for its implementation tenants. None of those sentences say that a parent company’s tool allow-list is automatically the policy of every subsidiary production tenant.

What is per tenant, whether or not you buy Bridge

Object Scope Workday documents
ObjectPeople, pay, positions Scope Workday documentsThe tenant’s database. Sandbox is typically a copy of that production tenant, not of a sister company
ObjectSecurity groups and domains Scope Workday documentsConfigured in the tenant. An HR Partner assignment in one tenant is not an assignment in another
ObjectAPI client Scope Workday documentsRegistered in the tenant whose URL the user signs in on
ObjectAudit Scope Workday documentsReports such as Update Audit and View Worker History run in that tenant
ObjectAgent registry, if you use Workday’s agents Scope Workday documentsAgent Management Hub is a tenant setup. Sandbox refresh behavior is described per tenant, not across a group

Pointing one assistant connection at the wrong host answers from the wrong workforce. That is true for a shared integration user and for a user-delegated grant. The worker can only sign in where they have an account.

What Bridge’s pages commit to

Decision Published Bridge position
DecisionTool list, field redaction, which writes exist Published Bridge positionAdmin policy, tested as real roles, then published. Disabled writes are absent from the tool list
DecisionWho the call runs as Published Bridge positionThe worker who signed in, on that tenant
DecisionWhich environments one plan includes Published Bridge positionProduction and the non-production tenants of that company
DecisionPrice Published Bridge position$499, $1,499, or $3,999 per month by the 1,000 / 5,000 / 20,000 employee bands. Above 20,000 is a quote. One person on their own developer tenant is free
DecisionA holding company with two production tenants and two licensed populations Published Bridge positionNot given a combining rule on the pricing page

So the operating rule, until a quote says otherwise, is:

  • One Workday policy per production tenant. Register the API client there. Choose tools and fields there. Test Employee, Manager, and HR Partner there. Audit there.
  • Sandboxes follow that production tenant, and they are included in the company plan. They are not a place to borrow another subsidiary’s workers. Sandbox data is typically a copy of production, so a demo can still show real people. Use a sample-data tenant when the audience must not see them. That split is covered in the companion guide on production and sandbox endpoints.
  • Do not add the licensed headcount of two companies together and pick a band, unless Kiweely’s quote says the commercial “company” is the parent. The page prices the employees you license in Workday for that company. It does not publish a roll-up formula.

Dedicated static IP and self-hosted container are enterprise quotes. A holding company that wants one outbound address per subsidiary, or a container inside each network, is in that quote, not in the $499 band’s small print.

A simple map

Shape Policies Plan
ShapeOne production tenant, plus sandbox and implementation PoliciesOne production policy. Non-production is included and should still use its own client and URL PlanOne company band
ShapeTwo production tenants, two workforces, one parent brand PoliciesTwo policies. Security cannot be shared by wish PlanNot specified. Ask when you register interest
ShapeConsultants hopping among clients PoliciesOut of scope for a Bridge company plan. That work is Kiweely Vine, which is the desktop product for builders PlanNot a Bridge band

Frequently asked questions

Can one OAuth client registered in the parent tenant read the subsidiary tenant?

No. The client belongs to the tenant where it was registered, and the worker signs in on that tenant’s URL. A second production tenant needs its own client and its own sign-in.

Will subsidiary employees see the parent tool list?

Only if they use a connector whose admin published that list and they sign in to that tenant. Bridge does not publish a group-wide policy inheritance. It is coming next, and the safe assumption is one governed tenant at a time.

Register interest and say how many production tenants you have. The bands alone do not answer a holding company.

Your Workday work, done by AI.

Kiweely Vine is the AI agent that builds, deploys and tests Extend apps as real people, makes changes in any Workday task screen, answers from your real tenant and builds reports.

Get the next one in your inbox.

One email a month for Workday teams: what’s changing in Workday and what to retest, one tip tried in a real tenant, and what’s new at Kiweely.

We’ll email you once to confirm. Unsubscribe in one click from any issue.