Change your account email

Your account email is the address you sign in with and the address we write to about your account. It belongs to you, not to a team, so changing it changes it in every team you are in.

This page is about your own sign-in address. To send a team’s build results and receipts to a shared inbox instead, see choose where your team’s email goes.

Change the address

1. Open the avatar menu and choose Profile.
2. In the Email row, select Change.
3. Type the new address, for example name@example.com, and select Continue.
4. Pass the security check (see the next section).
5. Open the new inbox. We send a 6-character code there, such as A1B2C3.
6. Type the code into the dialog and confirm.

The code works for one hour, and you get 5 tries. After that the request is over and you start again with a new code.

Until you confirm, nothing changes: your current address keeps working for sign-in and mail. While a request is open, the Email row on Profile says which address it is waiting on, with Enter code to pick it up again and Cancel to drop it.

Pass the security check

Before the code is sent, we ask you to prove it is you, even though you are already signed in. Which options you see depends on how your account signs in:

• Your password, plus the code from your authenticator app if you have one set up.
• Your passkey.
• The sign-in provider linked to your account, such as GitHub. This is offered only when you have no authenticator app and no passkey. Once you have either, use it or your password with the authenticator code.

If your account uses a second step this check cannot run, such as a hardware security key, or codes sent by text message or email, the dialog says so. Email support@deploybase.eu and we will change the address for you.

A passed check covers one change. Resend the code asks for it again.

What confirming changes

You are signed out in every browser. Confirming ends your deploybase session in every browser, including the one you are using. Sign in again with the new address.

The CLI and agents stay signed in. A CLI or agent that signed in as you keeps working after the change. Run deploybase logout on each machine where you no longer want it, then deploybase login with the new address. If you think someone else is signed in as you, use the freeze link described below, or email support@deploybase.eu.

Team API keys keep working. A key belongs to a team, not to you, so scripts and CI that use one are not affected.

Your sign-in provider keeps working. If you sign in with GitHub or another provider, you keep doing so. The change affects the address we email and your login name, not the provider link.

Your teams see the new address. Your membership in each team is updated to the new address.

Forms are not changed for you. If a form in one of your teams sends submissions to your old address, the dialog lists it after you confirm. Those recipients belong to the team, so we leave them alone: change each one in the form’s settings, or ask a team admin to.

Invoices do not follow. Invoices and receipts go to the address on your billing profile with our payment provider. Changing your account email does not change it. Update it from Billing in the billing portal.

The new address also gets a short note confirming that it is now your sign-in address.

If you did not make the change

When the change is confirmed, we send a notice to your old address. It carries a This wasn’t me: freeze my account link. The link works once, for 7 days.

Freezing the account:

• stops anyone signing in, including you;
• ends every session, so anyone signed in is signed out;
• alerts our support team, who check with you before anything is unlocked.

Freezing does not move the address back. The old mailbox can stop the account, not take it over, because a mailbox someone has given up may now belong to someone else.

If the link has expired or was already used, email support@deploybase.eu and we will freeze the account for you.

Your old address

For 30 days after the change, your old address stays reserved for you. Nobody else can sign up with it or move their account to it, and you can change back to it in that time. After 30 days it is free again.

When you can’t change it here

Your team uses single sign-on. If your account came from a team that signs in through its own identity provider, that provider manages your address. The Email row says so instead of offering Change. Ask your team admin to change it in the provider.

API keys can’t do it. Only a signed-in person can change a sign-in address.

Troubleshooting

No code arrived. Check spam, and check that you typed the new address correctly. If the address already belongs to another deploybase account, or another account gave it up in the last 30 days, the mail to it explains that instead of carrying a code. Use a different address.

The dialog says to use a plain address. Addresses with accented or other non-ASCII characters are not supported yet.

It says addresses at this domain are managed by another organisation. An organisation has claimed that email domain for its own sign-in. Use an address at a different domain.

It says there have been too many tries. You can start at most 3 changes an hour and 10 a day. Wait and try again.

It says your account is locked. The account was locked after too many wrong tries. Try again later, or email support@deploybase.eu.