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

 Release :

    - australia

ft:locale :

    - en-US

ft:publication_title :

    - Australia 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: Australia  
Updated March 12, 2026  
![](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 the Creator Studio plugin is activated, essential components such as tables and user roles are automatically installed.
This includes various configurations and properties that enhance the functionality of Creator Studio within ServiceNow.
Show full answer Show less  

## Key Features

* **Required Plugins:** To activate Creator Studio, the following plugins must be installed:
  * Creator Studio \[sncreatorstudio\]
  * Creator Studio - Global \[com.glide.creatorstudio.global\]
* **Properties Installed:** Key properties include:
  * **Template Deny List:** Hides specific App Engine Studio templates from users. Default value is a specific sysid.
  * **History Record Limit:** Controls the number of recently accessed apps, with a default value of 1000. Setting this to -1 disables the limit.
* **Roles Installed:** Various roles are installed to manage user permissions within Creator Studio, including:
  * **sncreatorstudio.user:** Allows users to create new apps.
  * **sncreatorstudio.admin:** Provides administrative write access.
  * **sncreatorstudio.basicread:** Grants basic read access to resources.
* **Tables Installed:** Significant tables include:
  * **Request Task:** Stores all requests made in Creator Studio.
  * **Creator Studio Activities:** Contains all standard and custom activities for automations.

## Key Outcomes

By installing Creator Studio, ServiceNow customers can streamline app creation and management processes, ensuring that the necessary components and permissions are in place for efficient operations. Admins have the flexibility to manage associated tables and user roles, allowing for tailored configurations that meet specific organizational needs.  
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=australia&pubname=australia-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=australia&pubname=australia-platform-administration&ft:locale=en-US).
    {#creator-studio-components-installed__ul_ifm_cpx_v2c}
:   For more information, see [Show the AES template](https://servicenow-prod.fluidtopics.net/LyaFn9h40J9VhVAmPbkE1w "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://servicenow-prod.fluidtopics.net/HrOQlP2NVlDxTiy7c5uTlw "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://servicenow-prod.fluidtopics.net/fuXNQaOF6ETkKpBqas3DVg "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}