---
sourceDocument: Zurich Build or modify applications
sourceDocumentLink: https://www.servicenow.com/docs/r/zurich/application-development

 Release :

    - zurich

ft:locale :

    - en-US

ft:publication_title :

    - Zurich Build or modify applications

ft:clusterId :

    - cadev

bundleId :

    - cadev

workflow :

    - Development, Data, and Analytics


---

# Installed components

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

* Release version: Zurich
* 
* Updated July 31, 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

Activating the Creator Studio plugin in ServiceNow automatically installs various essential components, including tables, user roles, and configuration properties.
These components enable customers to efficiently create, manage, and automate applications within Creator Studio.
Show full answer Show less  

## Required Plugins

To activate Creator Studio, customers must install two key plugins:

* Creator Studio \[sncreatorstudio\]
* Creator Studio - Global \[com.glide.creatorstudio.global\]

## Configuration Properties

Several properties are installed to control Creator Studio behavior:

* **com.glide.creatorstudio.templatedenylist**: Hides specific App Engine Studio templates from users creating apps by listing their sysids.
* **sncreatorstudio.historyrecordlimit**: Limits the number of recent accessed history records shown on the Creator Studio homepage (default 1000). Setting to -1 disables the limit, while lowering it can improve homepage load times.

## User Roles Installed

Creator Studio installs multiple roles tailored to different user personas and access levels:

* **sncreatorstudio.user**: Full access including app creation.
* **sncreatorstudio.restricteduser**: Access without app creation rights.
* **sncreatorstudio.basicread** and **sncreatorstudio.basicwrite**: Primitive read/write access to Creator Studio resources.
* **sncreatorstudio.admin** and **sncreatorstudio.adminwrite**: Administrative write access.
* Additional roles include app requestor and fulfiller roles with scoped permissions.

Note that App Engine admins with the admin role retain access to ServiceNow Studio via the experience switcher.

## Tables Installed

Creator Studio installs several important tables, many extending the Task table, which store app requests, tasks, activities, and configurations:

* **Request Task \[sncreatorstudiotask\]**: Central table for all app requests made in Creator Studio. Must be installed in both production and non-production instances.
* **Request Subtask \[sncreatorstudiochildtask\]** , **New Application Task** , and **New Application Admin Task**: Extend Task table to support app lifecycle management.
* **Request App Config \[sncreatorstudiorequestappconfig\]**: Extends Application File table for app configuration storage.
* **Creator Studio Activities \[sncreatorstudioactivity\]**: Stores all standard and custom automation activities; readable by Creator Studio users and delegated developers.

Administrators can customize the associated table and request types used by Creator Studio apps, requiring specific admin or configuration roles.

## Practical Benefits for Customers

By activating Creator Studio and its components, customers gain a ready-to-use framework for app development and request management within ServiceNow. The pre-installed roles facilitate secure and appropriate access controls for different user types. The tables provide structured data storage for app lifecycle and automation activities, supporting scalability and governance. Configuration properties allow fine-tuning of user experience and template availability, enhancing performance and usability.  
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=zurich&pubname=zurich-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=zurich&pubname=zurich-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/nP8WP6ZzpEPrZOjT8YFxlw "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/daOvZ9JEoX9YVxUC_h7Owg "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 associated table that each app in Creator Studio uses. However, the tables in this topics are still installed by default. For more information, see [Administering an app's associated table](https://www.servicenow.com/docs/Vaf9tHkA~bG6PpLVnccJBw "Admins can change the default table that apps built in Creator Studio save their requests to."). * 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. {#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}