---
title: "Workday Agent Management Hub Skills & ASOR Prerequisites"
description: "Why multiple .agentskill files deployed from App Builder show as a single skill in Agent Management Hub, how to activate them, and ASOR tenant prerequisites."
url: https://kiweely.com/guides/workday-agent-management-hub-skills-not-showing
---

# Why Custom Agent Skills Deployed From the Developer Site Don’t Appear in Agent Management Hub, and ASOR Tenant Prerequisites

When you deploy a Custom Agent with multiple .agentskill files from App Builder, Workday’s Agent System of Record packages all of their tools into a single combined skill registration that starts disabled. Learn how to enable and sync skills in Agent Management Hub and verify ASOR prerequisites.

-   **Checked** against Workday on November 6
-   Applies to **Workday Extend**
-   4 min read
-   Published November 6
-   By Kiweely

## Why four `.agentskill` files in App Builder appear as a single skill in Agent Management Hub

When you define multiple `.agentskill` files on a Custom Agent in App Builder—for example, `create-equipment-request.agentskill`, `find-equipment-request.agentskill`, `edit-equipment-request.agentskill`, and `view-equipment-request.agentskill` referenced under `skills:` in your `.agent` file—and click **Save and Deploy**, opening the agent inside your tenant’s **Agent Management Hub** shows only **one** skill row containing the aggregated list of all tools across all four `.agentskill` files.

This is expected platform behavior, not a failed deployment. As documented in Workday’s Custom Agent architecture (*Custom Agents on Workday’s AI Platform*):

-   An agent in App Builder can have multiple `.agentskill` files to modularize instructions, steps, and `allowed-tools` for the language model at runtime.
-   When you deploy the agent, the **Agent System of Record (ASOR)** automatically registers the agent and **aggregates all tools (`tool-wids`) across every `.agentskill` file attached to that `.agent` into a single combined Skill registration** in ASOR.
-   At runtime, the Workday agent runtime still reads your individual `.agent` and `.agentskill` files from App Hub to guide the model’s step-by-step reasoning, while ASOR governs user access and tool authorization through that single combined skill entry.

## Activating and syncing deployed Custom Agent skills in the tenant

Deploying an agent from App Builder pushes the artifacts to App Hub, but the agent and its skills remain inactive and invisible to end users in Workday Chat until you enable them in ASOR:

1.  **In a Development tenant:**
    1.  Open the **Agent Management Hub** report and select the **Agent Registry** tab.
    2.  Click your Custom Agent’s name and select **Configure Agent**.
    3.  On the **Agent Skill** row, switch the **Status** toggle to enabled.
    4.  In the **Available To** prompt, select the security groups (for example, *Employee as Self*) that are allowed to invoke the agent.
    5.  Check **Confirm**, click **OK**, and then click **Activate Agent** on the agent profile.
2.  **In higher environments (Implementation or Sandbox) or after promoting updates:** In non-Development environments, promoting the app does not automatically push updated `.agentskill` tool lists into ASOR. You must trigger the ASOR sync from **App Manager**:
    1.  Open **App Manager** in the target Workday tenant.
    2.  Click **Configure** on your Agent app (or Extend app containing the Custom Agent).
    3.  On the **Configuration** tab of the App Details page, click **Update Agents** inside the **Agent** card to register or refresh the agent definition in ASOR.
    4.  In the **Update Extend Agents** pop-up, select the **Confirm** check box and click **OK**, then return to **Agent Management Hub** > **Configure Agent** to verify the skill’s **Status** and **Available To** security groups.

Also inspect every entry under `tool-wids` in your `.agentskill` files in **Code Mode**: a leading, trailing, or embedded space inside any 32-character `wid` causes ASOR to silently skip registering that tool.

## ASOR tenant prerequisites when `Agent Management Hub` is inaccessible

If you grant yourself all ASOR security domains in a tenant and still cannot open **Agent Management Hub** or register agents, check the three layers required for ASOR access:

### 1\. Required ASOR and System security domains

Ensure your security group holds permissions on these domains in the **Agent System of Record** functional area (plus **Activate Pending Security Policy Changes**):

-   *Agent Management Hub* (view the **Agent Management Hub** and **Find Unregistered Workday Agents** reports)
-   *Manage: Agents* (run **Configure Agent**, **Activate Agent**, **Deactivate Agent**, and **View Security for Agent Skill**)
-   *Setup: Agents* (register agents and query `/asor/v1/agentResourceSearch`)
-   *Agent Compliance* and *Reports: Agent Reporting* (view compliance and session analytics)
-   *Reports: AI Agent Security* and *Set Up: Tenant Setup - Security* in the **System** functional area

### 2\. Tenant enablement, UMSA, and Innovation Services

Domain permissions alone do not turn on the Agent System of Record runtime if the tenant itself has not been provisioned for Workday AI / ASOR:

-   **Subscription Service Agreement (UMSA vs. MSA):** Check your organization’s agreement on Workday Community (**Profile** > organization name > **Subscription Service Agreement**). Customers on the **Universal Main Service Agreement (UMSA)** have AI features enabled without Innovation Services tasks. Customers on the **Main Service Agreement (MSA)** must enable Innovation Services and Machine Learning data contributions. While self-built agents in non-Production tenants do not require a signed UMSA, **Workday-built agents** require UMSA in both non-Production and Production tenants (plus Workday Flex Credits).
-   **Development tenant provisioning:** If **Agent Management Hub** remains unavailable in a Development tenant after activating all domain security policy changes, contact your Workday Customer Success Manager (CSM) or open a Workday Support case to verify that ASOR and Extend AI tenant provisioning are enabled on that environment.

### 3\. Can you add custom skills to Workday-delivered agents?

