---
sourceDocument: Australia Build or modify applications
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/application-development

 Release :

    - australia

ft:locale :

    - en-US

ft:publication_title :

    - Australia Build or modify applications

ft:clusterId :

    - cadev

bundleId :

    - cadev

workflow :

    - Development, Data, and Analytics


---

# Configure non-default access to the experience switcher

# Configure non-default access to the experience switcher {#ariaid-title1}

Release version: Australia  
Updated May 7, 2026  
![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read  
Grant non-default roles access to the experience switcher so users can switch between development environments in ServiceNow Studio.

## Before you begin

Role required: admin

## About this task

By default, the Experience Configurations table \[sn_udc_experience_configuration\] grants admins and delegated developers access to the experience switcher. To grant non-default roles access, add them to the Experience
Visibility Controls table \[sn_udc_experience_visibility_control\]. For more information about default roles, see [Roles and access in app development tools](https://servicenow-prod.fluidtopics.net/CgpnWB2etwd_1u317hbZkg "Access to ServiceNow Studio, Creator Studio, and ServiceNow IDE is controlled by the roles and permissions your admin assigns. Update role assignments when you need to change which tools a user can access.").

* Admins and delegated developers can use the experience switcher because they may need access to any product where they've been delegated to administer or develop an app.
* Creator Studio users and Creator Studio restricted users don't generally have access to the experience switcher because administrators limit them to a more curated experience.
{#configure-access-experience-switcher__ul_fjf_wpx_qdc}

## Procedure

1. Navigate to Allsn_udc_experience_visibility_control.list.
2. Select New.
3. Enter the experience you are configuring roles for.  
   For example, enter <kbd class="ph userinput">Serv</kbd> to select ServiceNow Studio.
4. Specify the roles that should get access to the experience.
   1. Unlock the Available for roles field by selecting the lock icon ![]().
   2. Start typing and then select the name of the role you're giving access to.
   3. Lock the Available for roles field by selecting the unlock icon ![]().
   {#configure-access-experience-switcher__substeps_fnf_4rx_qdc}
5. Specify the roles that should not have access to the experience.
   1. Unlock the Not available for roles field by selecting the lock icon ![]().
   2. Start typing and then select the name of the role you're restricting access for.
   3. Lock the Not available for roles field by selecting the unlock icon ![]().
   {#configure-access-experience-switcher__substeps_obb_n5x_qdc}
6. Select Submit.  
   The role is added to the Experience Visibility Controls table and the specified users can now access the experience switcher.

*[\>]: and then