Skip to content

Commit ef522ab

Browse files
Add troubleshooting section for email domain change login issues (#4095)
Users who change their email domain (e.g., company rebranding) can't log into Temporal Cloud because OAuth identifies accounts by email address. This adds a troubleshooting section to the users page explaining: - Why this happens (OAuth identity tied to email) - How to resolve (contact support with old/new email) - Prevention tip (use SAML for enterprise identity management) Addresses common user issue reported in community Slack. Co-authored-by: Brian MacDonald <brian.macdonald@temporal.io>
1 parent 9ce902b commit ef522ab

1 file changed

Lines changed: 27 additions & 0 deletions

File tree

  • docs/production-deployment/cloud/get-started

docs/production-deployment/cloud/get-started/users.mdx

Lines changed: 27 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -26,6 +26,7 @@ tags:
2626
- [How to update an account-level Role in Temporal Cloud](#update-roles)
2727
- [How to update Namespace-level permissions in Temporal Cloud](#update-permissions)
2828
- [How to delete a user from your Temporal Cloud account](#delete-users)
29+
- [How to troubleshoot account access issues](#troubleshoot-access)
2930

3031
## How to invite users to your Temporal Cloud account {#invite-users}
3132

@@ -350,3 +351,29 @@ These permissions are configured per Namespace per user.
350351
| ValidateGlobalizeNamespace | | ||
351352

352353
Account Owners and Global Admins will have Namespace Admin permissions on Namespaces.
354+
355+
## How to troubleshoot account access issues {#troubleshoot-access}
356+
357+
### Why can't I sign in after my email domain changed? {#email-domain-change}
358+
359+
If your organization changed its email domain (for example, from `@oldcompany.com` to `@newcompany.com`), you may be unable to sign in to Temporal Cloud with your existing account.
360+
361+
**Why this happens:**
362+
When you sign in using "Continue with Google" or "Continue with Microsoft", Temporal Cloud identifies your account by your email address.
363+
If your email address changes, Temporal Cloud sees this as a different identity and cannot match it to your existing account.
364+
365+
**How to resolve this:**
366+
[Create a support ticket](/cloud/support#support-ticket) with the following information:
367+
368+
- Your previous email address (the one originally used to access Temporal Cloud)
369+
- Your new email address
370+
- Your Temporal Cloud Account Id (if known)
371+
372+
Temporal Support can update your account to use your new email address.
373+
374+
:::tip Use SAML for enterprise identity management
375+
376+
If your organization frequently changes email domains or wants centralized control over user authentication, consider using [SAML authentication](/cloud/saml).
377+
With SAML, your identity provider (IdP) manages user identities, and email domain changes can be handled within your IdP without affecting Temporal Cloud access.
378+
379+
:::

0 commit comments

Comments
 (0)