---
sourceDocument: Australia IT Service Management
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/it-service-management

 Release :

    - australia

ft:locale :

    - en-US

ft:publication_title :

    - Australia IT Service Management

ft:clusterId :

    - itsm

bundleId :

    - itsm

workflow :

    - Technology


---

# Configure service desk groups to access the Service Operations Workspace landing page

# Configure service desk groups to access the Service Operations Workspace landing page {#ariaid-title1}

Release version: Australia  
Updated March 12, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read  
Confirm that the right users have access to the Service Operations Workspace landing page.

## Before you begin

Role required: admin

## About this task

The landing page's access is based on the audience associated with that page. Configure the audiences with the required service desk groups and the users that are part of these service desk groups can then access the landing
page. If you want users from multiple service desk groups to access the landing page, you should configure the landing page's audience with all those service desk groups.

It is applicable only for an instance that has Service Operations Workspace 1.1 installed and has upgraded to Australia.

## Procedure

1. Configure the system property for landing page access by performing the following steps.
   1. From the All menu, navigate to sys_properties.list.
   2. To verify that the user criteria records are used instead of roles to access the landing page, set the glide.ux.user_criteria_enabled property to <kbd class="ph userinput">true</kbd>.
   3. Select Update.
   {#configure-service-desk-groups-sow__substeps_ktf_dsh_ysb}
2. Add the user's service desk groups to the audience's user criteria by performing the following steps.
   1. Navigate to AllNow Experience FrameworkBuilding BlocksAudiences.
   2. Select an audience and perform the following steps, for example, SOW Service Desk Audience.  
      Note:  
      If the User Criteria Inclusions related list is read-only after setting the glide.ux.user_criteria_enabled property to <kbd class="ph userinput">true</kbd>, open the audience record directly in the classic ServiceNow AI Platform user interface by navigating to the record URL with the sys_id of the audience. Editing user criteria records require write access to the sys_user_criteria table, which may require the admin role.
      1. From the User Criteria Inclusions related list, open the audience, for example, Service Desk Group Inclusion.
      2. For the Groups field, add the required service desk group that the user is part of.
      3. Select Update.
      {#configure-service-desk-groups-sow__ol_w3t_jkh_ysb}
   {#configure-service-desk-groups-sow__substeps_ons_y2h_ysb}
{#configure-service-desk-groups-sow__steps_zcw_s4l_ctb}

*[\>]: and then