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

 Release :

    - yokohama

ft:locale :

    - en-US

ft:publication_title :

    - Yokohama 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: Yokohama
* 
* Updated January 30, 2025
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read

Control which roles have access to the experience switcher in ServiceNow Studio. The experience switcher enables you to easily switch between development environments to use the right tool for your task.

## Before you begin

Role required: admin

## About this task

By default, the Experience Configurations table \[sn_udc_experience_configuration\] gives admins and delegated developers access to see the experience switcher. However, you can add non-default roles to the Experience
Visibility Controls table \[sn_udc_experience_visibility_control\] to give access to the experience switcher. For more information about the default roles, see [Working with roles and access in app development tools](https://servicenow-prod.fluidtopics.net/PppcRPAdL91k1P49yhQZpg "Access to ServiceNow Studio, Creator Studio, and ServiceNow IDE depends on the roles and permissions your admin sets. However, there are some scenarios in which you might want to update the roles allowed to access each tool.").

* 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 that you're configuring roles for.  
   For example, start typing <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.

*[\>]: and then