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


---

# Closing requests and app notifications in Creator Studio

# Closing requests and app notifications in Creator Studio {#ariaid-title1}

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

The records that your app creates when a form is completed are not automatically closed, and some notifications are not automatic and must be configured.

## Closing requests generated by Creator Studio apps {#creator-studio-closing-requests-and-notifications__section_xjz_dlf_p1c}

After an app's automation is done and the request is fulfilled, users must manually close the request record in the Request App Workspace. When fulfillers manually close the request, the ServiceNow AI Platform emails the person who made the request to notify them that the request is closed.

Additionally, you can create a playbook in the app to automatically email the requester when their request is closed. For more information, see [Add activities to an app's playbook in Creator Studio](https://servicenow-prod.fluidtopics.net/OM8G1brxpfBAO~nPDBgBig "Add activities to an app's playbook to specify what the automation does to the designated record type. An activity defines what actually happens when a playbook executes.").

## Default notifications for apps built with Creator Studio {#creator-studio-closing-requests-and-notifications__section_jbg_5sk_p1c}

Apps created in Creator Studio send the following notifications by default.{#creator-studio-closing-requests-and-notifications__table_dtn_ltk_p1c__entry__3}

| Event | Recipient | Trigger |
|-|-|-|
| Request opened | User who opened the request from the app | Record in the app's Task table or underlying table is created. |
| Request assigned to user | User the request is assigned to | Record in the app's Task table or underlying table is created or updated. |
| Request assigned to group | All users in the group that the request is assigned to | Record in the app's Task table or underlying table is created or updated. |
| Request closed\* | User who opened the request | Record is updated any closed state, such as Complete or Cancelled. |
[Table 1. Default app notifications]

{#creator-studio-closing-requests-and-notifications__table_dtn_ltk_p1c}\*Remember, request records must be manually closed.

For more information on notifications from the ServiceNow AI Platform, see [Receive notifications](https://www.servicenow.com/docs/access?context=c_ReceiveNotifications&version=yokohama&pubname=yokohama-build-workflows&ft:locale=en-US).

## Notifications Creator Studio sends about building apps {#creator-studio-closing-requests-and-notifications__section_fpp_nqd_r1c}

{#creator-studio-closing-requests-and-notifications__table_fz1_pqd_r1c__entry__2}

| Event | Recipient |
|-|-|
| A Creator Studio Restricted User submits a new app request | App Engine Admin group |
| The requested app is approved and created by the admin | Creator Studio Restricted User who requested app creation |
| The app creation request has been fulfilled | App Engine Admin group |
[Table 2. Default app notifications]

{#creator-studio-closing-requests-and-notifications__table_fz1_pqd_r1c}