ibexa · mnocon · May 23, 2025 · May 21, 2025 · May 21, 2025 · May 22, 2025
diff --git a/docs/getting_started/first_steps.md b/docs/getting_started/first_steps.md
@@ -33,7 +33,7 @@ module.exports = [ eZConfig, ibexaConfig, ...customConfigs ];
 
 ## Add a content type
 
-1\. In your browser, go to the back office: `<your_domain>/admin`, and use the default credentials to log in: `admin/publish`.
+1\. In your browser, go to the back office: `<your_domain>/admin`, and log in with the default username: `admin` using the password specified during installation.
 
 !!! caution "Password change"
 

diff --git a/docs/getting_started/install_ibexa_dxp.md b/docs/getting_started/install_ibexa_dxp.md
@@ -273,6 +273,20 @@ php bin/console ibexa:graphql:generate-schema
 
 Before executing the command make sure that the database user has sufficient permissions.
 
+The installer will prompt you for a new password for the `admin` user.
+Make sure to use a [strong password](security_checklist.md#strong-passwords) meeting all the [password rules](passwords.md#password-rules).
+
+!!! note
+
+	In scenarios where entering the new password isn't possible, for example, in automated deployments and Continuous Integration environments, use the `--no-interaction` option to skip changing the password and keep the default one, `publish`:
+
+    ``` bash
+    php bin/console ibexa:install --no-interaction
+    php bin/console ibexa:graphql:generate-schema
+    ```
+
+    If doing so, [modify the password for the `admin` user](update_basic_user_data.md#change-password) before [going live with your project](security_checklist.md).
+
 ### Run post-installation script
 
 Run the post-installation script with the following command:

diff --git a/docs/infrastructure_and_maintenance/security/security_checklist.md b/docs/infrastructure_and_maintenance/security/security_checklist.md
@@ -319,3 +319,4 @@ to receive notifications when a security fix is released in a GitHub-hosted depe
 - Enable logging for [[= product_name =]], the web server, any frontend proxies, and the database.
 - Monitor the logs for unusual and suspicious activity. Consider using log monitoring software to make this easier.
 - Consider using different accounts for manual administrative tasks and for the day-to-day running of your installation. You could for instance configure [[= product_name =]] to use a different database user than the one you use during upgrades. This can make it easier to filter out noise in your log monitoring solution.
+
diff --git a/docs/tutorials/beginner_tutorial/2_create_the_content_model.md b/docs/tutorials/beginner_tutorial/2_create_the_content_model.md
@@ -33,7 +33,7 @@ More than one Ride can visit the same Landmark, so it's similar to an N-N relati
 
 In this step you add the first content type, Ride.
 
-Go to the admin interface (`<yourdomain>/admin`) and log in with the default username: `admin` and the default password: `publish`. 
+Go to the admin interface (`<yourdomain>/admin`) and log in with the default username: `admin` using the password specified during installation.
 
 In the upper-right corner, click the avatar icon to unfold the drop-down menu and disable the [Focus mode]([[= user_doc =]]/getting_started/discover_ui/#focus-mode).
 

diff --git a/docs/tutorials/generic_field_type/5_add_a_field.md b/docs/tutorials/generic_field_type/5_add_a_field.md
@@ -5,7 +5,7 @@ description: Learn how to use your custom field type by adding a field to a cont
 # Step 5 - Add a new Point 2D field
 
 All actions in this step are done in the admin interface also called the back office.
-Go to the admin interface (`<yourdomain>/admin`) and log in with the default username: `admin` and the default password: `publish`.
+Go to the admin interface (`<yourdomain>/admin`) and log in with the default username: `admin` using the password specified during installation.
 
 ## Add new content type
 

diff --git a/docs/tutorials/page_and_form_tutorial/1_get_a_starter_website.md b/docs/tutorials/page_and_form_tutorial/1_get_a_starter_website.md
@@ -15,7 +15,7 @@ Get it by following the [Install Ibexa DXP](install_ibexa_dxp.md) guide.
 
 ## Add content types
 
-Log in to the back office – add `/admin` to your installation's address (`<yourdomain>/admin`) and log in using `admin` as the login and `publish` as the password.
+Log in to the back office – add `/admin` to your installation's address (`<yourdomain>/admin`) and log in as `admin` user using the password specified during installation.
 Disable the Focus mode, go to content types screen and (under the content category) add two content types with the following settings:
 
 ### Dog Breed
Original file line number	Diff line number	Diff line change
Expand Up		@@ -319,3 +319,4 @@ to receive notifications when a security fix is released in a GitHub-hosted depe
		- Enable logging for [[= product_name =]], the web server, any frontend proxies, and the database.
		- Monitor the logs for unusual and suspicious activity. Consider using log monitoring software to make this easier.
		- Consider using different accounts for manual administrative tasks and for the day-to-day running of your installation. You could for instance configure [[= product_name =]] to use a different database user than the one you use during upgrades. This can make it easier to filter out noise in your log monitoring solution.