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


---

# Approve a collaboration request

# Approve a collaboration request {#ariaid-title1}

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

Admins and App Engine admin can review and approve (or reject) people's requests to join an app's development in Creator Studio.

## Before you begin

If you have a controller instance configured, you must approve collaboration requests on your controller instance, not the non-production instance with Creator Studio. The controller instance is typically the production instance, but it can vary depending on how your Pipelines and Deployments application is configured. For more information, see [Configure your controller instance](https://servicenow-prod.fluidtopics.net/GyaTyaBJjFilz0QcAFAv0g "You must identify one of the instances in your App Engine Studio (AES) pipeline as the controller instance. All communication between the instances in your pipeline, including the deployment order for applications in the pipeline, takes place in the controller instance.").

Role required: app_engine_admin

## About this task

Note:  
Users with a delegated developer role are automatically approved for collaboration.

## Procedure

1. Navigate to AllApp EngineCollaborationCollaboration Tasks.
2. Select the collaboration request in the Number column of the collaboration table.  
   You can search or filter on the App name or Invitee name columns to find the request faster.
3. Update the approval status in the State field.
   * Closed -- Approved
   * Closed -- Rejected
   * Canceled
   * Closed -- Failed
   {#approve-collaboration-request__choices_sbl_wcf_n1c}
4. Update the record to save your changes.

*[\>]: and then