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 (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 |
|---|---|
| PieceWorker, pay, benefits, security | Where it livesThe customer’s Workday tenant |
| PieceWho may call Workday | Where it livesThat worker’s sign-in |
| PieceScreen layout and colors | Where it livesThat company’s Leaf space (coming next) |
| PiecePhone install | Where it livesKiweely Leaf, once, from the public stores |
| PieceA store app named for the PEO | Where it livesNot 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 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.