diff --git a/manifest.toml b/manifest.toml
index c67dd9a..9e958e2 100644
--- a/manifest.toml
+++ b/manifest.toml
@@ -19,7 +19,7 @@ admindoc = "https://vikunja.io/docs/"
 code = "https://kolaente.dev/vikunja/vikunja"
 
 [integration]
-yunohost = ">= 11.2.18"
+yunohost = ">= 11.2.20"
 helpers_version = "2.1"
 architectures = "all"
 multi_instance = true
diff --git a/scripts/change_url b/scripts/change_url
index 7c11dd8..936ddb3 100644
--- a/scripts/change_url
+++ b/scripts/change_url
@@ -34,8 +34,6 @@ domain="$new_domain"
 path="$new_path"
 ynh_config_add --template="config.yml" --destination="$install_dir/config.yml"
 
-#REMOVEME? Assuming the file is setup using ynh_config_add, the proper chmod/chowns are now already applied and it shouldn't be necessary to tweak perms | chmod 600 "$install_dir/config.yml"
-
 #=================================================
 # START SYSTEMD SERVICE
 #=================================================
diff --git a/scripts/install b/scripts/install
index fd5b202..ba6ae41 100644
--- a/scripts/install
+++ b/scripts/install
@@ -46,8 +46,7 @@ executable="$(find $install_dir -name "vikunja-*" \! -name "*.sha256")"
 mv "$executable" "$install_dir/vikunja"
 
 chmod +x "$install_dir/vikunja"
-#REMOVEME? Assuming the install dir is setup using ynh_setup_source, the proper chmod/chowns are now already applied and it shouldn't be necessary to tweak perms | chmod -R o-rwx "$install_dir"
-#REMOVEME? Assuming the install dir is setup using ynh_setup_source, the proper chmod/chowns are now already applied and it shouldn't be necessary to tweak perms | chown -R $app:www-data "$install_dir"
+
 #=================================================
 # ADD A CONFIGURATION
 #=================================================
@@ -55,9 +54,6 @@ ynh_script_progression "Adding $app's configuration..."
 
 ynh_config_add --template="config.yml" --destination="$install_dir/config.yml"
 
-#REMOVEME? Assuming the file is setup using ynh_config_add, the proper chmod/chowns are now already applied and it shouldn't be necessary to tweak perms | chmod 400 "$install_dir/config.yml"
-#REMOVEME? Assuming the file is setup using ynh_config_add, the proper chmod/chowns are now already applied and it shouldn't be necessary to tweak perms | chown "$app:$app" "$install_dir/config.yml"
-
 #=================================================
 # SYSTEM CONFIGURATION
 #=================================================
diff --git a/scripts/restore b/scripts/restore
index b25afff..0cb6f49 100644
--- a/scripts/restore
+++ b/scripts/restore
@@ -10,8 +10,6 @@ ynh_script_progression "Restoring $app main directory..."
 
 ynh_restore "$install_dir"
 
-#REMOVEME? Assuming the install dir is setup using ynh_setup_source, the proper chmod/chowns are now already applied and it shouldn't be necessary to tweak perms | chmod -R o-rwx "$install_dir"
-#REMOVEME? Assuming the install dir is setup using ynh_setup_source, the proper chmod/chowns are now already applied and it shouldn't be necessary to tweak perms | chown -R "$app:www-data" "$install_dir"
 #=================================================
 # RESTORE THE POSTGRESQL DATABASE
 #=================================================
diff --git a/scripts/upgrade b/scripts/upgrade
index 739b597..385371f 100644
--- a/scripts/upgrade
+++ b/scripts/upgrade
@@ -99,8 +99,7 @@ executable="$(find $install_dir -name "vikunja-*" \! -name "*.sha256")"
 mv "$executable" "$install_dir/vikunja"
 
 chmod +x "$install_dir/vikunja"
-#REMOVEME? Assuming the install dir is setup using ynh_setup_source, the proper chmod/chowns are now already applied and it shouldn't be necessary to tweak perms | chmod -R o-rwx "$install_dir"
-#REMOVEME? Assuming the install dir is setup using ynh_setup_source, the proper chmod/chowns are now already applied and it shouldn't be necessary to tweak perms | chown -R $app:www-data "$install_dir"
+
 #=================================================
 # UPDATE A CONFIG FILE
 #=================================================
@@ -108,9 +107,6 @@ ynh_script_progression "Updating $app's configuration files..."
 
 ynh_config_add --template="config.yml" --destination="$install_dir/config.yml"
 
-#REMOVEME? Assuming the file is setup using ynh_config_add, the proper chmod/chowns are now already applied and it shouldn't be necessary to tweak perms | chmod 400 "$install_dir/config.yml"
-#REMOVEME? Assuming the file is setup using ynh_config_add, the proper chmod/chowns are now already applied and it shouldn't be necessary to tweak perms | chown $app:$app "$install_dir/config.yml"
-
 #=================================================
 # REAPPLY SYSTEM CONFIGURATIONS
 #=================================================