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

 Release :

    - australia

ft:locale :

    - pt-BR

ft:publication_title :

    - Australia Build or modify applications

ft:clusterId :

    - cadev

bundleId :

    - cadev

workflow :

    - Development, Data, and Analytics


---

# Manage intake requests

# Manage application intake requests {#ariaid-title1}

* Versão de lançamento: Australia
* 
* Atualizado 12 de mar. de 2026
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 min. de leitura

View details of application intake requests submitted by developers in App Engine Studio in the App Engine Management Center (AEMC) dashboard, and approve or reject them.

## Antes de Iniciar

Before application intake requests can be displayed in AEMC, you must confirm that the Application Intake application has been properly configured. For more information, see [Configure Application Intake](https://servicenow-prod.fluidtopics.net/1erz2wJla0W8e6tmOP0~GA "Use the App Engine Studio (AES) Application Intake guided setup to step through the initial configuration of the Application Intake application. Detailed instructions for each step are provided in subsequent sections of the product documentation."). For more information about how to submit application intake requests, see [Submit your idea for app development](https://servicenow-prod.fluidtopics.net/XVRq8AR3koWvrI8PVrGVIA "With your carefully-planned idea in hand, you are ready to submit it through Application Intake for approval and development in App Engine Studio (AES).").

App requests submitted from Creator Studio restricted users are managed on the App tab on the Requests page. For more information, see [Manage app requests from Creator Studio](https://servicenow-prod.fluidtopics.net/UskoZPwcmEF4ReCd8bDapw "View and manage new app requests in App Engine Management Center (AEMC) that users with the Creator Studio Restricted role (sn_creator_studio_restricted_user) submit for apps they want to create.").

Role required: sn_app_eng_notify.app_engine_admin

## Procedimento

1. Navigate to AllApp EngineAdministrationApp Engine Management Center.  
   The AEMC dashboard shows the number of pending application intake requests.  
   Nota:  
   To view a list of all application intake requests, either select the number of requests or select the Requests page.
2. Select an application intake request to review its details.  
   Figura 1. Pending application intake request
3. Return to the Details tab and review the request.  
   Nota:  
   The Administration section includes a Development instance field. Make sure that the development instance the developer intends to use has been selected. Also, if the user isn't defined on that instance, a message displays and you must manually add the user to that instance. For more information, see [Create a user](https://www.servicenow.com/docs/access?context=t_CreateAUser&version=australia&pubname=australia-platform-administration&ft:locale=en-US).
4. Use the Permission type list in the Administration section to select one of the following options for provisioning groups to this application.

   | Permission type | Description |
   | Select group(s) | Option to give one or more of the following groups permission to develop this application. * App Engine Studio User Limited * App Engine Studio Users * Creator Studio Restricted Users * Creator Studio Users {#manage-intake-application-requests__ul_rrv_yfq_vbc} For more information about how to control which groups show up in this list, see [Manage user groups for Application Intake](https://servicenow-prod.fluidtopics.net/A3PCJyT4dEUC8Yyb9RBlVQ "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."). |
   | I will manually provision user | Option to add groups to the application manually. |
   | Do not give requestor permissions | Option not to add any groups to the application at the time of the request. |
   |-|-|

   {#manage-intake-application-requests__choicetable_ok3_pfq_vbc}  
5. Approve or reject the request.
   * If the request is approved, the user is added to the App Engine Studio User group and granted the App Engine Studio User role. The AES User role enables developers to begin creating their application in AES in the approved instance. The user also receives an email notification with a link to the provisioned instance. For more information about the AES User role, see [Components installed with App Engine Studio](https://servicenow-prod.fluidtopics.net/lQOuD92zSPCm6aeo~hYt2g "Several types of components are installed with activation of the App Engine Studio (AES) plugin, including tables and user roles.").
   * If the request is rejected, a rejection email is sent to the user. The user can submit new requests. However, the rejected request can't be edited.
   {#manage-intake-application-requests__choices_hnz_lnf_vsb}