---
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


---

# Configuring Creator Studio

# Configuring Creator Studio {#ariaid-title1}

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

Admins need to install Creator Studio before it can be configured for users to start building apps.

## Configuration overview {#configuring-creator-studio__section_cth_gbl_d1c}

The following is a general overview of installing and configuring Creator Studio.

1. Decide on an instance strategy, for example, what are your development (non-production) and production instances. For more information, see [Creator Studio development instance strategy](https://www.servicenow.com/docs/HPh6Qw0Z7R54YJOU88YALA "Make sure to install Creator Studio on all ServiceNow instances where users will be building applications, including the production instance.").
2. Download Creator Studio from the ServiceNow Store and install it. For more information, see [Installing Creator Studio from the ServiceNow Store](https://www.servicenow.com/docs/SRCz2hZ_Im2j38Ubo0VhpQ "Installing Creator Studio from the ServiceNow Store makes it available for people to build apps on your instance.").
3. Run Guided Setup to configure administration and collaboration. For more information, see [Configure Creator Studio using Guided Setup](https://www.servicenow.com/docs/vB7sqC2g0q21HFEhU9cHMQ "So you've installed Creator Studio on an instance. Now what? You must configure it before users can start building apps.").
4. Ensure all users who need access have the correct role. For more information, see [Creator Studio roles and personas](https://www.servicenow.com/docs/BZXV1eeUDgME7cqrKhKYig "Roles control what everyone you work with can do in Creator Studio. Administrators assign roles to give team members permission to configure or use Creator Studio.").
{#configuring-creator-studio__ol_c2r_zr2_w1c}

## Using Guided Setup to implement Creator Studio {#configuring-creator-studio__section_dth_gbl_d1c}

Guided Setup provides a sequence of tasks that help you configure Creator Studio on your ServiceNow instance. Currently, the Guided Setup helps you to set up the following:

* The admin group to define who can administer Creator Studio
* Collaboration descriptors to manage what app owners and editors can do
* Who has full and restricted access to creating apps in Creator Studio
{#configuring-creator-studio__ul_i24_hr2_w1c}

To open Guided Setup for Creator Studio, navigate to AllApp EngineGuided Setup -- Shared.

For more information, see [Guided Setup](https://www.servicenow.com/docs/access?context=guided-setup&version=yokohama&pubname=yokohama-platform-user-interface&ft:locale=en-US).

## Catalog configuration requirement for Creator Studio {#configuring-creator-studio__section_fkj_23b_v1c}

To ensure that forms appear correctly for users, the non-production and production instances must have the same Service Catalog and all of its categories.

## Configuring Virtual Agent chatbot previews {#configuring-creator-studio__section_xqc_nxc_y1c}

If you want forms to appear in the Virtual Agent chatbot, you must install the necessary plugins. For more information, see [Activate Virtual Agent](https://www.servicenow.com/docs/access?context=activate-virtual-agent&version=yokohama&pubname=yokohama-conversational-interfaces&ft:locale=en-US).
* **[Installing Creator Studio from the ServiceNow Store](https://www.servicenow.com/docs/SRCz2hZ_Im2j38Ubo0VhpQ)**   
  Installing Creator Studio from the ServiceNow Store makes it available for people to build apps on your instance.
* **[Configure Creator Studio using Guided Setup](https://www.servicenow.com/docs/vB7sqC2g0q21HFEhU9cHMQ)**   
  So you've installed Creator Studio on an instance. Now what? You must configure it before users can start building apps.
* **[Configuring Pipelines and Deployments to deploy apps built in Creator Studio](https://www.servicenow.com/docs/T6dzhYs~lXH1MDE2mJ0aFA)**   
  You can install Pipelines and Deployments and configure a controller instance to deploy apps built in Creator Studio to production instances.
* **[Creator Studio roles and personas](https://www.servicenow.com/docs/BZXV1eeUDgME7cqrKhKYig)**   
  Roles control what everyone you work with can do in Creator Studio. Administrators assign roles to give team members permission to configure or use Creator Studio.
* **[Creator Studio and domain separation](https://www.servicenow.com/docs/f7KRT6St16WfMHC5_n0JDQ)**   
  Domain separation is not supported in Creator Studio. This means that you can't separate data, processes, and administrative tasks into distinct groups, called domains, within the ServiceNow AI Platform.
* **[Configuring form generation in Creator Studio](https://www.servicenow.com/docs/SrvuR3VwyQMHJVehSVlFvQ)**   
  Install and configure ServiceNow Otto for Creator in Creator Studio.

*[\>]: and then