diff --git a/website/content/en/docs/deployment/add-ons/storage/efs/guide.md b/website/content/en/docs/deployment/add-ons/storage/efs/guide.md
index 6eac2185d2..6acdfc3a1f 100644
--- a/website/content/en/docs/deployment/add-ons/storage/efs/guide.md
+++ b/website/content/en/docs/deployment/add-ons/storage/efs/guide.md
@@ -239,6 +239,11 @@ yq e '.spec.template.spec.volumes[0].persistentVolumeClaim.claimName = env(CLAIM
 kubectl apply -f $GITHUB_STORAGE_DIR/notebook-sample/set-permission-job.yaml
 ```
 
+#### Automated setup default EFS owner  
+The automated setup sets the default Kubeflow Notebook user (Jovyan) as owner of the EFS file system by default.  
+You can always change the `uid` and `gid` used for the setup by passing different parameters to the script.  
+See [Advanced Customization](#advanced-customization) for more details on the different parameters that are available.
+
 ### 3.4 Use existing EFS volume as workspace or data volume for a Notebook
 
 Spin up a new Kubeflow notebook server and specify the name of the PVC to be used as the workspace volume or the data volume and specify your desired mount point. We'll assume you created a PVC with the name `efs-claim` via Kubeflow Volumes UI or via the manual setup step [Static Provisioning](#4-option-2-static-provisioning). For our example here, we are using the AWS Optimized Tensorflow 2.6 CPU image provided in the Notebook configuration options (`public.ecr.aws/c9e4w0g3/notebook-servers/jupyter-tensorflow`). Additionally, use the existing `efs-claim` volume as the workspace volume at the default mount point `/home/jovyan`. The server might take a few minutes to come up.