diff --git a/doc/source/backup/kubernetes/running-restore-playbook-locally-on-the-controller.rst b/doc/source/backup/kubernetes/running-restore-playbook-locally-on-the-controller.rst
index 961204a10..e8e05fdd5 100644
--- a/doc/source/backup/kubernetes/running-restore-playbook-locally-on-the-controller.rst
+++ b/doc/source/backup/kubernetes/running-restore-playbook-locally-on-the-controller.rst
@@ -215,6 +215,27 @@ Below you can find other ``-e`` command line options:
                 -e restore_mode=optimized \
                 -e "@/path/to/restore_overrides.yaml"
 
+``-e restore_extra_items``
+    Enables the restore playbook to extract additional items from the backup
+    during its execution. This is useful when the user has unmanaged files that
+    are not included in a normal restore operation.
+
+    The following is an example of restoring some files that had been manually
+    modified on the system pre-backup:
+
+    .. code-block::
+
+        ansible-playbook /usr/share/ansible/stx-ansible/playbooks/restore_platform.yml \
+          -e "initial_backup_dir=/home/sysadmin" \
+          -e "backup_filename=localhost_platform_backup_2024_08_12_22_58_21.tgz"
+          -e '{"restore_extra_items": ["etc/pam.d/common-auth", "etc/security/group.conf"]}'
+
+    .. note::
+
+        The ``restore_extra_items`` option will restore files only on
+        controller-0. The user must restore files on other nodes after they
+        are reinstalled, if required.
+
 **Legacy**
 
 ``-e skip_patching=true``