--- title: Components installed with Creator Studio description: When you activate the Creator Studio plugin, various components like tables and user roles are automatically installed. locale: en-US canonical_url: https://www.servicenow.com/docs/r/australia/application-development/creator-studio/creator-studio-components-installed.html release: australia product: Creator Studio classification: creator-studio topic_type: reference last_updated: "2026-03-12" reading_time_minutes: 3 breadcrumb: [Install, Configure, Creator Studio, Building no-code applications, Developing your application, Building applications] --- # Components installed with Creator Studio 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://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/platform-administration/find-components.md). ## What plugins are required to activate Creator Studio? You must install the following plugins for Creator Studio: - Creator Studio \[sn\_creatorstudio\] - Creator Studio - Global \[com.glide.creator\_studio.global\] ## Properties installed with Creator Studio - **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://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/platform-administration/c_UniqueRecordIdentifier.md). For more information, see [Show the AES template](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/application-development/creator-studio/creator-studio-unhide-template.md). - **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 ## Roles installed with Creator Studio 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://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/application-development/creator-studio/roles-creator-studio.md).
Role Description Contains role
sn\_creatorstudio.user - Provides access to Creator Studio - Users can create new apps - 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
sn\_creatorstudio.restricted\_user - Provides access to Creator Studio - Users can't create new apps - 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
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
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 canvas\_user
## Tables installed with Creator Studio
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://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/application-development/creator-studio/creator-studio-admin-app-table.md). - 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 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.
**Parent Topic:**[Installing Creator Studio from the ServiceNow Store](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/application-development/creator-studio/installing-creator-studio-from-the-store.md)