---
title: "Kiweely Leaf: custom employee screens for Workday"
description: "Host AI-built portals, approvals and dashboards outside Workday. Live pass-through with each employee’s Workday permissions and zero HR data stored."
url: https://kiweely.com/leaf
---

![Kiweely Leaf](https://kiweely.com/_assets/kiweely-leaf-logo.C15-eGqn.svg)Coming next

# Kiweely Leaf: Beyond Workday’s screens. Built by AI agents.

For the HRIS team inside your company: employee screens in your own design, on live Workday data, in the browser, in Microsoft Teams and on the phone. Kiweely Vine is for consultants.

Register interest See how it works

The same Time off app open in a desktop browser at the company’s own address: Paid Time Off, Sick and Floating Holiday balances, December 22 to 24 chosen on the month, Dana Whitfield as the approver and Send request.

The Time off app Kiweely Leaf built for Pacific Logistics, open in the Kiweely Leaf phone app. It shows 112 hours of Paid Time Off left, 40 hours of Sick and 8 of Floating Holiday, December 22 to 24 chosen on the month, Dana Whitfield as the approver and Send request.

## From one sentence to a live app.

Connect your tenant once with one Workday API client. Then describe what you need.

Step 1 of 5: Describe the screen. Say who it is for and what they need, the way you would tell a colleague. A walk-through of Kiweely Leaf.

**New screen** Draft

## Any screen your people wish Workday had.

In your brand, your languages and your layout, in the browser and on the phone.

Employee portals

Pay, time off, benefits and onboarding on one page, without Workday’s menus.

Approvals in chat

Leave, expense and timecard approvals in Teams, Slack, DingTalk or Lark.

Manager views

Headcount, open roles and who is out, for managers who rarely open Workday.

Frontline apps

Three big actions on a phone, in the worker’s own language.

## One app for your whole workforce.

This is the Kiweely Leaf phone app, not the Kiweely phone app for Vine and Nest. Your pages live in your company’s space inside it, so you build no phone app of your own.

1.  ### Install Kiweely Leaf once.
    
    Employees get it from the App Store or Google Play. Nothing of yours goes through a store review.
    
2.  ### Sign in with Workday.
    
    Single sign-on once, then a face or a fingerprint. Each person lands in your company’s space, with your name and colors.
    
3.  ### Open your company’s apps.
    
    Every screen Leaf builds, and any web app your developers host, is a tile. A change you publish is there the next time they open it.
    
4.  ### Answer from the notification.
    
    A private notification says something needs them. The details stay inside the app.
    

Pacific Logistics in the Kiweely Leaf phone app. Ana Ruiz’s request for 3 days off needs the manager’s answer, with Approve and Decline. Under it are the company’s apps: Time off, Pay and Onboarding built by Kiweely Leaf, and Shift swap built by the company’s IT team.

## Live from Workday. Nothing kept on our servers.

Your security team can sign off faster.

### Nothing stored.

Read on demand, gone when the request ends.

### Workday’s own permissions.

Every call runs as the signed-in employee.

### No Workday Extend license.

Standard Workday APIs from outside the tenant.

### Complete freedom over the UI.

Your brand, languages and layouts, no layout limits.

## How Kiweely Leaf compares.

Four ways organizations put a custom experience in front of Workday today, and where each stops.

Compare Kiweely Leaf with

   

How Kiweely Leaf compares with other ways to build screens for Workday
| Capability | Kiweely Leaf AI-built screens on live data | Workday Extend Apps inside the Workday tenant | HR portal suites Applaud, ServiceNow Employee Center | App builders Retool, Superblocks, Lovable | Employee chatbots Moveworks, Leena AI, Workday Everywhere |
| --- | --- | --- | --- | --- | --- |
| Built by HRIS admins in plain English | Kiweely Leaf Yes Agents inspect your tenant, wire the Workday APIs and host the screen. | Workday Extend Partly Needs developer tooling, PMD and AMD code, or Kiweely Vine to build inside Extend. | HR portal suites Partly No-code widgets inside preset templates, usually stood up by an implementation partner. | App builders Partly Lovable builds from prompts and Retool from components, but someone still wires Workday OAuth, WQL, RaaS and errors. | Employee chatbots Partly Admins configure chat topics and connectors, not custom screens. |
| Any custom web, mobile or chat layout | Kiweely Leaf Yes Full web freedom for browsers, the Kiweely Leaf phone app, DingTalk, Feishu, Lark and Microsoft Teams. | Workday Extend Partly Runs inside Workday, bound to Workday’s page components and navigation. | HR portal suites Partly Polished intranet pages and cards, bounded by the suite’s widget library. | App builders Yes Full web canvas, mostly designed around internal desktop tools. | Employee chatbots No Chat threads and compact approval cards only, not portals or dashboards. |
| Works without a Workday Extend license | Kiweely Leaf Yes Uses standard Workday REST, WQL, RaaS and business process APIs. | Workday Extend No Requires a commercial Workday Extend subscription. | HR portal suites Yes Connects over standard Workday APIs, behind its own enterprise contract. | App builders Yes Connects over HTTP to whichever Workday endpoints your engineers wire. | Employee chatbots Yes Connects over Workday APIs for supported chat actions. |
| Enforces each employee’s own Workday security | Kiweely Leaf Yes Every call runs live under the signed-in worker’s own Workday sign-in. | Workday Extend Yes Native inside Workday under the signed-in worker. | HR portal suites Partly Often queries through an integration user and rebuilds access rules in the portal. | App builders No Typically shares one service credential unless engineers build per-user Workday OAuth. | Employee chatbots Partly Maps chat users to workers, scoped to the bot’s integration permissions. |
| No employee HR data stored outside Workday | Kiweely Leaf Yes Reads and writes live, and stores only screen settings. | Workday Extend Yes Everything stays inside your Workday tenant. | HR portal suites Partly Commonly caches or indexes worker profiles, cases and content in its own cloud. | App builders Partly Possible, depending on how engineers set up logs and caching. | Employee chatbots No Stores conversation history and synced worker context to answer questions. |
| Launches without an engineering or SI project | Kiweely Leaf Yes Hosted by Kiweely; your HRIS admin describes the screen, tests it and publishes. | Workday Extend No Requires Extend development skills, tenant promotion steps and ongoing upkeep. | HR portal suites No Enterprise procurement followed by a multi-month portal rollout. | App builders No Requires full-stack engineers to build, secure and maintain every Workday integration. | Employee chatbots Partly Quick for preset questions, not for custom multi-step workflows. |

## Questions teams ask first.

Workday security, where the data goes, and how to start.

**Does Kiweely Leaf require a Workday Extend subscription?**

No. Kiweely Leaf runs outside Workday on Kiweely’s cloud and connects through the standard Workday APIs that come with your core tenant. If you already use Workday Extend and want apps inside Workday, Kiweely Vine builds those today.

**Do you store any of our employees’ Workday data on Kiweely servers?**

No. When an employee opens a screen or submits a form, Leaf calls Workday live and sends the result straight back to their browser. Kiweely stores only your app layouts, branding and tenant connection settings, never worker records, compensation or payroll data.

**How do employee sign-in and Workday security permissions work?**

Employees sign in with Workday, or through single sign-on inside DingTalk, Feishu, Lark or Microsoft Teams, matched to their Workday worker account. Every call uses that employee’s own short-lived sign-in, so Workday enforces the domain and business process permissions set in your tenant.

**Where can employees open the screens we build?**

In any desktop or phone browser under your company’s address, in the Kiweely Leaf phone app for iPhone and Android, or embedded as an internal workplace app inside DingTalk, Feishu, Lark, Microsoft Teams or Slack.

**Can our own developers build apps that employees open in the Kiweely Leaf phone app?**

Yes. Your company gets its own space in one Kiweely Leaf phone app on the App Store and Google Play. Employees install it once, sign in with Workday and see every app your company has published there, whether Leaf’s agents built it or your developers wrote it as a web app. Every Workday call still runs through Leaf under the employee’s own sign-in, so the same Workday permissions apply and no HR data is stored outside Workday.

**How is Kiweely Leaf different from Kiweely Vine and Kiweely Nest?**

Kiweely Vine is the desktop AI agent for Workday consultants and developers, live today. Kiweely Nest is your in-house AI HRIS team that looks after tickets, projects and routines across your tenants. Kiweely Leaf is the hosted UI layer your whole workforce opens when they need a cleaner screen than Workday’s own. The Kiweely phone app is the companion for Vine and Nest; employees use the separate Kiweely Leaf phone app.

**How do we get started with Kiweely Leaf?**

Tell us the screens your employees need first through the form below. We will reach out to connect your Workday tenant and set up your company’s space in the Kiweely Leaf phone app.

## Tell us what you want to build.

Share the screens your employees need first, and we will write to set up your company.
