Skip to content
KiweelyKiweelyKiweely

Who Can Publish an Employee Screen, and Who Can Only Request One

Leaf’s public page says an HRIS admin describes, tests, and publishes, and nothing goes live until you say so. It does not list a requester role. Until it does, treat publish as a named person’s action and keep requests in the description step.

  • By Kiweely
  • 2 min read
On this page

The risky moment is not the sentence that describes a screen. It is the publish that puts that screen on every phone. Those should not be the same permission for a company that has a shared services desk and a Workday security administrator.

Kiweely Leaf (coming next) says the HRIS admin describes the screen, tests it, and publishes it, and nothing reaches employees until you say so. A change you publish is what people see the next time they open the app. The public page does not describe an admin console, a requester role, or a matrix of who may publish and who may only file a request. Run the split as an operating rule, and ask for it as a product behavior on the interest form.

A rule you can keep before the console exists

Someone close to the work writes the request in plain language: who the screen is for, what they must be able to finish, and which Workday task they use today. They do not publish.

A named publisher, usually the HRIS administrator who already owns business process security, checks three things:

  1. The screen calls Workday as the signed-in worker, not as a shared integration user.
  2. The submit starts the business process you already run (open enrollment, expense report, life event, internal apply), tried in a non-production tenant.
  3. A worker outside the audience gets nothing they cannot already see in Workday.

Then that person publishes. Until they do, employees stay on the last published layout. If the new one is wrong, the publisher puts the previous description back. Two publishers on the same screen the same day will overwrite each other. Name one.

Requests can pile up from HR partners, payroll, and frontline operations. Publishing stays small. That is the same shape as Workday domain security: many people can ask, few people can activate a policy.

What not to improvise

Do not share the publisher’s Workday sign-in so a requester can “just try production.” The screen will run as that administrator and can show data the requester must not see. Do not let a requester publish to production because the non-production tenant was refreshing. Wait.

A console, when it exists, should record who requested and who published, without storing the worker data the screen displayed. Leaf’s storage line is layouts, branding, and tenant connection settings. An audit of publish actions fits that line. A copy of the payslip someone opened does not.

Write the first screens and the name of the publisher. Coming next, so the console is a request, not a control you have today.

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.