diff --git a/docs/user-guide/ref-architecture-aws/features/sso/configuration.md b/docs/user-guide/ref-architecture-aws/features/sso/configuration.md
index 3543112c..13ea15b6 100644
--- a/docs/user-guide/ref-architecture-aws/features/sso/configuration.md
+++ b/docs/user-guide/ref-architecture-aws/features/sso/configuration.md
@@ -73,8 +73,6 @@ Once the project has been set up to use SSO, the profiles that AWS CLI will use
 
 To do this, simply run `leverage aws configure sso`.
 
-This step needs to be performed every time the user works in a new account that assumes a different role than the one that they are currently using. For example, if the user is working in the `security` account, assuming the `DevOps` role, but needs to operate on a layer of the `management` account which requires assuming an `Administrator` role, then SSO needs to be reconfigured.
-
 !!! warning "Attention"
     This step simply writes over the credentials files for AWS CLI without asking for confirmation from the user. So it's recommended to backup/wipe old credentials before executing this step in order to avoid loss of credentials or conflicts with profiles having similar names to the ones generated by Leverage.