--- 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 --- # Components installed # Components installed with AES {#ariaid-title1} Release version: Australia Updated April 28, 2026 ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 3 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 AES Activating the App Engine Studio (AES) plugin installs various components including tables and user roles essential for managing and developing applications within AES. These components support application building, deployment, environment management, and user access control. Show full answer Show less ## Roles Installed Several key roles are installed to manage AES functionality: * **App Engine admin \[appengineadmin\]**: Full administrative rights for AES, including user and app configuration management. Automatically assigned to users in the AES Admins group. * **App Engine Studio app template admin \[apptemplateadmin\]**: Manages template use, sharing, and activation. Assigned individually by admins. * **App Engine Studio admin \[snappengstudio.admin\]**: Provides granular administrative access to AES and its tables, which can be combined with other granular roles for tailored permissions. * **App Engine Studio user \[snappengstudio.user\]**: Enables users to build applications within AES. Assigned automatically to AES Users group members. Additional granular admin roles from dependent applications include Collaboration request admin and AES Table Builder Wizard admin, which can be combined with other roles to fit specific user functions. Detailed role management guidance is available under configuring AES personas and granular admin roles. ## Tables Installed Several tables are installed to support AES operations and application lifecycle management: * **App Details**: Tracks developer activities during app creation in AES. * **Applications in Projects**: Lists applications created within AES projects. * **Environment**: Defines instances used for development, testing, and launching applications. * **Deployment Request**: Manages application deployment requests, enabling reviewers to approve, reject, or provide feedback. * **Pipeline**: Configures deployment pipelines for moving applications across environments, with only one active pipeline at a time. * **Project**: Captures details of AES development sessions and projects. * **Resources Content and Resources Content Topic**: Store help resources and their categorizations for user assistance within AES. * **Taxonomy and related tables (Category, Details)**: Manage and categorize application files by type such as data, experience, logic, automation, or security. Data preservers are added to pipeline-related tables to prevent overwriting during cloning on non-production instances, ensuring deployment configurations remain intact. ## Practical Implications for ServiceNow Customers Understanding these roles and tables helps administrators effectively manage AES access and application lifecycle processes. The roles enable precise control over who can build, administer, or deploy applications, while the tables provide structured storage and tracking of development and deployment data. The data preservers safeguard critical pipeline configurations during instance cloning, maintaining consistency across environments. Several types of components are installed with activation of the App Engine Studio (AES) plugin, including tables and user roles. 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). ## Roles installed {#installed-with-aes__section_wly_yyh_wdb} {#installed-with-aes__table_u1t_gb1_wdb__entry__3} | Role title \[name\] | Description | Contains roles | |-|-|-| | App Engine admin \[app_engine_admin\] | Administers AES, including users, app configuration, and other management tasks. This role is assigned automatically to users in the App Engine Studio Admins group. | * sn_request_read * sn_request_write * sn_app_eng_studio.user {#installed-with-aes__ul_bft_gqt_stb} | | App Engine Studio app template admin \[app_template_admin\] | Administers the use, sharing, and activation or deactivation of templates. This role is assigned by an admin to individual users. For more information, see [Manage template access](https://servicenow-prod.fluidtopics.net/xSTM_x_xsFJDrA6q8kxPbg "Control who has access to templates in App Engine Studio (AES) using the app_template_admin role. App template admins activate and deactivate templates and grant other users access to share their templates."). | * app-template-author * app-template-runner * flow-designer * flow-operator {#installed-with-aes__ul_lcw_hrt_stb} | | App Engine Studio admin \[sn_app_eng_studio.admin\] | Granular admin role that grants access to App Engine Studio and enables administrative access to App Engine Studio tables. You can combine this role with other granular admin roles or delegated development for additional permissions. For more information about granular admin 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). | sn_app_eng_studio.user | | App Engine Studio user \[sn_app_eng_studio.user\] | Builds applications in App Engine Studio. This role is assigned automatically to users in the App Engine Studio Users group. For more information, see [Grant user access to AES](https://servicenow-prod.fluidtopics.net/U5kT_5Fj9xeWN_kuhVor~A "Control who has access to build applications in App Engine Studio (AES) by adding users to AES Users group or the AES User Limited group."). | * catalog_builder_editor * app_template_runner * sn_g_app_creator.app_creator {#installed-with-aes__ul_zrm_hqt_stb} | [ ] {#installed-with-aes__table_u1t_gb1_wdb} Note: Additional granular admin roles are installed with App Engine Studio dependent applications, including: * Collaboration request admin \[sn_collab_request.collaboration_request_admin\] * AES Table Builder Wizard admin \[sn_table_bldr_wzd.table_bldr_wzd_admin\] {#installed-with-aes__ul_q2k_jsv_bjc}You can combine these granular admin roles with other roles to provide the level of access needed for a user's function. For more information about roles in App Engine Studio, see [Configure AES personas and roles](https://servicenow-prod.fluidtopics.net/TQ1R83bM5FLH5Z29G2zk3Q "The responsibilities of your staff are controlled by roles assigned to each member. Personas aren’t explicitly part of App Engine Studio (AES) but administrators assign roles to give team members permission to configure or use AES."). For more information about granular admin 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). ## Tables installed {#installed-with-aes__section_s1x_dzh_wdb} {#installed-with-aes__table_fbz_45z_vdb__entry__2} | Table | Description | |-|-| | App Details \[sn_app_eng_studio_app_details\] | Details about the operations that a developer used to create an application in App Engine Studio. The table is updated automatically as developers build applications in App Engine Studio. | | Applications in Projects \[sn_app_eng_studio_project_application_m2m\] | Applications that a developer creates in App Engine Studio. This table is updated automatically as developers build applications in App Engine Studio. | | Environment \[sn_pipeline_environment\] | Instances that you use for the developing, testing, or launching an application. You update this table as you define environments for App Engine Studio. | | Deployment Request \[sn_deploy_pipeline_deployment_request\] | Requests to review and publish an application that a developer created in App Engine Studio. From the deployment request form, a reviewer can deploy the application to different environments, accept or reject an application, and send feedback to a developer. For more information, see [Deployment Request form in the Pipelines and Deployments app](https://servicenow-prod.fluidtopics.net/Zug1shPHVimbxGlIA5Pw1w "The Deployment Request form is accessed from within the Pipelines and Deployments section of the App Engine Management Center."). | | Pipeline \[sn_pipeline_pipeline\] | Configurations for deploying applications to different environments. Only one pipeline can be active at a time. You update this table as you create a pipeline for the deployment of applications from App Engine Studio. For more information, see [Managing deployments using Pipelines and Deployments](https://servicenow-prod.fluidtopics.net/BzuaMeyjTR94t7g1nHeEVA "Manage deployments using Pipelines and Deployments in the App Engine Management Center (AEMC)."). | | Project \[sn_app_eng_studio_project\] | Details about App Engine Studio development sessions. A project is created automatically when a developer creates an application in App Engine Studio. This table is updated automatically as developers build applications in App Engine Studio. | | Resources Content \[sn_app_eng_studio_resources_content\] | Help resources that a developer can access in App Engine Studio. This table includes configurations to support the default user experience for App Engine Studio. | | Resources Content Topic \[sn_app_eng_studio_resources_content_topic\] | Categorizations of help resources in App Engine Studio. This table includes configurations to support the default user experience for App Engine Studio. | | Taxonomy \[sn_app_eng_studio_taxonomy\] | Application files that a developer creates in App Engine Studio. This table is updated automatically as developers build applications in App Engine Studio. | | Taxonomy Category \[sn_app_eng_studio_taxonomy_category\] | Categorizations for application files in App Engine Studio. By default, application files are categorized as data, experience, logic and automation, or security. This table includes configurations to support the default user experience for App Engine Studio. | | Taxonomy Details \[sn_app_eng_studio_taxonomy_details\] | Details about application files that a developer creates in App Engine Studio. This table includes configurations to support the default user experience for App Engine Studio. | [ ] {#installed-with-aes__table_fbz_45z_vdb} Note: Data preservers are added for the following tables related to pipelines: * Environment * Pipeline * Pipeline Environment Order * Pipeline Types {#installed-with-aes__ul_kr2_g14_trb} The data preservers prevent records in these tables from being overwritten during cloning on a non-production instance. For more information, see [Create a clone preserver](https://www.servicenow.com/docs/access?context=create-new-clone-preserver&version=australia&pubname=australia-platform-administration&ft:locale=en-US).