---
title: "PEO and ASO Employee Apps on Each Customer's Workday Tenant"
description: "How a PEO or ASO can offer employee screens that sign in to each customer's own Workday tenant."
url: https://kiweely.com/blog/peo-aso-white-label-employee-apps-customer-tenants
---

# PEO and ASO Employee Apps on Each Customer’s Workday Tenant

Each customer tenant is its own Leaf connection and company space. Employees install the Kiweely Leaf app, then see that customer’s name and colors. The public page does not offer a PEO-branded store app or a shared login across customers.

-   By Kiweely
-   November 16
-   2 min read

A professional employer organization or an administrative-services organization lives in a hard place: clients expect a branded employee experience, and each client’s workers, pay, and security live in that client’s Workday tenant. The app cannot pool those tenants behind one integration user.

[Kiweely Leaf](https://kiweely.com/leaf) (coming next) connects a tenant with one Workday API client and gives that company a space. Employees install Kiweely Leaf from the App Store or Google Play, sign in with Workday, and land in the company’s space with that company’s name and colors. Screens call Workday as the signed-in worker. Layouts are stored. Worker records are not.

## What “white label” can mean here

It can mean the space shows the client’s name and colors, and the client’s HRIS admin (or the PEO acting with that client’s administrators) describes screens and publishes them for that tenant. It cannot mean, on the public page, a binary you submit to Apple or Google under the PEO’s name. “Nothing of yours goes through a store review” is the Leaf phone model: one Kiweely Leaf app, many company spaces.

It also cannot mean one sign-in that sees every client. A worker reaches Workday only through their own sign-in on their employer’s tenant. Pointing client A’s worker at client B’s tenant is a cross-customer breach, not a convenience feature. The product page does not describe a PEO console that holds client credentials. Each connection is that customer’s.

ASO arrangements where the client remains the Workday customer are the same shape. The tenant owner authorizes the API client. The space name should be the name employees expect, which is usually the client, not the ASO.

## What the PEO still owns

| Piece | Where it lives |
| --- | --- |
| Worker, pay, benefits, security | The customer’s Workday tenant |
| Who may call Workday | That worker’s sign-in |
| Screen layout and colors | That company’s Leaf space (coming next) |
| Phone install | Kiweely Leaf, once, from the public stores |
| A store app named for the PEO | Not in the public Leaf description |

Screens you repeat across clients (a time-off page, a day-one checklist) are still published per company, because the business processes and plan names differ by tenant. Copying a layout is a request you can make. Assuming the layout is correct on the next tenant without reading that tenant’s event types will file the wrong process. Leaf’s flow is to read the tenant you connected before the screen is designed.

There is no Leaf price on the public page. Commercial terms for a PEO with many customer tenants are a conversation, not a figure this article can invent.

[Write from the Leaf page](https://kiweely.com/leaf) with the number of customer tenants and the first screen each client needs. Coming next: none of those spaces exist until that setup is done.

## Read next

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

-   [November 16 ### Multi-Brand and Franchise Screens on One Workday Tenant](https://kiweely.com/blog/multi-brand-franchise-leaf-spaces-one-workday-tenant)
-   [November 16 ### Vine, Nest, Bridge, Leaf, and Roots: One Workday Tenant, Five Jobs](https://kiweely.com/blog/vine-nest-bridge-leaf-and-roots-one-workday-tenant)
-   [November 15 ### Codex for Workday Community Answers: Verify Against the Tenant Before Advising](https://kiweely.com/blog/codex-verify-workday-community-answers-in-tenant)

### More guides on Tenants and developer accounts

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

-   [Employee Screen Languages Without Changing the Tenant Default](https://kiweely.com/guides/localization-beyond-one-language-without-tenant-default)
-   [Accessing Employee Payslip Summaries and PDF Payslips Through Workday APIs](https://kiweely.com/guides/workday-payroll-payslip-summary-pdf-retrieval-apis)
-   [How Workday Stores Custom Plan Names, Reason Codes, and Translated Labels Across APIs](https://kiweely.com/guides/workday-custom-labels-translations-reading-tenant-terminology)
-   [Why Workday W-2 Box 1, 3, or 5 Wages Don’t Match Payroll Summary (and How to Fix Them)](https://kiweely.com/guides/workday-w2-box-mismatch-adjust-tax-balances)
-   [How to Customize the Workday Home Page, Daily Brief, and Global Navigation Sidebar](https://kiweely.com/guides/workday-configurable-home-page-daily-brief-setup)
-   [Workday Payroll Parallel Testing and Retro Calculation Audits in Sandbox](https://kiweely.com/guides/workday-payroll-parallel-testing-retro-audit)
-   [Workday Test Data: How to Build Realistic Data in a Sandbox or Implementation Tenant](https://kiweely.com/guides/workday-test-data-sandbox)
-   [How do I plan end-to-end and regression testing in Workday, and what does a test scenario cover?](https://kiweely.com/guides/workday-end-to-end-testing)

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

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

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