Redis Cloud does not currently provide a self-service option to change the email address associated with an existing account. To update an email, you must add the new email as a user, transfer ownership and access, reconfigure security settings, and then remove or downgrade the original account.
This process ensures uninterrupted access to databases, billing, and team management.
Applies to
Redis Cloud (all plans)
Key Considerations
Email addresses cannot be modified on an existing account
Ownership must be transferred before removing the original user
Billing and notifications must be updated manually
MFA, API tokens, and integrations do not transfer automatically. Review API tokens, service accounts, and integrations to determine whether they must be recreated or updated for the new user.
Removing the original user too early may result in loss of access
Procedure
Step 1: Add the New Email Address
Sign in to the Redis Cloud Console using a user with Owner permissions
From the left navigation panel, click Access Management
On the Team page, click the Add new user button (+ icon) in the upper-right corner
Enter the name and new email address
Assign the appropriate role:
Recommended: Owner (if this user will replace the current owner)
Click Add user
Step 2: Accept the Invitation
Open the inbox for the new email address
Locate the Redis Cloud invitation email
Click the invitation link
Set a password and complete account setup
Step 3: Confirm Owner Access
Return to Access Management → Team
Locate the new user
Ensure the role is set to Owner
Update the role if necessary
Step 4: Validate Access
Log in as the new user and confirm:
All databases are visible and accessible
Team members can be managed
Billing settings can be accessed
Administrative actions are available
Step 5: Update Billing and Notifications
Navigate to Billing
Update billing ownership (if applicable)
Update all notification and alert email addresses
Note: Billing configuration may vary depending on account type (direct vs marketplace).
Step 6: Recreate Security and Integrations
Reconfigure the following for the new account:
Multi-Factor Authentication (MFA)
API tokens
Service accounts (if applicable)
External integrations (CI/CD, monitoring, automation tools)
Update any external systems to use credentials from the new account.
Step 7: Remove or Downgrade the Old User
Once the new account is fully validated:
Log in as the new user
Go to Access Management → Team
Locate the original user
Either:
Remove the user, or
Downgrade their role (recommended temporarily for rollback safety)
Validation Checklist
| Before removing the old account, confirm: | Details |
|---|---|
| Owner access | The new user has the Owner role. |
| Billing access | Billing access is updated and verified. |
| Database access | All databases are visible and accessible from the new account. |
| MFA | MFA is enabled on the new account. |
| API tokens and integrations | API tokens are recreated and integrations are working. |
| Notifications | Alerts and notifications are routed to the new email address. |
| Automation dependencies | No automation, CI/CD, monitoring, or external systems depend on the old account. |
Troubleshooting
New user cannot access billing
Ensure the user has the Owner role and billing ownership has been updated.
Integrations fail after migration
Recreate API tokens and update all dependent systems.
Missing access to resources
Verify the new user has the correct role and organization access.
Lost access after removing old user
This may occur if ownership or billing was not fully transferred. Contact Redis Support.
Additional Notes
There is no supported method to directly edit an email address on an existing account
This is the recommended approach for changing account email ownership in Redis Cloud.
Keeping the old user temporarily (downgraded) is recommended until validation is complete
If your organization uses SSO/SAML authentication, user management and email identity may be controlled by your identity provider (IdP). Coordinate with your organization administrator before making changes.
0 comments
Please sign in to leave a comment.