diff --git a/content/operate/rc/security/access-control/saml-sso/_index.md b/content/operate/rc/security/access-control/saml-sso/_index.md
index fa0096667f..52b86d2422 100644
--- a/content/operate/rc/security/access-control/saml-sso/_index.md
+++ b/content/operate/rc/security/access-control/saml-sso/_index.md
@@ -44,7 +44,7 @@ You can also initiate single sign-on from the [Redis Cloud console](https://clou
 
 1. From the Redis Cloud console's [sign-in screen](https://cloud.redis.io/#/login), select **SSO**.
 
-    {{<image filename="images/rc/button-sign-in-sso.png" width="150px" alt="Sign in with SSO button">}}
+    {{<image filename="images/rc/button-sign-in-sso.png" width="50px" alt="Sign in with SSO button">}}
 
 1. Enter the email address associated with your SAML user account.
 
@@ -100,7 +100,7 @@ Before you set up SAML SSO in Redis Cloud, you must verify that you own the doma
 
     {{<image filename="images/rc/saml-button-add-domain.png" width="120px" alt="Add domain button">}}
 
-1. Enter the domain name and select {{<image filename="images/rc/saml-button-confirm.png#no-click" width="20px" alt="The confirm domain button" class="inline">}} to save it, or select {{<image filename="images/rc/saml-button-cancel.png#no-click" width="20px" alt="The cancel button" class="inline">}} to cancel.
+1. Enter the domain name and select {{<image filename="images/rc/saml-button-confirm.png#no-click" width="20px" alt="Confirm domain" class="inline">}} to save it, or select {{<image filename="images/rc/saml-button-cancel.png#no-click" width="20px" alt="Cancel" class="inline">}} to cancel.
 
     {{<image filename="images/rc/saml-enter-domain.png" width="80%" alt="Enter domain name in the Domain field.">}}
 
@@ -110,12 +110,10 @@ Before you set up SAML SSO in Redis Cloud, you must verify that you own the doma
 
     We'll check the domain's DNS records for the provided TXT record. If the TXT record does not exist or we can't resolve your domain, we won't be able to verify the domain and users with that domain won't be able to sign in using SAML SSO. 
     
-    Select {{<image filename="images/rc/saml-button-delete-domain.png#no-click" width="25px" alt="The delete domain button" class="inline">}} to delete a domain if it was added by mistake.
+    Select {{<image filename="images/rc/saml-button-delete-domain.png#no-click" width="25px" alt="delete domain" class="inline">}} to delete a domain if it was added by mistake.
 
     If we find the TXT record, the domain's status will change to **Verified**.
 
-    {{<image filename="images/rc/saml-domain-verified.png" width="80%" alt="The Manage domain bindings panel, with a verified domain">}}
-
     You can select **Add domain** to add another domain.
 
 1. Select **Close** to close the domain binding panel.
@@ -300,12 +298,10 @@ To see and interact with the Redis Cloud account in the **Unlinked accounts** li
 
 1. Select **Link account**.
 
-    {{<image filename="images/rc/saml/button-saml-link-account.png" alt="The Link Account button">}}
+    {{<image filename="images/rc/saml/button-saml-link-account.png" alt="The Link Account button" width=150px >}}
 
 1. In the **Convert existing users** dialog, select **Confirm conversion** to finish linking the accounts.
 
-    {{<image filename="images/rc/saml/popup-saml-convert-users.png" alt="The Convert users popup">}}
-
 ## Deactivate SAML SSO
 
 Before you can deactivate SAML SSO for an account, you must sign in to the account as a local (non-SAML) user with the owner role assigned.
diff --git a/content/operate/rc/security/access-control/saml-sso/saml-integration-auth0.md b/content/operate/rc/security/access-control/saml-sso/saml-integration-auth0.md
index 82608f72df..b9c79ea205 100644
--- a/content/operate/rc/security/access-control/saml-sso/saml-integration-auth0.md
+++ b/content/operate/rc/security/access-control/saml-sso/saml-integration-auth0.md
@@ -175,16 +175,14 @@ Replace `ID` so it matches the `AssertionConsumerService` Location URL ID (the c
 
     {{<image filename="images/rc/saml/sm_saml_8.png" >}}
 
-   A popup appears, explaining that, in order to test the SAML connection, that we need to login with credentials of a user defined in Auth0.
-
-    {{<image filename="images/rc/saml/sm_saml_9.png" >}}
+   A popup appears, explaining that, in order to test the SAML connection, we need to login with credentials of a user defined in Auth0. Select **Continue** to go to the Auth0 login screen.
 
 1. The Auth0 login screen appears. Enter the credentials and select **Sign In**.
 
     {{<image filename="images/rc/saml/auth0_saml_12.png" >}}
 
-1. If the test has succeeded, you will see the the Redis Cloud console screen. Your local account is now considered a SAML account. To log in to the Redis Cloud console from now on, click on **Sign in with SSO**.
+If everything is configured correctly, you will see the the Redis Cloud console screen. Your local account is now considered a SAML account. 
 
-1. Enter your SAML email and select **Login**. 
+To log in to the Redis Cloud console from now on, click on **Sign in with SSO**.
 
-You have successfully configured SAML as an identification provider.
+{{<image filename="images/rc/button-sign-in-sso.png" width="50px" alt="Sign in with SSO button">}}
diff --git a/content/operate/rc/security/access-control/saml-sso/saml-integration-aws-identity-center.md b/content/operate/rc/security/access-control/saml-sso/saml-integration-aws-identity-center.md
index eeb112c2fe..25ccd9c164 100644
--- a/content/operate/rc/security/access-control/saml-sso/saml-integration-aws-identity-center.md
+++ b/content/operate/rc/security/access-control/saml-sso/saml-integration-aws-identity-center.md
@@ -138,18 +138,14 @@ The final step in our SAML integration with AWS IAM identity Center is to activa
 
    {{<image filename="images/rc/saml/sm_saml_8.png" >}}
 
-  A logout notification screen displays, letting you know that you are redirected to AWS IAM Identity Center's login screen.
-
-   {{<image filename="images/rc/saml/sm_saml_9.png" >}}
+  A logout notification screen displays, letting you know that you will be redirected to your identity provider. Select **Continue** to go to the AWS IAM Identity Center's login screen.
 
 1. Enter your AWS IAM Identity Center credentials.
 
    {{<image filename="images/rc/saml/aws_iam_identity_center_saml_18.png" >}}
 
-1. If everything is configured correctly, you should get a **SAML activation succeeded** message. From this point forward, users need to click **SSO** to sign in to the Redis Cloud console.
-
-   {{<image filename="images/rc/saml/aws_iam_identity_center_saml_19.png" >}}
+If everything is configured correctly, you will see the the Redis Cloud console screen. Your local account is now considered a SAML account. 
 
-  A message displays, stating that your local user is now converted to a SAML user. Select **Confirm**.
+To log in to the Redis Cloud console from now on, click on **Sign in with SSO**.
 
-   You have successfully configured AWS IAM Identity Center as an identification provider.
+{{<image filename="images/rc/button-sign-in-sso.png" width="50px" alt="Sign in with SSO button">}}
\ No newline at end of file
diff --git a/content/operate/rc/security/access-control/saml-sso/saml-integration-azure-ad.md b/content/operate/rc/security/access-control/saml-sso/saml-integration-azure-ad.md
index b0967eeb32..a9a738f5ca 100644
--- a/content/operate/rc/security/access-control/saml-sso/saml-integration-azure-ad.md
+++ b/content/operate/rc/security/access-control/saml-sso/saml-integration-azure-ad.md
@@ -163,23 +163,17 @@ Make sure the **Namespace** field is empty when modifying these claims.
 
     {{<image filename="images/rc/saml/sm_saml_8.png" >}}
 
-1. A popup appears, explaining that you must log in with the credentials of a Microsoft Entra user to test the SAML connection.
-
-    {{<image filename="images/rc/saml/sm_saml_9.png" >}}
+1. A popup appears, explaining that you must log in with the credentials of a Microsoft Entra user to test the SAML connection. Select **Continue** to go to the Microsoft login screen.
 
 1. The Microsoft login screen will appear. Enter the credentials and click **Sign In**.
 
     {{<image filename="images/rc/saml/ad_saml_19.png" >}}
 
-1. If the test has succeeded, you will see the following screen. Your local account is now considered a SAML account. To log in to Redis Cloud console going forward, select **Sign in with SSO**.
-
-    {{<image filename="images/rc/saml/sm_saml_11.png" >}}
-
-1. Enter your SAML email and click **Login**.
+If everything is configured correctly, you will see the the Redis Cloud console screen. Your local account is now considered a SAML account. 
 
-    {{<image filename="images/rc/saml/ad_saml_21.png" >}}
+To log in to the Redis Cloud console from now on, click on **Sign in with SSO**.
 
-   You have successfully configured SAML as an identification provider.
+{{<image filename="images/rc/button-sign-in-sso.png" width="50px" alt="Sign in with SSO button">}}
 
 ## Claim conditions and user groups
 
diff --git a/content/operate/rc/security/access-control/saml-sso/saml-integration-google.md b/content/operate/rc/security/access-control/saml-sso/saml-integration-google.md
index 271ddeb686..8cb9f56dc6 100644
--- a/content/operate/rc/security/access-control/saml-sso/saml-integration-google.md
+++ b/content/operate/rc/security/access-control/saml-sso/saml-integration-google.md
@@ -163,10 +163,8 @@ A logout notification screen displays, letting you know that you are redirected
 
    {{<image filename="images/rc/saml/google_workspace_saml_18.png" >}}
 
-1. If everything is configured correctly, you should get a **SAML activation succeeded** message. From this point forward, users need to click **SSO** to log in to the Redis Cloud console.
+If everything is configured correctly, you will see the the Redis Cloud console screen. Your local account is now considered a SAML account. 
 
-   {{<image filename="images/rc/saml/google_workspace_saml_19.png" >}}
+To log in to the Redis Cloud console from now on, click on **Sign in with SSO**.
 
-A message displays, stating that your local user is now converted to a SAML user. Select **Confirm**.
-
-You have successfully configured Google Workspace as an identification provider.
+{{<image filename="images/rc/button-sign-in-sso.png" width="50px" alt="Sign in with SSO button">}}
diff --git a/content/operate/rc/security/access-control/saml-sso/saml-integration-okta-generic.md b/content/operate/rc/security/access-control/saml-sso/saml-integration-okta-generic.md
index 34f3750f64..5be4f65acb 100644
--- a/content/operate/rc/security/access-control/saml-sso/saml-integration-okta-generic.md
+++ b/content/operate/rc/security/access-control/saml-sso/saml-integration-okta-generic.md
@@ -253,24 +253,14 @@ To activate SAML, you must have a local user (or social sign-on user) with the *
 
     {{<image filename="images/rc/saml/sm_saml_8.png" >}}
 
-    A popup appears, stating that to test the SAML connection, you need to log in with Okta credentials of the user defined in the Redis Cloud group. This user is part of the group to which you assigned the Redis Cloud application.
-
-    {{<image filename="images/rc/saml/sm_saml_9.png" >}}
+    A popup appears, stating that to test the SAML connection, you need to log in with Okta credentials of the user defined in the Redis Cloud group. This user is part of the group to which you assigned the Redis Cloud application. Select **Continue** to go to the Okta login screen.
 
 1. The Okta login screen appears. Enter the credentials and select **Sign In**.
 
     {{<image filename="images/rc/saml/okta_saml_app_int_14.png" >}}
 
-1. If the test succeeds, your local account is now considered a SAML account. To log in to Redis Cloud console going forward, select **Sign in with SSO**.
-
-    {{<image filename="images/rc/saml/sm_saml_11.png" >}}
-
-1. Enter your SAML email and click **Login**.
-
-    {{<image filename="images/rc/saml/okta_saml_app_int_15.png" >}}
-
-1. If only one user is defined in Redis Cloud console, you get a popup window where you select **Confirm** to convert the local user to a SAML user. Consider setting up one more local user other than a SAML user.
+If everything is configured correctly, you will see the the Redis Cloud console screen. Your local account is now considered a SAML account. 
 
-    {{<image filename="images/rc/saml/okta_saml_app_int_16.png" >}}
+To log in to the Redis Cloud console from now on, click on **Sign in with SSO**.
 
-1. You have successfully configured SAML as an identity provider.
+{{<image filename="images/rc/button-sign-in-sso.png" width="50px" alt="Sign in with SSO button">}}
\ No newline at end of file
diff --git a/content/operate/rc/security/access-control/saml-sso/saml-integration-okta-org2org.md b/content/operate/rc/security/access-control/saml-sso/saml-integration-okta-org2org.md
index a711deea0a..e5a87f244d 100644
--- a/content/operate/rc/security/access-control/saml-sso/saml-integration-okta-org2org.md
+++ b/content/operate/rc/security/access-control/saml-sso/saml-integration-okta-org2org.md
@@ -241,20 +241,14 @@ Replace `<ID>` so it matches the AssertionConsumerService Location URL ID (the c
 
     {{<image filename="images/rc/saml/sm_saml_8.png" >}}
 
-   A popup appears, explaining that, to test the SAML connection, you need to log in with Okta credentials of the user defined in the Redis Cloud group. This user is part of the group to which you assigned the Redis Cloud application.
+   A popup appears, explaining that, to test the SAML connection, you need to log in with Okta credentials of the user defined in the Redis Cloud group. This user is part of the group to which you assigned the Redis Cloud application. Select **Continue** to go to the Okta login screen.
 
-    {{<image filename="images/rc/saml/sm_saml_9.png" >}}
-
-1. The Okta log-in screen appears. Enter the credentials and select **Sign In**.
+1. The Okta login screen appears. Enter the credentials and select **Sign In**.
 
     {{<image filename="images/rc/saml/sm_saml_10.png" >}}
 
-1. If the test succeeds, the next screen appears. Your local account is now considered a SAML account. Going forward, to log in to Redis Cloud console, select **Sign in with SSO**.
-
-    {{<image filename="images/rc/saml/sm_saml_11.png" >}}
-
-1. Enter your SAML email and select **Login**
+If everything is configured correctly, you will see the the Redis Cloud console screen. Your local account is now considered a SAML account. 
 
-    {{<image filename="images/rc/saml/sm_saml_12.png" >}}
+To log in to the Redis Cloud console from now on, click on **Sign in with SSO**.
 
-You have successfully configured SAML as an identity provider.
\ No newline at end of file
+{{<image filename="images/rc/button-sign-in-sso.png" width="50px" alt="Sign in with SSO button">}}
\ No newline at end of file
diff --git a/content/operate/rc/security/access-control/saml-sso/saml-integration-ping-identity.md b/content/operate/rc/security/access-control/saml-sso/saml-integration-ping-identity.md
index a8d5af8652..9a41b37591 100644
--- a/content/operate/rc/security/access-control/saml-sso/saml-integration-ping-identity.md
+++ b/content/operate/rc/security/access-control/saml-sso/saml-integration-ping-identity.md
@@ -162,25 +162,19 @@ To activate SAML, you must have a local user (or social sign-on user) with the *
 
 1. Return to the Redis Cloud console and select **Activate**.
 
-    {{<image filename="images/rc/saml/ping_identity_saml_19.png" >}}
+    {{<image filename="images/rc/saml/sm_saml_8.png" >}}
 
-1. A popup appears, explaining that to test the SAML connection, you need to log in with credentials of a user defined in Ping Federate.
-
-    {{<image filename="images/rc/saml/sm_saml_9.png" >}}
+1. A popup appears, explaining that to test the SAML connection, you need to log in with credentials of a user defined in Ping Federate. Select **Continue** to go to the Ping Federate login screen.
 
 1. The Ping Federate login screen will appear. Enter the credentials and select **Sign In**.
 
     {{<image filename="images/rc/saml/ping_identity_saml_20.png" >}}
 
-1. If the test has succeeded, you will see the following screen. Your local account is now considered a SAML account. To log in to Redis Cloud console going forward, select the **Sign in with SSO** button.
-
-    {{<image filename="images/rc/saml/sm_saml_11.png" >}}
-
-1. In the screen, enter your SAML email and select *Login*.
+If everything is configured correctly, you will see the the Redis Cloud console screen. Your local account is now considered a SAML account. 
 
-    {{<image filename="images/rc/saml/ad_saml_21.png" >}}
+To log in to the Redis Cloud console from now on, click on **Sign in with SSO**.
 
-   You have successfully configured SAML as an identity provider.
+{{<image filename="images/rc/button-sign-in-sso.png" width="50px" alt="Sign in with SSO button">}}
 
 ## IdP-initiated SSO
 
diff --git a/content/operate/rc/security/cidr-whitelist.md b/content/operate/rc/security/cidr-whitelist.md
index fecbd952b5..0cd4b55c65 100644
--- a/content/operate/rc/security/cidr-whitelist.md
+++ b/content/operate/rc/security/cidr-whitelist.md
@@ -30,7 +30,7 @@ To define the CIDR allow list for a database:
 
 1. Enter the first IP address (in CIDR format) you want to allow in the text box and then select the check mark to add it to the allow list:
 
-    {{<image filename="images/rc/database-details-configuration-tab-security-cidr-allowlist-add-first-ip.png" width="300px" alt="Add the first IP address to the CIDR allow list." >}}
+    {{<image filename="images/rc/database-details-configuration-tab-security-cidr-allowlist-add-first-ip.png" width="80%" alt="Add the first IP address to the CIDR allow list." >}}
    
 1. To allow additional IP addresses:
 
@@ -38,7 +38,7 @@ To define the CIDR allow list for a database:
 
     1. Enter the new IP address in the text box and then select check to add it to the allow list.
 
-        {{<image filename="images/rc/database-details-configuration-tab-security-cidr-allowlist-add-more-ips.png" width="300px" alt="Add a new IP address to the CIDR allow list." >}}
+        {{<image filename="images/rc/database-details-configuration-tab-security-cidr-allowlist-add-more-ips.png" width="80%" alt="Add a new IP address to the CIDR allow list." >}}
 
 1. Select **Save database** to apply your changes.
 
diff --git a/static/images/rc/access-management-saml-config.png b/static/images/rc/access-management-saml-config.png
index 82c2387ab9..8e20e0a001 100644
Binary files a/static/images/rc/access-management-saml-config.png and b/static/images/rc/access-management-saml-config.png differ
diff --git a/static/images/rc/button-access-management-sso-setup.png b/static/images/rc/button-access-management-sso-setup.png
index 169b8ad76d..e55a133b45 100644
Binary files a/static/images/rc/button-access-management-sso-setup.png and b/static/images/rc/button-access-management-sso-setup.png differ
diff --git a/static/images/rc/button-sign-in-sso.png b/static/images/rc/button-sign-in-sso.png
index 88da667820..f5d401371f 100644
Binary files a/static/images/rc/button-sign-in-sso.png and b/static/images/rc/button-sign-in-sso.png differ
diff --git a/static/images/rc/database-details-configuration-tab-security-cidr-allowlist-add-first-ip.png b/static/images/rc/database-details-configuration-tab-security-cidr-allowlist-add-first-ip.png
index 5eaa50648c..e3ae12476b 100644
Binary files a/static/images/rc/database-details-configuration-tab-security-cidr-allowlist-add-first-ip.png and b/static/images/rc/database-details-configuration-tab-security-cidr-allowlist-add-first-ip.png differ
diff --git a/static/images/rc/database-details-configuration-tab-security-cidr-allowlist-add-more-ips.png b/static/images/rc/database-details-configuration-tab-security-cidr-allowlist-add-more-ips.png
index 49f7a3daff..9c90aa661f 100644
Binary files a/static/images/rc/database-details-configuration-tab-security-cidr-allowlist-add-more-ips.png and b/static/images/rc/database-details-configuration-tab-security-cidr-allowlist-add-more-ips.png differ
diff --git a/static/images/rc/saml-button-add-domain.png b/static/images/rc/saml-button-add-domain.png
index 171a7df54e..86983a4e3f 100644
Binary files a/static/images/rc/saml-button-add-domain.png and b/static/images/rc/saml-button-add-domain.png differ
diff --git a/static/images/rc/saml-button-cancel.png b/static/images/rc/saml-button-cancel.png
index cff6061cd8..e825983113 100644
Binary files a/static/images/rc/saml-button-cancel.png and b/static/images/rc/saml-button-cancel.png differ
diff --git a/static/images/rc/saml-button-close.png b/static/images/rc/saml-button-close.png
index dcb1ffb995..6e6a646474 100644
Binary files a/static/images/rc/saml-button-close.png and b/static/images/rc/saml-button-close.png differ
diff --git a/static/images/rc/saml-button-confirm.png b/static/images/rc/saml-button-confirm.png
index c3f2492726..0934874dc7 100644
Binary files a/static/images/rc/saml-button-confirm.png and b/static/images/rc/saml-button-confirm.png differ
diff --git a/static/images/rc/saml-button-delete-domain.png b/static/images/rc/saml-button-delete-domain.png
index ccec656fa5..cc75975afa 100644
Binary files a/static/images/rc/saml-button-delete-domain.png and b/static/images/rc/saml-button-delete-domain.png differ
diff --git a/static/images/rc/saml-domain-verified.png b/static/images/rc/saml-domain-verified.png
index 6aec04fbf3..646d9118f9 100644
Binary files a/static/images/rc/saml-domain-verified.png and b/static/images/rc/saml-domain-verified.png differ
diff --git a/static/images/rc/saml-enable-button.png b/static/images/rc/saml-enable-button.png
index 253fc6920c..e882f34ea3 100644
Binary files a/static/images/rc/saml-enable-button.png and b/static/images/rc/saml-enable-button.png differ
diff --git a/static/images/rc/saml-enter-domain.png b/static/images/rc/saml-enter-domain.png
index afeb0ae343..cf495adbb2 100644
Binary files a/static/images/rc/saml-enter-domain.png and b/static/images/rc/saml-enter-domain.png differ
diff --git a/static/images/rc/saml-manage-domain-bindings.png b/static/images/rc/saml-manage-domain-bindings.png
index a7615eee1d..e6453e3477 100644
Binary files a/static/images/rc/saml-manage-domain-bindings.png and b/static/images/rc/saml-manage-domain-bindings.png differ
diff --git a/static/images/rc/saml/button-saml-link-account.png b/static/images/rc/saml/button-saml-link-account.png
index af7e9c2a95..6752c8687c 100644
Binary files a/static/images/rc/saml/button-saml-link-account.png and b/static/images/rc/saml/button-saml-link-account.png differ
diff --git a/static/images/rc/saml/popup-saml-get-token.png b/static/images/rc/saml/popup-saml-get-token.png
index 1f768cc99b..adc9da1ffe 100644
Binary files a/static/images/rc/saml/popup-saml-get-token.png and b/static/images/rc/saml/popup-saml-get-token.png differ
diff --git a/static/images/rc/saml/sm_saml_1.png b/static/images/rc/saml/sm_saml_1.png
index 0da240a443..1a72e27b3d 100644
Binary files a/static/images/rc/saml/sm_saml_1.png and b/static/images/rc/saml/sm_saml_1.png differ
diff --git a/static/images/rc/saml/sm_saml_3.png b/static/images/rc/saml/sm_saml_3.png
index 10d6b2ff73..6277d9bf60 100644
Binary files a/static/images/rc/saml/sm_saml_3.png and b/static/images/rc/saml/sm_saml_3.png differ
diff --git a/static/images/rc/saml/sm_saml_8.png b/static/images/rc/saml/sm_saml_8.png
index 51b91b8bed..c75ac14245 100644
Binary files a/static/images/rc/saml/sm_saml_8.png and b/static/images/rc/saml/sm_saml_8.png differ