---
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


---

# Manage collaboration requests

# Manage collaboration requests {#ariaid-title1}

* Release version: Yokohama
* 
* Updated January 30, 2025
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 1 minute to read

As an admin, view and approve or reject collaboration requests in the App Engine Management Center (AEMC) from developers who want assistance building their applications.

## Before you begin

To view collaboration requests in AEMC, you must first set up Pipelines and Deployments in your production instance. Otherwise, requests are created on the instance where they originated (that is, the instance with App Engine Studio (AES) installed).

Role required: sn_app_eng_notify.app_engine_admin

## About this task

Developers with collaboration permissions can access and develop certain parts of an application. Requests for collaboration may come from App Engine Studio or Creator Studio.  
Requests from collaborators may be approved automatically depending on permissions or roles they already have.

* For AES collaboration requests, users who have the AES User role are approved automatically.
* Creator Studio users who have already created an app (or have had one created for them) have delegated development permissions, and are automatically approved to collaborate on other apps.
* Current delegated developers without the Creator Studio User or Creator Studio Restricted User roles are automatically approved to collaborate in Creator Studio.

{#manage-collaboration-requests__ul_nj4_13w_2bc}For more information about managing collaboration and permissions, see [Collaborate with other developers](https://servicenow-prod.fluidtopics.net/q~qVPcU2przcaLzG_VkTGA#aes-collaboration-feature-overview "In App Engine Studio (AES), you can add or remove users and groups to be collaborators on an application.").

## Procedure

1. Navigate to AllApp EngineAdministrationApp Engine Management Center.  
   The AEMC dashboard shows the number of
   pending collaboration requests.  
   Note:  
   To view a list of all collaboration requests, either select the number of requests or select the Requests page.
2. Select a collaboration request to review its details.  
   Figure 1. Pending collaboration request record
3. Return to the Details tab and review the request.
4. Approve or reject the request.
   * If the request is approved, the user invited to be a collaborator is added as a developer to the specified app. The collaborator can now work on the parts of the app defined in the Collaboration Descriptor, but cannot concurrently develop other apps in AES. For more information about the AES User role, see [Components
     installed with App Engine Studio](https://servicenow-prod.fluidtopics.net/pMNnpM5gv9AWUBD2KlkwLA "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, the request is closed, and the primary developer is notified by email.
   {#manage-collaboration-requests__choices_kdm_fhg_vsb}

*[\>]: and then