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

 Release :

    - australia

ft:locale :

    - pt-BR

ft:publication_title :

    - Australia Build or modify applications

ft:clusterId :

    - cadev

bundleId :

    - cadev

workflow :

    - Development, Data, and Analytics


---

# Configure using Guided Setup

# Configure Creator Studio using Guided Setup {#ariaid-title1}

* Versão de lançamento: Australia
* 
* Atualizado 12 de mar. de 2026
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 8 min. de leitura

So you've installed Creator Studio on an instance. Now what? You must configure it before users can start building apps.

## Antes de Iniciar

Creator Studio must be installed on the instance before you can configure it. Find out more about that in [Installing Creator Studio from the ServiceNow Store](https://servicenow-prod.fluidtopics.net/xw0LVx93pSSr2AqK684mLg "Installing Creator Studio from the ServiceNow Store makes it available for people to build apps on your instance.").

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.

Role required: admin

## Por Que e Quando Desempenhar Esta Tarefa

Guided Setup streamlines configuring Creator Studio, and keeps track of what you have completed, so you can stop and start again where you left off.

In this Guided Setup, you'll configure user access and collaboration settings to control who can do what in Creator Studio.

## Procedimento

1. Let's open Guided Setup. On your instance, select the All tab.
2. In the white text field, enter <kbd class="ph userinput">App Engine</kbd>.  
   The list of apps displayed underneath the text box now pertains only to App Engine.
3. In the list, select Guided Setup -- Shared, which starts the configuration process.  
   The Guided Setup app opens, where you make some basic configurations.  
   Figura 1. Guided Setup
4. Start the setup process by selecting the Get Started button.
5. Select the Welcome to App Engine Guided Setup breadcrumb link to return to the main Guided Setup page.

## O que Fazer Depois

Next, it's time to configure specific Creator Studio features, which include the following:

* [Set up the Creator Studio admin group](https://servicenow-prod.fluidtopics.net/ZME3cNwanTTvJWNc_JfegA#crs-setup-admin-group "Set up the admin group to enable ServiceNow administrators access to work on and configure Creator Studio.")
* [Set up Creator Studio collaboration descriptors](https://servicenow-prod.fluidtopics.net/ZME3cNwanTTvJWNc_JfegA#crs-setup-collab-descriptors "Set up collaboration descriptors to manage what app Owner and Editor collaboration types can do in Creator Studio.")
* [Set up Creator Studio full access users](https://servicenow-prod.fluidtopics.net/ZME3cNwanTTvJWNc_JfegA#crs-setup-full-access-users "Set up who has full access to Creator Studio to decide which users get full access to work on app in Creator Studio, and who has more limited capabilities.")
* [Set up Creator Studio restricted access users](https://servicenow-prod.fluidtopics.net/ZME3cNwanTTvJWNc_JfegA#crs-setup-restricted-users "Set up limited access for Creator Studio users. People in the Creator Studio Restricted Users Group have limited access to working with apps, and must request that admins create apps for them.")
* [Set up Creator Studio playbook activities](https://servicenow-prod.fluidtopics.net/ZME3cNwanTTvJWNc_JfegA#crs-setup-playbook-activities "Configure the activities that appear when users build playbooks in Creator Studio.")
* [Configure the table for Creator Studio apps](https://servicenow-prod.fluidtopics.net/ZME3cNwanTTvJWNc_JfegA#crs-setup-app-table "Use Guided Setup to change the table that the app saves its requests to.")
* [Set up Creator Studio custom notification emails](https://servicenow-prod.fluidtopics.net/ZME3cNwanTTvJWNc_JfegA#crs-setup-email-notifications "Configure customized email notifications that Creator Studio apps send. For example, you can add branding to notification emails that a request was opened.")
{#config-creator-studio-guided-setup__ul_em5_fqg_pgc}

## O que Fazer Depois

After you finish configuring Creator Studio, you can configure Pipelines and Deployments to enable apps built in Creator Studio to be deployed to production. For information on how, see [Configure Pipelines and Deployments](https://servicenow-prod.fluidtopics.net/cyoyYrjdGhH7FmbtbLgXWg "Use the Pipelines and Deployments guided setup to complete the initial configuration of Pipelines and Deployments. Detailed instructions for each step are provided in subsequent sections of the product documentation.").

## Set up the Creator Studio admin group {#ariaid-title2}

Set up the admin group to enable ServiceNow administrators access to work on and configure Creator Studio.

### Antes de Iniciar

Initiate the Guided Setup as described in [Configure Creator Studio using Guided Setup](https://servicenow-prod.fluidtopics.net/ZME3cNwanTTvJWNc_JfegA#config-creator-studio-guided-setup "So you've installed Creator Studio on an instance. Now what? You must configure it before users can start building apps.").

### Antes de Iniciar

Role required: admin

### Procedimento

1. Select the Get Started button in the Set up user access section.
2. Select the Configure button for the Set up the admin group section.
3. Make any changes to the App Engine Admins group.  
   App Engine Admins approve tasks for app development, such as when restricted users need an app created for them.
4. Update the record to save your changes.
5. Select the Mark as complete button on the Guided Setup page to indicate that you're done with this step.

### O que Fazer Depois

Next, [Set up Creator Studio collaboration descriptors](https://servicenow-prod.fluidtopics.net/ZME3cNwanTTvJWNc_JfegA#crs-setup-collab-descriptors "Set up collaboration descriptors to manage what app Owner and Editor collaboration types can do in Creator Studio.").

## Set up Creator Studio collaboration descriptors {#ariaid-title3}

Set up collaboration descriptors to manage what app Owner and Editor collaboration types can do in Creator Studio.

### Antes de Iniciar

Initiate the Guided Setup as described in [Configure Creator Studio using Guided Setup](https://servicenow-prod.fluidtopics.net/ZME3cNwanTTvJWNc_JfegA#config-creator-studio-guided-setup "So you've installed Creator Studio on an instance. Now what? You must configure it before users can start building apps.").

Role required: admin

### Procedimento

1. Select the Configure button for the Set up collaboration descriptors to manage your user's capabilities section.  
   By default, owners can do anything on an app, while editors are more restricted in what they can do. For more information, see [Collaborating with others to build apps in Creator Studio](https://servicenow-prod.fluidtopics.net/ZHCMnKoqNY9_r~2ka0rxiQ "Sometimes you need help with building out your app, and that’s OK! And sometimes other people need your help building their apps, which is great! This point is where collaboration comes into play.").
2. Customize the collaboration roles or add new ones.  
   For more information, see [Application collaboration](https://servicenow-prod.fluidtopics.net/NFI_m30krkjNdKpYnrRlvg "People with admin privileges can manage the permissions of developers collaborating on an application.").
3. Update the record to save your changes.
4. Select the Mark as complete button on the Guided Setup page to indicate that you're done with this step.

### O que Fazer Depois

Next, [Set up Creator Studio full access users](https://servicenow-prod.fluidtopics.net/ZME3cNwanTTvJWNc_JfegA#crs-setup-full-access-users "Set up who has full access to Creator Studio to decide which users get full access to work on app in Creator Studio, and who has more limited capabilities.").

## Set up Creator Studio full access users {#ariaid-title4}

Set up who has full access to Creator Studio to decide which users get full access to work on app in Creator Studio, and who has more limited capabilities.

### Por Que e Quando Desempenhar Esta Tarefa

For example, restricted users must request that an admin create a new app for them. For more information, see [Creator Studio roles and personas](https://servicenow-prod.fluidtopics.net/DaGqrj2XVFjj~Ff4wv4K7A "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.").

### Antes de Iniciar

Initiate the Guided Setup as described in [Configure Creator Studio using Guided Setup](https://servicenow-prod.fluidtopics.net/ZME3cNwanTTvJWNc_JfegA#config-creator-studio-guided-setup "So you've installed Creator Studio on an instance. Now what? You must configure it before users can start building apps.").

Role required: admin

### Procedimento

1. Select the Get Started button in the Set up access to Creator Studio section.
2. Set up full access for users by selecting the Configure button for the Grant full Creator Studio access to users section.
3. Add users to the Creator Studio Users Group.  
   People in the Creator Studio Users Group have full access to working with apps, and can create apps without needing help from an admin.
4. Update the record to save your changes.
5. Select the Mark as complete button on the Guided Setup page to indicate that you're done with this step.

### O que Fazer Depois

Next, [Set up Creator Studio restricted access users](https://servicenow-prod.fluidtopics.net/ZME3cNwanTTvJWNc_JfegA#crs-setup-restricted-users "Set up limited access for Creator Studio users. People in the Creator Studio Restricted Users Group have limited access to working with apps, and must request that admins create apps for them.").

## Set up Creator Studio restricted access users {#ariaid-title5}

Set up limited access for Creator Studio users. People in the Creator Studio Restricted Users Group have limited access to working with apps, and must request that admins create apps for them.

### Antes de Iniciar

Initiate the Guided Setup as described in [Configure Creator Studio using Guided Setup](https://servicenow-prod.fluidtopics.net/ZME3cNwanTTvJWNc_JfegA#config-creator-studio-guided-setup "So you've installed Creator Studio on an instance. Now what? You must configure it before users can start building apps.").

Role required: admin

### Procedimento

1. Navigate to All.
2. Select the Configure button for the Grant Creator Studio Restricted access to users section.
3. Add users to the Creator Studio Restricted Users Group.
4. Update the record to save your changes.
5. Select the Mark as complete button on the Guided Setup page to indicate that you're done with this step.

## Set up Creator Studio custom notification emails {#ariaid-title6}

Configure customized email notifications that Creator Studio apps send. For example, you can add branding to notification emails that a request was opened.

### Por Que e Quando Desempenhar Esta Tarefa

Customized email templates can be applied to notifications that are sent when users request something from an app, or the request was changed or closed.

### Antes de Iniciar

Initiate the Guided Setup as described in [Configure Creator Studio using Guided Setup](https://servicenow-prod.fluidtopics.net/ZME3cNwanTTvJWNc_JfegA#config-creator-studio-guided-setup "So you've installed Creator Studio on an instance. Now what? You must configure it before users can start building apps.").

Role required: admin

### Procedimento

1. Select the Configure button for the Configure Email Notifications Creator Studio Requests section.
2. Add users to the Creator Studio Restricted Users Group.  
   A table displays all email notifications for Creator Studio.
3. Select the Name of the email that you want to customize.  
   For example, Request opened.  
   Nota:  
   Depending on your scope, you may need to switch to the Creator Studio Configurations scope to make changes.
4. Make any updates and customizations to the content of the email.  
   You can select into any of the following tabs to edit their details:
   1. When to send
   2. Who will receive
   3. What it will contain

   {#crs-setup-email-notifications__ol_wjk_4wb_2gc}

   For more information on editing notifications on the ServiceNow AI Platform, see [Create an email notification](https://www.servicenow.com/docs/access?context=t_CreateANotification&version=australia&pubname=australia-platform-administration&ft:locale=en-US).
5. Update the record to save your changes.
6. Select the Mark as complete button on the Guided Setup page to indicate that you're done with this step.

## Set up Creator Studio playbook activities {#ariaid-title7}

Configure the activities that appear when users build playbooks in Creator Studio.

### Antes de Iniciar

Initiate the Guided Setup as described in [Configure Creator Studio using Guided Setup](https://servicenow-prod.fluidtopics.net/ZME3cNwanTTvJWNc_JfegA#config-creator-studio-guided-setup "So you've installed Creator Studio on an instance. Now what? You must configure it before users can start building apps.").

Role required: admin

### Procedimento

1. Select the Configure button for the Configure Playbook activities for Creator Studio section.  
   All of the default Creator Studio playbook activities appear.Figura 2. Creator Studio activities in Guided Setup
2. **Opcional:** Rearrange the order activities appear in the selection list.  
   Order numbers are relative to the other activities, which you can view on the Configure Playbook activities for Creator Studio landing page in Guided Setup.
   1. Select into the Order column for the activity you want to renumber.
   2. Enter a new order number for the activity.  
      Figura 3. Reorder an activity
   3. Select the Save icon ![]() or press Enter.
   {#crs-setup-playbook-activities__substeps_qdx_2lg_pgc}
3. **Opcional:** Add a new activity.  
   Nota:  
   The activity must already be configured in the activities table for you to add it to the Creator Studio playbook list.
   1. Select the New button.
   2. Search for the activity you want to add in the Activity field.
   3. Enter the Order it appears in.
   4. Enter a Short Description, which will appear in the activity picker under the activity name.
   5. Leave the Active check box selected to make the activity visible immediately.
   6. Select the Submit button.
   {#crs-setup-playbook-activities__substeps_rny_yhg_pgc}

### O que Fazer Depois

Users who are actively working in Creator Studio must refresh their browser to see the changes you just made.

## Configure the table for Creator Studio apps {#ariaid-title8}

Use Guided Setup to change the table that the app saves its requests to.

### Por Que e Quando Desempenhar Esta Tarefa

Some general guidelines for changing the table are:

* If you change an app's table to one that doesn't extend a Request Task-extended table, it could affect automations.
* If the new table doesn't have the request_type field, the app's automations won't be correctly triggered.  
  Nota:  
  You can change the Request type field, which specifies the form, on the Request Task table or a table that extends Request Task. To do so, you must be an admin or have the sn_creatorstudio.configuration_admin or sn_creatorstudio.task_admin role.
* The request_type field for the new table should have the label Request type, and it should be a reference to the Record Producer table.
* If the new table isn't in the same scope as the app, the scope of the table must allow updates from other scopes.
{#crs-setup-app-table__ul_e21_cnt_bfc}

### Antes de Iniciar

Initiate the Guided Setup as described in [Configure Creator Studio using Guided Setup](https://servicenow-prod.fluidtopics.net/ZME3cNwanTTvJWNc_JfegA#config-creator-studio-guided-setup "So you've installed Creator Studio on an instance. Now what? You must configure it before users can start building apps.").

The app must already be created before you can change the table for it.

### Antes de Iniciar

For more information on changing an app's table, see [Changing the table for an app](https://servicenow-prod.fluidtopics.net/9kC92Ck427Ka0IDZXiMh9Q "Admins can change the associated table for an app built in Creator Studio. That is, you can change the table that the app saves its requests to.").

Role required: admin

Role required: admin, app configurator (sn_creatorstudio.app_configurator), or Creator Studio configuration admin (sn_creatorstudio.configuration_admin). For more information on working with granular roles, see [Granular admin roles](https://www.servicenow.com/docs/access?context=granular-admin-roles&version=australia&pubname=australia-platform-security&ft:locale=en-US).

### Procedimento

1. Select the Configure button for the Configure the associated table for Creator Studio Service Desk apps section.  
   All of the apps built on the instance in Creator Studio appear.Figura 4. Guided Setup to configure the associated table
2. Select the app that you want to change the table for.  
   Nota:  
   You may need to change the scope that you're in.
3. Change the table.
   1. Select into the Request table field.
   2. Search for and select the table that you want to associate the app with.  
      Figura 5. Change the table
   {#crs-setup-app-table__substeps_bnf_fnm_pgc}
4. Select the Update button.

### Resultado

The associated table for an app changes to the new table. Any users currently in Creator Studio may need to refresh their browser to see the change.