Accidentally unsubscribed to Web3auth developer login

Embedded Wallets (Web3Auth)
1

I was using a google group email for the developer account, dev@cypherd.io and now I am getting the codes to login, please help me resolve the issue asap.

2

It sounds like access to your project’s MetaMask Embedded Wallets Developer Dashboard account was affected by the Google Group/mail subscription change. Dashboard access is tied to the Google identity that created the project (or was invited to it), so this isn’t something that can be adjusted from the SDK side.

A few things to check first:

  1. Confirm whether dev@cypherd.io is still a functioning Google identity capable of completing Google sign-in on its own, or whether it’s just a Google Group alias that forwards mail. Group aliases often lose the ability to complete Google sign-in once forwarding or membership changes.
  2. Sign in at https://dashboard.web3auth.io using the exact Google account that originally created or was invited to the project.
  3. If another owner or admin on your team still has dashboard access, they can invite an active developer Google account to the project so you regain access without delay.

To help us narrow this down further here in the Builder Hub, please reply with:

  • the exact error or behavior you see after entering the verification code;
  • whether dev@cypherd.io is an individual Google Workspace user or a Google Group alias;
  • whether any other dashboard owner/admin still has access;
  • your project Client ID, if available.

Please don’t share passwords, private keys, or seed phrases here — none of those are needed to sort out dashboard access.

Sources

Note: This response was generated by an AI bot and may require further verification. The MetaMask Community Team has tracked this issue and will be responding as soon as possible.

3

dev@cyphed.io is Google Group alias, and it was the only owner, if you are able to subscribe me again I will be able to login with email

4

We can’t re-subscribe an email address or restore a Dashboard login from here — Dashboard access is tied to the Google identity that authenticated, and a Google Group alias like dev@cyphed.io is controlled by that group’s administrators, not by the Embedded Wallets SDK or the Dashboard itself.

Two things decide what’s possible:

  1. Whether the Google Group alias can be restored on your side. If a Google Workspace admin for cyphed.io can re-create the alias/group and restore mail delivery, the same Google sign-in should work again at https://dashboard.web3auth.io with no change needed on our end.
  2. Whether any other owner remains on the project. If a second account still has owner access, that account can add a new owner directly from the Dashboard.

If neither applies, please reply here with:

  • The affected Client ID(s) and project name
  • The exact login method used (Google sign-in via the dev@cyphed.io alias)
  • Confirmation of whether a Workspace admin for the domain still exists

We’ll take it from there.

Please don’t post any password, private key, or recovery phrase in this thread — none of that is needed for Dashboard access questions, and we will never ask for it.

Sources

Note: This response was generated by an AI bot and may require further verification. The MetaMask Community Team has tracked this issue and will be responding as soon as possible.

5

The Google Group alias was not deleted it is active, I clicked in the unsubscribe button on the email that I got OTP

6

Hi @rishikhesh thanks for sharing the details, we’ll let the team know

7

Any updates on this, this is super critical for me

8

Hey @rishikhesh

Please fill up this form you will be resubscribed Email OTP or magic link not received | MetaMask developer documentation

9

Thanks this worked, I am able to relogin now

1 Like
10

Great — glad you’re able to log back in.

For future access safety on Embedded Wallets accounts, we’d recommend enabling MFA so the account has additional recovery factors beyond the single social login: enableMFA | MetaMask developer documentation (equivalent guides exist for Android, iOS, and Flutter).

As always, never share your private keys, recovery factors, or account passwords with anyone — MetaMask will never ask for them.

Happy to help if anything else comes up!

Sources

Note: This response was generated by an AI bot and may require further verification. The MetaMask Community Team has tracked this issue and will be responding as soon as possible.