--- sourceDocument: Yokohama Build or modify applications sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/yokohama/application-development Release : - yokohama ft:locale : - en-US ft:publication_title : - Yokohama Build or modify applications ft:clusterId : - cadev bundleId : - cadev workflow : - Development, Data, and Analytics --- # Application Intake configuration tasks # Application Intake configuration tasks {#ariaid-title1} * Release version: Yokohama * * Updated January 30, 2025 * * ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read As you work through the App Engine Studio (AES) Application Intake guided setup, you must perform different configuration tasks.{#app-intake-config-tasks__otherprops-integration-2} ## Activating and configuring the intake request process, and setting up development environments {#app-intake-config-tasks__section_app_intake} The tasks for configuring Application Intake are listed below, along with links to detailed instructions for completing them. {#app-intake-config-tasks__table_lqq_1qt_rhb__entry__2} | Task | Description | |-|-| | Activate the catalog item where developers will submit their application ideas | Activate the Apply for Citizen Development catalog item so that citizen developers can submit their ideas for applications. For detailed instructions, see [Activate the Apply for Citizen Development catalog item](https://servicenow-prod.fluidtopics.net/NKlNip_vdId_DYzJJpPEbw "Enable citizen developers to submit their ideas for applications by activating the Apply for Citizen Development catalog item. This is the first step in configuring the App Engine Studio (AES) Application Intake app."). | | Set up the Apply for Citizen Development catalog item | For quick setup and use, use the predefined Apply for Citizen Development catalog item in Catalog Builder. To customize your app intake form, either update the Apply for Citizen Development catalog item, or use the AES App Intake template as a starting point and add questions and fields as needed. For detailed instructions, see [Customize the App Intake form in Catalog Builder](https://servicenow-prod.fluidtopics.net/sFAT~nJRU~BSfdqf9CJbKw#customize-app-intake-form-catalog-builder "Create a custom app intake experience for your organization by editing the fields and questions on the App Engine Studio (AES) App Intake form in Catalog Builder."). | | Add users to the App Engine Admins group | Add users to the App Engine Admin group. After the email address of the App Engine Admin group is configured, members can receive notifications for app development-related requests, including application intake requests. Note: If you already added users on the production instance using [AES guided setup](https://servicenow-prod.fluidtopics.net/l1TBZvK7Q08EizUIaJaX4g "App Engine Studio (AES) guided setup provides a sequence of tasks that help you configure AES on your ServiceNow instance.") or [Configure Pipelines and Deployments](https://servicenow-prod.fluidtopics.net/FeMXIgTasnIaAvr5457m9A "Use the App Engine Studio (AES) Pipelines and Deployments guided setup to step through the initial configuration of Pipelines and Deployments. Detailed instructions for each step are provided in subsequent sections of the product documentation.") guided setup, you can skip this step. For detailed instructions, see [Add users to the App Engine Admin group](https://servicenow-prod.fluidtopics.net/dtM3thE6B5fF7VJQ~5o70w "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."). | | Create development environment records | On your production instance, create an environment record of type "Development" for each development instance that you want to provision users to. This will allow your production instance to connect to your development instances. Note: If these records have already been set up in the Pipelines and Deployments Guided Setup, you can skip this step. For detailed instructions, see [Configure your pipeline environments](https://servicenow-prod.fluidtopics.net/hJxuurdVY0ikEtekdvTA3Q "Set up your App Engine Studio (AES) production and non-production (for example, development, test, and/or staging) environments by adding the URLs and credentials used to access each instance."). | [Table 1. Application Intake configuration tasks] {#app-intake-config-tasks__table_lqq_1qt_rhb} When you have completed Application Intake guided setup, proceed to [Pipelines and Deployments guided setup](https://servicenow-prod.fluidtopics.net/FeMXIgTasnIaAvr5457m9A "Use the App Engine Studio (AES) Pipelines and Deployments guided setup to step through the initial configuration of Pipelines and Deployments. Detailed instructions for each step are provided in subsequent sections of the product documentation.") to fully configure App Engine Studio. * **[Activate the Apply for Citizen Development catalog item](https://servicenow-prod.fluidtopics.net/NKlNip_vdId_DYzJJpPEbw)** Enable citizen developers to submit their ideas for applications by activating the Apply for Citizen Development catalog item. This is the first step in configuring the App Engine Studio (AES) Application Intake app. * **[Customize the App Intake form in Catalog Builder](https://servicenow-prod.fluidtopics.net/sFAT~nJRU~BSfdqf9CJbKw#customize-app-intake-form-catalog-builder)** Create a custom app intake experience for your organization by editing the fields and questions on the App Engine Studio (AES) App Intake form in Catalog Builder. * **[Manage user groups for Application Intake](https://servicenow-prod.fluidtopics.net/Z_KQy_0RTnDEI5_Ug8v8~Q)** Control which user groups are available for admins to give Creator Studio and App Engine Studio app development permissions to during the Application Intake process. These groups are managed on the User Groups Permission Types \[sn_app_intake_permission_type\] table.