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


---

# Components installed with Creator Studio

# Components installed with Creator Studio {#ariaid-title1}

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

Summarize  
![AI sparkle icon](https://servicenow.com/docs/portal-asset/ai-sparkle-icon) Summarized using AI  
This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete.  

## Summary of Components installed with Creator Studio

When you activate the Creator Studio plugin in ServiceNow, it automatically installs various essential components including tables, user roles, and properties that support app creation and management.
This setup streamlines the process for users and administrators by providing the necessary infrastructure to build and handle applications within Creator Studio.
Show full answer Show less  

## Key Features

* **Required Plugins:** Activation requires two plugins: Creator Studio \[sncreatorstudio\] and Creator Studio - Global \[com.glide.creatorstudio.global\].
* **Properties:** Includes settings such as *templatedenylist* to hide specific App Engine Studio templates and *historyrecordlimit* to control the number of recent app access records displayed, which can be adjusted to improve performance.
* **User Roles:** Multiple roles are installed with Creator Studio to manage access and permissions, ranging from users who can create apps to those with read-only or administrative rights. These roles align with typical user personas such as app creators, requestors, and fulfillers.
* **Tables:** Several tables are installed to manage requests, tasks, activities, and configurations related to Creator Studio apps. Notably, the *Request Task \[sncreatorstudiotask\]* table is essential and must exist on both production and non-production instances.

## Key Outcomes

* ServiceNow customers gain a ready-to-use environment for app creation with all necessary components pre-installed and configured for immediate use.
* Role-based access control enables secure and efficient app development workflows tailored to different user responsibilities.
* Administrators have flexibility to manage app-related data and tasks through dedicated tables, ensuring proper tracking and automation capabilities.
* Performance tuning is supported through configurable properties, helping maintain an optimal user experience on the Creator Studio home page.  
When you activate the Creator Studio plugin, various components like tables and user roles are automatically installed.
Note:  
The Application Files table lists the components that are installed with this application. For instructions on how to access this table, see [Find components installed with an
application](https://www.servicenow.com/docs/access?context=find-components&version=yokohama&pubname=yokohama-platform-administration&ft:locale=en-US).

## What plugins are required to activate Creator Studio? {#creator-studio-components-installed__section_z4k_zqg_x1c}

You must install the following plugins for Creator Studio:

* Creator Studio \[sn_creatorstudio\]
* Creator Studio - Global \[com.glide.creator_studio.global\]
{#creator-studio-components-installed__ul_izt_brg_x1c}

## Properties installed with Creator Studio {#creator-studio-components-installed__section_at4_x2p_ldc}

com.glide.creator_studio.template_deny_list
:   Hides App Engine Studio template from appearing for users when they create an app.

    * Type: string
    * Default value: 211f71ca73202010ae42d31ee2f6a785
    * Hide additional templates by adding their system values (sys_id for the template), separated by commas, in the Value field. For more information on the sys_id, see [Unique record identifier (sys_id)](https://www.servicenow.com/docs/access?context=c_UniqueRecordIdentifier&version=yokohama&pubname=yokohama-platform-administration&ft:locale=en-US).
    {#creator-studio-components-installed__ul_ifm_cpx_v2c}
:   For more information, see [Show the AES template](https://www.servicenow.com/docs/N1yrGguKNvFItPtyS_vfrA "You can make the App Engine Studio (AES) template, which is hidden by default, appear for users when they create an app in Creator Studio.").

sn_creatorstudio.history_record_limit
:   Limits the last accessed history, for example in recent apps and sorting on the Creator Studio home page.

    * Type: integer
    * Default value: 1000
    * Set this value to -1 to disable the limit
    * Reduce this value from the default if the home page isn't loading fast enough
    {#creator-studio-components-installed__ul_id3_mlv_ldc}

## Roles installed with Creator Studio {#creator-studio-components-installed__section_rlf_b4l_51c}

The following table lists all roles installed with Creator Studio. For details on how the roles work with Creator Studio, 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.").{#creator-studio-components-installed__table_oyr_sy3_v1c__entry__3}

| Role | Description | Contains role |
|-|-|-|
| sn_creatorstudio.user | * Provides access to Creator Studio * Users can create new apps {#creator-studio-components-installed__ul_e5z_qz3_v1c} | * catalog_builder_editor * sn_collab_request.basic_write * sn_udc.basic_read * sn_creatorstudio.basic_read * sn_collab_request.basic_read * app_template_runner * sn_g_app_creator.app_creator {#creator-studio-components-installed__ul_g2j_5z3_v1c} |
| sn_creatorstudio.restricted_user | * Provides access to Creator Studio * Users can't create new apps {#creator-studio-components-installed__ul_vs4_lz3_v1c} | * catalog_builder_editor * sn_creatorstudio.app_requestor * sn_collab_request.basic_write * sn_udc.basic_read * sn_creatorstudio.basic_read * sn_collab_request.basic_read * app_template_runner {#creator-studio-components-installed__ul_bdp_nz3_v1c} |
| sn_creatorstudio.basic_read | Primitive read access to Creator Studio resources |   |
| sn_creatorstudio.basic_write | Primitive write access to Creator Studio resources |   |
| sn_creatorstudio.admin | Admin write access to Creator Studio Note: App Engine admins (app_engine_admin) with this role are not restricted from accessing ServiceNow Studio in the experience switcher. | sn_creatorstudio.admin_write |
| sn_creatorstudio.admin_write | Admin write access to Creator Studio | * sn_creatorstudio.basic_read * sn_creatorstudio.basic_write {#creator-studio-components-installed__ul_lkv_zy3_v1c} |
| sn_creatorstudio.app_requestor | Primitive app requester access to Creator Studio resources |   |
| sn_creatorstudio.basic_fulfiller | Gives some fulfillers the following: * Access to the Request App Workspace * Ability to edit some fields in the sn_creatorstudio_task table {#creator-studio-components-installed__ul_p5j_gz3_v1c} | canvas_user |
[Table 1. Roles installed with Creator Studio]

{#creator-studio-components-installed__table_oyr_sy3_v1c}

## Tables installed with Creator Studio {#creator-studio-components-installed__section_ok4_d4l_51c}

{#creator-studio-components-installed__table_dhl_j4l_51c__entry__2}

| Table | Description |
|-|-|
| Request Subtask \[sn_creatorstudio_child_task\] | Extends the Task table. |
| New Application Admin Task \[sn_creatorstudio_new_application_admin_task\] | Extends the Task table. |
| New Application Task \[sn_creatorstudio_new_application_task\] | Extends the Task table. |
| Request App Config \[sn_creatorstudio_request_app_config\] | Extends the Application File table. |
| Request Task \[sn_creatorstudio_task\] | Table where all requests from apps made in Creator Studio are stored. Note: * You must have the Request Task table installed on the production instance as well as the non-production instance. * Admins can change the underlying table that each app in Creator Studio uses. However, the tables in this topics are still installed by default. {#creator-studio-components-installed__ul_mxr_kqz_1fc} |
| Creator Studio Activities \[sn_creatorstudio_activity\] | Table where all standard and custom activities for Creator Studio automations are stored. Note: This table is readable by Creator Studio users and delegated developers. |
[Table 2. Tables installed]

{#creator-studio-components-installed__table_dhl_j4l_51c}