---
sourceDocument: Xanadu Employee Service Management
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/xanadu/employee-service-management

 Release :

    - xanadu

ft:locale :

    - en-US

ft:publication_title :

    - Xanadu Employee Service Management

ft:clusterId :

    - emplsm

bundleId :

    - emplsm

workflow :

    - Employee


---

# Add the Universal Task list category in Service Operations Workspace Core

# Add the Universal Task list category in Service Operations Workspace Core {#ariaid-title1}

* Release version: Xanadu
* 
* Updated August 1, 2024
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read

Add the Universal Task list category to the new Service Operations Workspace Core so that agents can access and navigate through various modules directly from the new workspace.

## Before you begin

Role required: admin

## About this task

Due to the deprecation of the old service operations workspace, the Universal Task category listing isn't displayed in the new workspace. To display the relevant modules, you can manually add records to the table sys_ux_list_category.

## Procedure

1. Navigate to AllSystem DefinitionTablesUX List CategoriesShow List.  
   To access the list directly, you can use the navigation search bar and perform a search by using the table name sys_ux_list_category.list.
2. Insert records in the sys_ux_list_category table by selecting New.
3. On the form, fill in the fields.  
   For more information, see [.](https://www.servicenow.com/docs/access?context=ux-list-category-form&version=xanadu&pubname=xanadu-it-business-management&ft:locale=en-US).
4. Select Submit.
{#add-universal-task-list-categories__steps_fh3_lqh_3xb}

## Result

The Universal Task list category is added to the Service Operations Workspace Core.
* **[Add lists under the Universal Task list categories](https://servicenow-prod.fluidtopics.net/RzjruCukDwn7Les_TJjnQA)**   
  Add lists under the newly created Universal Task list category in Service Operations Workspace so that agents can access these modules from the new workspace.

*[\>]: and then