diff --git a/docs/operator/use-cases/velero-backup-restoration.md b/docs/operator/use-cases/velero-backup-restoration.md
index 1c9ca83e..1ff91a96 100644
--- a/docs/operator/use-cases/velero-backup-restoration.md
+++ b/docs/operator/use-cases/velero-backup-restoration.md
@@ -16,4 +16,12 @@ In case of a data loss, the right thing to do is to restore the cluster with **V
 ./velero-restore.sh --kubeconfing /path/to/your/kubeconfig restore
 ```
 
-Running this command, we are going to patch the tenant's namespaces manifests that are actually `ownerReferences`-less. Once the command has finished its run, you got the cluster back.
\ No newline at end of file
+Running this command, we are going to patch the tenant's namespaces manifests that are actually `ownerReferences`-less. Once the command has finished its run, you got the cluster back.
+
+Additionally you can also specify a selected range of tenants to be restored:
+
+```bash
+./velero-restore.sh --tenant "gas oil" restore
+```
+
+In this way, only the tenants **gas** and **oil** will be restored.
\ No newline at end of file