Employees should not learn three versions of the same time-off or expense screen because one lives in a browser, one in Microsoft Teams, and one on a phone. Kiweely Leaf (coming next) is built so the screen you publish is the screen they open in those places. Workday Everywhere is a different product: Workday’s conversational self-service inside collaboration tools.
One Leaf layout, three places
The Leaf page says any employee experience, in your design, on live Workday data, in the browser, in Teams, and on the phone. The same page lists Slack, DingTalk, Feishu, and Lark as places a screen can be embedded, plus the Kiweely Leaf phone app from the App Store and Google Play. Your company’s space carries your name and colors. A change you publish is there the next time they open it. Developers’ own web apps can sit as tiles beside Leaf screens. Every Workday call still runs as the signed-in employee.
What the public page does not say: that a phone layout is pixel-identical to the desktop layout, or that a chat tab embeds the identical document object model. It says one published screen is available in those channels, and that you have freedom over the layout. Design the narrow phone case on purpose. Publish once. Employees install Leaf once; your screen does not go through a store review.
Sign-in is Workday OAuth for the browser and the phone, or single sign-on inside DingTalk, Feishu, Lark, or Microsoft Teams mapped to the worker. The call still uses that worker’s permissions.
Workday Everywhere is chat and quick actions inside Workday’s app
Workday Everywhere lets workers perform self-service from Gemini Enterprise, Microsoft 365 Copilot, Microsoft Teams, or Slack, using the Self-Service Agent. Workday recommends enabling that agent and its conversational skills. People can reach actions they already have in Workday. A manager can open team performance reviews there; a worker sees their own. You connect an implementation or production workspace to your tenant. Contingent workers can use it when you grant access; they cannot set it up. If the worker who installed it leaves, someone else needs Manage: Innovation Services.
Setup for Teams installs Workday as a third-party app, assigns it with a permission policy, and grants Microsoft Graph permissions so the app can manage itself, read users’ full profiles, and sign in and read the user profile. The Self-Service Agent setup uses one Workday app for Microsoft, shared by Copilot and Teams, and the same sign-in for both. Examples Workday gives are phrases such as “How much vacation time do I have?” and notifications when a worker requests time off.
Capabilities are guides (links into Workday tasks), notifications (an Approve button on a time-off card in Teams or Slack), and quick actions. Workday plans to retire Workday Assistant in 2027R2 and points people to the Self-Service Agent. By default Everywhere uses English unless the worker picks a language in Gemini Enterprise, Copilot, Teams, or Slack.
Security setup enables the Workday Everywhere functional area and the Workday Everywhere User domain. Workday also describes opt-in steps tied to a subscription agreement when you turn on Innovation Services and AI features. That agreement is Workday’s, for Workday’s agent. It is not a Leaf prerequisite. Leaf’s published answer is that it does not require a Workday Extend subscription and uses standard APIs on the core tenant.
| Leaf screen (coming next) | Workday Everywhere | |
|---|---|---|
| What the employee gets | Leaf screen (coming next)A page you designed | Workday EverywhereChat, links, notifications, quick actions |
| Where | Leaf screen (coming next)Browser, Leaf phone app, Teams, Slack, DingTalk, Feishu, Lark | Workday EverywhereTeams, Slack, Copilot, Gemini Enterprise |
| Who designs it | Leaf screen (coming next)Your HRIS admin describes it; you publish | Workday EverywhereWorkday’s skills and the tasks you already secured |
| Sign-in | Leaf screen (coming next)That worker’s Workday permissions | Workday EverywhereActions they can already perform in Workday |
| Extra Workday AI agreement | Leaf screen (coming next)Not required for Leaf, per the Leaf page | Workday EverywhereInnovation Services setup references Workday’s subscription steps |
Use Everywhere when a sentence and a notification are enough. Publish a Leaf screen when the task is a calendar, a multi-step form, or a phone page with a few large actions. Putting a custom election worksheet into Everywhere’s chat is the wrong tool. Rebuilding Workday’s time-off notification card as a second product is also the wrong tool if the card you want is the one Workday already delivers.
Register the screen and the channels on the Leaf page. Coming next: the screen is not in your tenant until that work is done.
Questions
Does embedding in Teams mean we installed Workday Everywhere?
No. Teams can host Workday’s app and, separately, an internal app your company embeds. Leaf’s embed is the second kind. Security, language defaults, and the Self-Service Agent belong to Everywhere only when you have set Everywhere up.
Do we maintain three codebases?
Leaf’s public description is one published screen opened from the browser, chat, and the phone app. You still design for a small phone. You do not register three API clients for the three channels. The page says you connect the tenant once.