diff --git a/docs/platform-services/automation-service/automation-service-playbooks.md b/docs/platform-services/automation-service/automation-service-playbooks.md
index b8d4fbcdc1..73ecd9af97 100644
--- a/docs/platform-services/automation-service/automation-service-playbooks.md
+++ b/docs/platform-services/automation-service/automation-service-playbooks.md
@@ -210,10 +210,31 @@ A filter node filters results from the preceding action based on the condition y
## Playbook versioning
-Every time you edit a playbook, a new version of the playbook is saved. In the screen image below, notice how all the versions of the playbook are listed (#4 being the published version as indicated by the publish icon). Click on a version to edit it, and if you want, publish it. In this way, you maintain version control of your playbooks, and ensure that all versions are retained.
+### Autosave
+
+Every time you edit a playbook draft, the draft is automatically saved, and the following notification briefly appears in the lower right corner of the playbook screen:
+
+When the automatic save is complete, the following notification lets you know.
+
+To enable or disable autosave, use [playbook preferences](#playbook-preferences).
+
+### Versions
+
+To publish a playbook so that others may use it, click the publish button at the bottom of the playbook screen.
+
+Every time you publish a playbook, a new version of the playbook is retained. In the screen image below, notice how all the versions of the playbook are listed (#4 being the published version as indicated by the publish icon). Click on a version to edit it, and if you want, publish it. In this way, you maintain version control of your playbooks, and ensure that all versions are retained.
+## Playbook preferences
+
+1. Click the preferences button in the upper-right corner of the screen.
+2. Configure preferences in the **Playbooks Preferences** screen.
+
+### Autosave preference
+
+Select **Enable Autosave for all playbooks** to ensure that while editing a playbook, all changes will be automatically saved to the draft. For more information, see [Autosave](#autosave).
+
## Import and export playbooks
With the mechanism to import and export playbooks, you can move a playbook, along with all its configurations, from one instance to another. The file should be in tar.gz format and adhere to naming conventions.
diff --git a/static/img/platform-services/automation-service/autosave-playbook-1.png b/static/img/platform-services/automation-service/autosave-playbook-1.png
new file mode 100644
index 0000000000..fdb6120d92
Binary files /dev/null and b/static/img/platform-services/automation-service/autosave-playbook-1.png differ
diff --git a/static/img/platform-services/automation-service/autosave-playbook-2.png b/static/img/platform-services/automation-service/autosave-playbook-2.png
new file mode 100644
index 0000000000..e69cc8146c
Binary files /dev/null and b/static/img/platform-services/automation-service/autosave-playbook-2.png differ
diff --git a/static/img/platform-services/automation-service/playbook-preferences-screen.png b/static/img/platform-services/automation-service/playbook-preferences-screen.png
new file mode 100644
index 0000000000..03cd0048ef
Binary files /dev/null and b/static/img/platform-services/automation-service/playbook-preferences-screen.png differ
diff --git a/static/img/platform-services/automation-service/playbook-preferences.png b/static/img/platform-services/automation-service/playbook-preferences.png
new file mode 100644
index 0000000000..dffbe18953
Binary files /dev/null and b/static/img/platform-services/automation-service/playbook-preferences.png differ
diff --git a/static/img/platform-services/automation-service/playbook-publish-button.png b/static/img/platform-services/automation-service/playbook-publish-button.png
new file mode 100644
index 0000000000..7b6a852f68
Binary files /dev/null and b/static/img/platform-services/automation-service/playbook-publish-button.png differ