What is the best way to move Playbooks to Production instance?

[Jake Sadler]

What is the best way to move Playbooks from development instance to a production instance. Are update sets the best way?

How would non admin users who create and playbooks do this?

[Cheikh Ahmadou · Accepted solution]

Best Practice for Moving Playbooks to Production

1. Use Application Scoping and Source Control (Best Practice)

If you're working in a custom scoped app, the best way is:

Use Application Repository or Source Control to move all Playbook records as part of your app.
This is the most robust way and ideal for team development and repeatable deployments.

2. Use Update Sets

If you're not using application scope or are working in Global scope, then yes — you can use Update Sets, but with caution:

• Some Playbook records are not automatically captured in update sets.

• You must manually capture additional records such as:

  • Related Flow Designer flows

  • Data Lookups

  • Action Configurations

  • Script Includes (if used)

 How to do it properly:

• Set the update set to “Current” before creating or editing Playbooks.

• After changes are complete, review the update set using "Preview" to detect missing dependencies.

• Use "Include Related Records" where needed.
  
  

What About Non-Admin Users?

Non-admin users cannot move update sets or publish to App Repo by default.

To allow them to contribute:

• Give them the admin role temporarily (not recommended in prod).

• OR better: have them create Playbooks in dev, and have a platform admin move them to prod.

• OR: Designate an App Owner or DevOps lead who has permission to manage deployment.

[Cheikh Ahmadou · Accepted solution]

Best Practice for Moving Playbooks to Production

1. Use Application Scoping and Source Control (Best Practice)

If you're working in a custom scoped app, the best way is:

Use Application Repository or Source Control to move all Playbook records as part of your app.
This is the most robust way and ideal for team development and repeatable deployments.

2. Use Update Sets

If you're not using application scope or are working in Global scope, then yes — you can use Update Sets, but with caution:

• Some Playbook records are not automatically captured in update sets.

• You must manually capture additional records such as:

  • Related Flow Designer flows

  • Data Lookups

  • Action Configurations

  • Script Includes (if used)

 How to do it properly:

• Set the update set to “Current” before creating or editing Playbooks.

• After changes are complete, review the update set using "Preview" to detect missing dependencies.

• Use "Include Related Records" where needed.
  
  

What About Non-Admin Users?

Non-admin users cannot move update sets or publish to App Repo by default.

To allow them to contribute:

• Give them the admin role temporarily (not recommended in prod).

• OR better: have them create Playbooks in dev, and have a platform admin move them to prod.

• OR: Designate an App Owner or DevOps lead who has permission to manage deployment.

[Ankur Bawiskar · Accepted solution]

@Jake Sadler 

I recently worked on playbooks and yes Update sets are the only way.

If my response helped please mark it correct and close the thread so that it benefits future readers.

[Ankur Bawiskar]

@Jake Sadler 

Hope you are doing good.

Did my reply answer your question?

If my response helped please mark it correct and close the thread so that it benefits future readers.