chore(docs): automated cloud documentation update

Author: shahednasser

www/apps/cloud/app/environments/long-lived/page.mdx

@@ -291,21 +291,18 @@ You can't change the branch of preview environments. This section only applies t
 
 </Note>
 
-In an environment's "Settings" tab, you can manage the deployment rules for the environment. Deployment rules allow you to control how and when deployments are triggered for the environment.
+In an environment's **Settings** tab, the **Deployment Rules** section lets you manage the branch the environment deploys from and configure conditions that control when deployments are triggered.
 
-To change the branch associated with an environment using deployment rules:
+To change the branch associated with an environment:
 
-1. In the [environment's dashboard](#open-environment-dashboard), click on the "Settings" tab.
-2. Choose the "Deployment rules" tab from the sidebar.
-3. Click the <InlineIcon Icon={EllipsisHorizontal} alt="three-dots" /> icon at the right side of the `branch` rule.
-4. Choose "Edit" from the dropdown menu.
-5. In the side window that opens, you can change the branch associated with the environment.
-6. Once you're done, click the "Save" button.
+1. In the [environment's dashboard](#open-environment-dashboard), click on the **Settings** tab.
+2. Choose **Deployment Rules** from the sidebar.
+3. In the **Linked Branch** section, click the pencil icon next to the current branch name.
+4. In the drawer that opens, enter the new branch name in the **Branch** field.
+5. Click **Save**.
 
 Changes will take effect the next time you push a commit to the new branch. The environment will be redeployed with the latest changes from the new branch.
 
-![Change environment branch in the environment's settings tab](https://res.cloudinary.com/dza7lstvk/image/upload/v1750170517/Cloud/CleanShot_2025-06-17_at_17.28.25_2x_nfx79a.png)
-
 ---
 
 ## Import and Export Environment's Database Dump

www/apps/cloud/app/environments/preview/page.mdx

@@ -151,11 +151,16 @@ For example, you can define environment variables that are common to all preview
 
 To manage the shared settings for preview environments:
 
-1. In a [project's dashboard](../../projects/page.mdx#open-project-dashboard), click on the "Settings" tab.
-2. Choose the "Previews" tab from the sidebar.
-3. In the Previews settings, you can:
-    - Manage environment variables, as explained in the [Manage Environment Variables](../environment-variables/page.mdx) guide. All preview environments created after making changes will inherit these variables.
-    - Specify which database to create the preview environment's database from. By default, a new database will be created from the Production environment's database. You can change this to use a different environment's database, such as Staging.
+1. In a [project's dashboard](../../projects/page.mdx#open-project-dashboard), click on the **Settings** tab.
+2. Choose **Previews** from the sidebar.
+3. Click on the **Backend** tab.
+
+In the Backend tab, you can configure the following:
+
+- **Provisioning Rules**: Define conditions that control when a preview environment is provisioned for a pull request. Available fields are **author**, **branch name**, **title**, **description**, and **label**. Use the **is**, **is not**, or **contains** operators and combine conditions with AND/OR logic. Click **Save** to apply changes.
+- **Deploy Rules**: Define conditions that control when a provisioned preview environment is deployed. Available fields are **author** and **commit message**. Use the same operators and logic options as provisioning rules. Click **Save** to apply changes.
+- **Environment variables**: Manage environment variables shared across all preview environments, as explained in the [Manage Environment Variables](../environment-variables/page.mdx) guide. All preview environments created after making changes will inherit these variables.
+- **Database base branch**: Specify which environment's database to create the preview environment's database from. By default, a new database is created from the Production environment's database. You can change this to use a different environment's database, such as Staging.
 
 <Note>
 

www/apps/cloud/generated/edit-dates.mjs

@@ -13,8 +13,8 @@ export const generatedEditDates = {
   "app/update-medusa/page.mdx": "2026-01-08T08:54:50.149Z",
   "app/connect-storefront/page.mdx": "2026-01-08T08:50:31.830Z",
   "app/environments/environment-variables/page.mdx": "2026-07-14T15:49:50.427Z",
-  "app/environments/long-lived/page.mdx": "2026-06-18T13:40:26.814Z",
-  "app/environments/preview/page.mdx": "2026-05-20T13:20:57.494Z",
+  "app/environments/long-lived/page.mdx": "2026-07-27T15:27:12.712Z",
+  "app/environments/preview/page.mdx": "2026-07-27T15:27:45.446Z",
   "app/faq/page.mdx": "2026-04-14T10:44:08.191Z",
   "app/billing/page.mdx": "2026-07-24T15:42:16.652Z",
   "app/usage/page.mdx": "2026-04-10T10:22:15.211Z",