--- sourceDocument: Australia Build or modify applications sourceDocumentLink: https://www.servicenow.com/docs/r/australia/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 --- # Perform configuration tasks # Perform AES configuration tasks {#ariaid-title1} Release version: Australia Updated April 28, 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 Perform AES configuration tasks Configuring App Engine Studio (AES) in your ServiceNow environment involves setting up the application, managing access, activating essential features, and integrating tools to enable efficient app development and collaboration. These tasks are primarily performed during the AES guided setup and are critical to provide developers and administrators with the appropriate capabilities and controls. Show full answer Show less ## Key Configuration Tasks * **Install App Engine Studio:** Install the AES application (com.snc.app-engine-studio) in development instances using administrative privileges. This also installs related applications and plugins if needed. * **Set up instance credentials:** Create Connections and Credentials aliases for each instance, ensuring the alias type is Credential to enable secure connections. * **Activate Playbooks:** Enable Playbooks and the Process Automation Designer plugin (com.glide.pad.license) to allow process editing within AES. * **Set up Integration Hub spokes:** Activate spokes such as Gmail, Google Sheets, Jira, Microsoft 365 Excel, Microsoft Teams, Slack, Twilio, X (formerly Twitter), and Zoom to enhance integration capabilities within AES and Workflow Studio. * **Review access settings:** Adjust permissions for Workflow Studio and Catalog Builder to empower developers with suitable editing and catalog management rights. * **Set up an instance scan cadence:** Schedule regular scans in Health Center to detect issues arising from app development activities. * **Manage user access groups:** * Add users to the AES Admin group in production instances for administrative control and to receive notifications. * Add developers to the AES Users group in development instances to enable app building. * Add collaborators to the AES User Limited group to allow collaboration on apps created by others. * **Set up collaboration descriptors:** Define custom collaboration roles globally to tailor how collaborators are represented in AES. * **Manage template access:** Assign the apptemplateadmin role in non-production instances to users who will manage app templates' activation, deactivation, and sharing. ## Practical Benefits By completing these configuration tasks, ServiceNow customers ensure that their AES environment is secure, integrated, and aligned with organizational roles and responsibilities. This enables developers to efficiently build and collaborate on applications, administrators to maintain control and oversight, and teams to leverage integrations that streamline workflows. Regular instance scans help maintain system health, while tailored access settings promote compliance and governance within app development processes. As you work through the App Engine Studio (AES) guided setup, you must perform different configuration tasks. ## Setting up environments, tools, and user access {#aes-config-tasks__section_qw5_2qk_psb} The following table lists the tasks required for configuring App Engine Studio, including links to detailed instructions for completing the tasks. {#aes-config-tasks__table_lqq_1qt_rhb__entry__2}{#aes-config-tasks__integrationhub-spokes} | Task | Description | |-|-| | Install App Engine Studio in your development instances. | You can install the App Engine Studio application (com.snc.app-engine-studio) if you have the admin role. The application installs related ServiceNow® Store applications and plugins if they are not already installed. For detailed instructions, see [Installing App Engine Studio](https://www.servicenow.com/docs/n~GOnec_sMS36RvKqQIcvg "You can install the App Engine Studio (AES) application (com.snc.app-engine-studio) if you have the admin role. The application installs related ServiceNow Store applications and plugins if they are not already installed."). | | Set up instance credentials. | For each instance that you're using, create a Connections and Credentials alias. Verify that the alias type is Credential, not Connection and Credential. For detailed instructions, see [Set up instance credentials](https://www.servicenow.com/docs/access?context=connection-alias&version=australia&pubname=australia-platform-security&ft:locale=en-US). | | Activate Playbooks. | You can edit processes in App Engine Studio, but you must activate Playbooks for App Engine Studio and enable the Process Automation Designer for App Engine \[com.glide.pad.license\] plugin to get started. For more information, see [Activate Playbooks](https://www.servicenow.com/docs/access?context=activate-process-automation-designer&version=australia&pubname=australia-build-workflows&ft:locale=en-US). | | Set up Integration Hub spokes. | Activate spokes to enhance your Workflow Studio and App Engine Studio experience with integration-specific content. The following spokes are available for use with App Engine Studio. * [Gmail spoke](https://www.servicenow.com/docs/access?context=setup-gmail&version=australia&pubname=australia-integrate-applications&ft:locale=en-US) * [Google Sheets spoke](https://www.servicenow.com/docs/access?context=setup-gsheets&version=australia&pubname=australia-integrate-applications&ft:locale=en-US) * [Jira Spoke](https://www.servicenow.com/docs/access?context=jira-spoke-v3-0-2&version=australia&pubname=australia-integrate-applications&ft:locale=en-US) * [Microsoft 365 Excel spoke](https://www.servicenow.com/docs/access?context=setup-office-365-excel&version=australia&pubname=australia-integrate-applications&ft:locale=en-US) * [Microsoft Teams spoke](https://www.servicenow.com/docs/access?context=microsoft-teams-spoke&version=australia&pubname=australia-integrate-applications&ft:locale=en-US) * [Slack spoke](https://www.servicenow.com/docs/access?context=set-up-slack&version=australia&pubname=australia-integrate-applications&ft:locale=en-US) * [Twilio spoke](https://www.servicenow.com/docs/access?context=setup-twilio&version=australia&pubname=australia-integrate-applications&ft:locale=en-US) * [X Spoke (formerly Twitter Spoke)](https://www.servicenow.com/docs/access?context=twitter-spoke-ol&version=australia&pubname=australia-integrate-applications&ft:locale=en-US) * [Zoom spoke](https://www.servicenow.com/docs/access?context=setup-zoom&version=australia&pubname=australia-integrate-applications&ft:locale=en-US) {#aes-config-tasks__ul_om1_5kl_lrb} | | Review access settings for Workflow Studio in your development instance. | Enable your developers to use the editing capabilities that best suit them. For detailed instructions, see [Review Flow Designer access settings](https://www.servicenow.com/docs/access?context=user-access-flow-designer&version=australia&pubname=australia-build-workflows&ft:locale=en-US). | | Review access settings for Catalog Builder. | Enable your developers to add items to the appropriate catalogs and categories.​ For detailed instructions, see [Review Catalog Builder access settings](https://www.servicenow.com/docs/access?context=catalog-builder&version=australia&pubname=australia-servicenow-platform&ft:locale=en-US). | | Set up an instance scan cadence. | Schedule regular scans of your instance so that you can identify possible issues that arise from application development in App Engine Studio. For detailed instructions, see [Set up an instance scan cadence in Health Center](https://www.servicenow.com/docs/access?context=hs-landing-page&version=australia&pubname=australia-platform-administration&ft:locale=en-US). | | In your production instance, add users to the App Engine Studio admin group. | Add members to the group so they can review app- and deployment-related requests. Also, define a contact email address for the group. For detailed instructions, see [Add users to the App Engine Admin group](https://www.servicenow.com/docs/5fjJ~hiuoWm1J8ddxiQpBQ "Add users to the App Engine Admin group in your production instance to give them administrative rights to App Engine Studio (AES). You must also identify a contact email address for the group. After you configure the email address of the App Engine Admin group, members can receive notifications for app development-related requests, including app intake requests."). | | In your development instance, add developers to the App Engine Studio users group. | Enable developers in your organization to build applications in App Engine Studio. For detailed instructions, see [Grant user access to AES](https://www.servicenow.com/docs/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."). | | In your development instance, add users to the App Engine Studio User Limited group. | Enable developers in your organization to collaborate on applications that someone else created in App Engine Studio. For detailed instructions, see [Grant user access to AES](https://www.servicenow.com/docs/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."). | | Set up collaboration descriptors. | Set up custom collaboration descriptors in the global scope for use in App Engine Studio. For detailed instructions, see [Set up custom collaboration descriptors](https://www.servicenow.com/docs/BA0RtRhCWWpuzRk8z8VUCw "Customize the set of development collaborators you list in App Engine Studio (AES) using Guided Setup."). | | In your non-production instance, specify an app template admin. | Grant the app_template_admin role to users who will manage template activation, deactivation, and sharing in App Engine Studio. For detailed instructions, see [Manage template access](https://www.servicenow.com/docs/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."). | [Table 1. App Engine Studio configuration tasks] {#aes-config-tasks__table_lqq_1qt_rhb} {#aes-config-tasks__table_pdv_qb1_15b__entry__2} | Learn more about AES configuration | Additional ServiceNow resources | |-|-| | ServiceNow provides several additional resources on configuring and administering App Engine Studio. | [https://www.servicenow.com/docs/access?context=app-engine-studio-rn\&version=australia\&pubname=australia-release-notes\&ft:locale=en-US](https://www.servicenow.com/docs/access?context=app-engine-studio-rn&version=australia&pubname=australia-release-notes&ft:locale=en-US) | | ServiceNow provides several additional resources on configuring and administering App Engine Studio. | [ServiceNow Community site](https://community.servicenow.com/community?id=community_search&q=app%20engine%20studio&spa=1) | | ServiceNow provides several additional resources on configuring and administering App Engine Studio. | [App Engine Studio video on adding security](https://www.youtube.com/watch?v=7qdHbzVcmoI&list=PLCOmiTb5WX3ptBi7tdjmAGwx8EhgcTp9o&index=7) | [ ] {#aes-config-tasks__table_pdv_qb1_15b} * **[Add users to the App Engine Admin group](https://www.servicenow.com/docs/5fjJ~hiuoWm1J8ddxiQpBQ)** Add users to the App Engine Admin group in your production instance to give them administrative rights to App Engine Studio (AES). You must also identify a contact email address for the group. After you configure the email address of the App Engine Admin group, members can receive notifications for app development-related requests, including app intake requests. * **[Grant user access to AES](https://www.servicenow.com/docs/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. * **[Manage template access](https://www.servicenow.com/docs/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. * **[Set up custom collaboration descriptors](https://www.servicenow.com/docs/BA0RtRhCWWpuzRk8z8VUCw)** Customize the set of development collaborators you list in App Engine Studio (AES) using Guided Setup.