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


---

# Activate a playbook in Creator Studio

# Activate a playbook 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

Activating a playbook means that it will run when its related form is created or updated on your non-production, development instance. However, the app must still be deployed to production.

## Before you begin

You must resolve any errors in the playbook before you can activate it.

To activate a playbook, you must be given permission to work on the app.

## About this task

You can check the activation status of a playbook at any time in the app header.  
Figure 1. Playbook activation status

If you don't activate a playbook and its app is deployed to production, the automation won't run on the applicable records. However, your App Engine admin can activate the deployed playbook for you.

## Procedure

1. Go to AllApp EngineCreator Studio to see all the apps on the Creator Studio home page.
2. Open the app that contains the playbook you want to activate.
3. Select the form that contains the playbook that you want to activate.
4. Select the automation that contains the playbook that you want to activate.  
   Figure 2. Select automation that has the playbook
5. Select the Activate button.  
   Figure 3. Activate the playbook ![Select the Activate button to activate the playbook]()

## Result

The status displayed in the app header updates from Inactive to Saving to Active, informing you of when changes are made.

The playbook is ready to be deployed with your app. Once the app is deployed, the form is available in the associated service catalog. If the form's app hasn't been deployed, you need to deploy it.

*[\>]: and then