You cannot attach custom `.agentskill` files directly to a first-party Workday-built agent (such as the **Self-Service Agent**); on a Workday-delivered agent, administrators can only enable or disable the skills Workday delivers. To add custom business logic alongside the Self-Service Agent, build a **Custom Agent** in App Builder (with Agent-Ready Tools and Custom Agent Action orchestrations); once activated in ASOR, your Custom Agent becomes discoverable inside the Workday Self-Service Agent chat panel and Sana.

## Verifying the configuration in your tenant

Open **Agent Management Hub** > **Agent Registry**, select your Custom Agent, and confirm its status is **Active** and the skill row shows **Enabled** with your target security groups in **Available To**. Click **View Security** on the **Skills** tab to run **View Security for Agent Skill**, verifying that all tools aggregated from your `.agentskill` files appear in the list and show no **Config Required** gaps.

## Sources checked

-   [Custom Agents on Workday's AI Platform](https://developer.workday.com/documentation/GUID-c3910467-0fd6-4f27-b78e-436cfe0a3147-enHYPHENus)
-   [Build and Deploy Custom Agents](https://developer.workday.com/documentation/GUID-c2e04f80-557a-4968-8957-9f1210156908-enHYPHENus)
-   [About Workday Agents](https://developer.workday.com/documentation/GUID-0e960e10-8a0f-4975-afc6-83ab303ed485-enHYPHENus)
-   [Register External Agents](https://developer.workday.com/documentation/GUID-267aee04-5657-4f75-9ddb-95a657f43d75)
-   [Sample Artifacts](https://developer.workday.com/documentation/GUID-7e74bb3c-7459-4516-bda7-abe03b7aa456-enHYPHENus)

## Related guides

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

-   [### Why a Workday Custom Agent Has No Credentials Tab in Agent Management Hub, and How to Expose It Through A2A Workday displays the Credentials tab in Agent Management Hub only for registered External Agents. To expose a Custom Agent built on Workday’s AI platform to an external assistant, register a third-party Agent Definition in the Agent System of Record that wraps the Custom Agent WID as an A2A tool.](https://kiweely.com/guides/workday-custom-agent-missing-credentials-tab-a2a)
-   [### Passing Large CSV File Attachments From a Workday Custom Agent Flow to Orchestrate Without Hitting Context Limits Passing a multi-thousand-row CSV directly through a Custom Agent Action JSON input forces the LLM to serialize the entire file inside its context window. Store the uploaded CSV in an Extend Attachment Business Object via a PMD fileUploader widget and pass only the Attachment WID to Orchestrate.](https://kiweely.com/guides/workday-custom-agent-csv-file-attachment-orchestrate)
-   [### Preventing Duplicate Initiate\_Change\_Job Business Process Events When a Workday Custom Agent Calls a Write Tool When a Custom Agent write tool calls Initiate\_Change\_Job without returning a clear Change Job business process WID in its response payload, the LLM assumes the call did not produce a WID and retries. Return the explicit event WID, set Destructive annotations, and check for in-progress events.](https://kiweely.com/guides/workday-custom-agent-duplicate-initiate-change-job)
-   [### Why Custom Agent Actions Fail With S22 Permission Denied or Task Not Authorized in Agent Chat Orchestration Builder runs Custom Agent Actions directly as your user, whereas Agent Chat enforces dual ASOR authorization and restricts the Agent System User token to the resources listed in your .agentskill file. Register every REST, SOAP, and WQL resource WID via the Finder API to fix it.](https://kiweely.com/guides/workday-custom-agent-actions-permission-denied-tool-wids)

### More guides on Custom agents and Workday AI

[All 91 guides](https://kiweely.com/guides#custom-agents)

-   [Fixing Workday Developer Agent VS Code Sign-In With a Personal Developer Account and Subagent Interrupt Errors](https://kiweely.com/guides/workday-developer-agent-vscode-personal-account-login)
-   [Finding Workday tool IDs with the Agent Resource Search (finder) API](https://kiweely.com/guides/workday-finder-api-tool-discovery)
-   [Connecting an Extend app to the Workday Self-Service Agent and Microsoft Teams](https://kiweely.com/guides/workday-extend-self-service-agent-teams)
-   [How to build a chatbot in Workday Extend](https://kiweely.com/guides/workday-extend-chatbot)
-   [How to call AI Gateway Document Intelligence from a Workday Extend app](https://kiweely.com/guides/workday-extend-ai-gateway-document-intelligence)
-   [Who gets Workday Developer Agent, and what it uses in Flex Credits](https://kiweely.com/guides/workday-developer-agent-access-flex-credits)
-   [Connecting a Workday custom agent to an outside agent platform with A2A](https://kiweely.com/guides/workday-custom-agents-a2a-external-agents)
-   [Why Workday custom agents use up Flex Credits so quickly](https://kiweely.com/guides/workday-custom-agent-usage-limits)

### From the blog on Custom agents and Workday AI

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

-   [Insurance and MSA Language for AI Agents That Touch Workday](https://kiweely.com/blog/insurance-msa-language-ai-agents-workday)
-   [Load and Concurrency: When AI UI Agents Are the Wrong Tool for Workday](https://kiweely.com/blog/when-ai-ui-agents-wrong-tool-workday-load-concurrency)
-   [Migrating a Workday Extend App from Hand-Edited JSON to an Agent-Maintained Repo](https://kiweely.com/blog/migrate-extend-app-to-agent-maintained-repo)

## Let Workday check the work.

Kiweely writes WQL and builds orchestrations in your own tenant, and Workday, not Kiweely, says whether they passed.

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

## Get the next guide in your inbox.

One email a month with new guides and one Extend tip. Nothing else.
