---
sourceDocument: Yokohama Build or modify applications
sourceDocumentLink: https://www.servicenow.com/docs/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


---

# Create an experience for UI Builder

# Create an experience for UI Builder {#ariaid-title1}

* Release version: Yokohama
* 
* Updated January 30, 2025
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read

Learn how to create a workspace or portal experience for UI Builder in the ServiceNow platform.

## Before you begin

Role required: ui_builder_admin

## About this task

This task shows you a basic example of how to create a workspace or portal experience for UI Builder. This example creates an experience called Demo Experience to demonstrate the process.

## Procedure

1. Navigate to AllNow Experience FrameworkUI Builder.
2. Select Create from the UI Builder home page.  
3. Select Experience.
4. In the form, fill in the fields.  
   Figure 1. Create an experience dialog box

{#create-experience__table_mn1_ytg_wnb__entry__2}

| Field | Description |
|-|-|
| Name | Add a name to track your experience internally. The experience name is visible to users from the browser tab. For this example, it is <kbd class="ph userinput">MyApp</kbd>. |
| App Shell UI | You must choose an app shell for the experience to work. For example, you could choose a workspace or portal app shell. The app shell is the wrapper of the page contents, which is similar to the functionality of a web page. The app shell can show things like the logo of your company, user preferences, the search icon. For more information, see [Define UI experiences using app shells](https://www.servicenow.com/docs/SOu7yd6gtq2RDMZtsDR7aQ "Understand what app shells are, what app shells are available for UI Builder, and why you would pick one over another."). |
| URL path | Add a path for your experience. The path appends to the end of the URL parameter of your experience. For example, if you used <kbd class="ph userinput">MyApp</kbd> as the title for your experience, you could type <kbd class="ph userinput">my/app</kbd> for the path. |
| Landing path | The landing path is the prefix that people use to reach your experience homepage. To designate a page as the homepage, you must create a page that has a matching path. |
| Roles | Only users with these assigned roles can access the experience. If you leave this field empty, the experience is open to all logged-in users by default. |
[Table 1. Create an experience form]

{#create-experience__table_mn1_ytg_wnb}

5. Select Create to create your experience.
6. Select Open experience to view the main page for your experience.  
   Figure 2. Main page for your new experience  
   Note:  
   In addition to the name of your new experience, the screen includes the URL, application scope, admin panel, and the roles of users who can view the experience. Any pages or variants you create for the experience appear in the Pages and variants section.

## What to do next

Now that you have created an experience you can add and customize pages. For more information, see [Manage UI Builder pages and page variants](https://www.servicenow.com/docs/gTnZkApUadVKq3LWn7k3HA "Learn what a page is in UI Builder. Understand the building blocks of a UI Builder page, such as column layouts and components.").

*[\>]: and then