I want to know how to add a button to a Workspace using UI Builder.

[t-takumi]

Right now, I edited an existing OOTB “Publish” UI Action and changed the settings (added a Workspace Form Button/Form Menu as shown in the screenshot).
However, the button did not appear in the Workspace.

Therefore, I tried using UI Builder, but I’m not sure how to use it.
These are the points I don’t understand:

• What is a “variant”? After creating a variant, will it automatically be applied without further configuration?
• What are the steps to add a button created with a UI Action?

[AllambaiN448493]

Hi @t-takumi 
To add any buttons in the Workspace we have to navigate to 
Declarative actions > Form actions 

you can check there if it was helpful please hit 👍

[Dr Atul - LNG]

Hi @t-takumi 

To see the Publish button, a user must have either the knowledge_manager or knowledge_admin role. If you don’t have one of these roles, you won’t be able to publish the article. Out‑of‑the‑box, the button is available — the only dependency is whether your user account has the required role.

[AndersBGS]

Hi @t-takumi ,

You should look at the declarative actions is this is the buttons for workspaces. 

[Dinesh Chilaka]

Hi @t-takumi ,

In ServiceNow workspaces (e.g., CSM/FSM or Agent Workspace), a variant enables the same page URL to dynamically render different UI layouts or components based on the user's role or context, without changing the underlying page structure.

Scenario Example:
Consider an Incident record being worked on by two users: an Admin and an Agent.

The page URL remains identical for both (e.g., /now/workspace/agent/incident/12345).

However, the workspace variant renders distinct experiences:

Admin variant: Displays advanced tabs like "Audit Log," "SLAs," full scripting console, and bulk action buttons for elevated permissions.
Yes if we create an variant it will automatically get the UI actions related to that red

Agent variant: Shows a streamlined view with only "Summary," "Work Notes," "Attachments," and basic resolve/close actions—optimized for frontline support efficiency.

This is achieved in UI Builder via Variant conditions (e.g., role-based logic like gs.hasRole('admin')), ensuring contextual, role-appropriate interfaces while maintaining a single, shareable URL.

If you create a variant for the record page ,the UI actions related to that table all will come automatically no need to do any extra configurations.

If my response helped, mark it as helpful and accept the solution.