CustomDomain Docs
Account and security

Notifications

Choose which alerts and emails you get.

CustomDomain™ tells you when something happens to your domains, your billing or your agents, so you do not have to keep a tab open. There are two places a notification can land, and you choose each one separately:

  • The bell. The bell at the top right of the console holds your latest notifications, with a count of the ones you have not opened. See all notifications opens the full list. Nothing here asks for a permission.
  • Push. A notification from your browser, on your phone or computer, even when the console is closed. Push is off until you turn it on in a browser, and your browser asks you first.

Email is separate from both. Email, below, lists every email we send, who gets it and how to stop it. Security and account email is always sent.

What you are told about

NotificationWhenIn the bellPush
A domain goes liveA domain finishes connecting and is serving your customers.OnOn
A domain needs attentionA domain did not finish connecting after a day, or is still waiting for DNS records.OnOn
DNS records changedA record we manage changed or went missing and you have to put it right.OnOn
DNS records put backWe restored records that went missing, through access you kept.OnOn
Certificate problemsA certificate could not be issued, keeps failing to renew, is about to expire or has expired.OnOn
A payment fails, choose a plan reminders, adding domains is paused, billing is back in good standing, your trial is endingEach rings when its billing email is sent. A few billing emails have no bell: the trial starting, a subscription ending and an ended plan's three emails.OnOn
A refund or dispute is under reviewA payment is refunded or disputed and a person is looking at it. Nothing changes on its own.OnOn
A domain you bought is registered, or the purchase failedA purchase through your workspace finished or could not be completed.OnOn
An agent spent money, or a new agent was connectedAn AI agent bought a domain, or someone gave one access to the workspace.OnOn
An agent's access endedA person or the agent revoked the agent's access to the workspace.OnOn
An agent hit its spend capAn agent tried to buy a domain past the monthly cap you set. The purchase is refused and no money moves.OnOn
An agent's credential was reusedAn old agent credential was used again after it was replaced. The agent's access is revoked.OnOn
A DNS provider needs reconnectingA provider stopped accepting a saved key, so automatic repair is paused.OnOn
A DNS provider key ends soonAn API key a secure sign-in made at a DNS provider ends in 30 or 7 days, so its end user can sign in again first.OnOn
Routine agent actionsWhat an agent does, such as connecting a domain, once an hour.OnOff
A customer connects through your widgetOne of your customers connected a domain with the widget. A domain you connected yourself with the widget, from the welcome, is told here too, as that domain being live.OnOff
Someone joins your teamA person you invited accepted.OnOff

These go to the owners and admins of the workspace. A member or a viewer does not get them. The last three are quiet by default because they can be frequent; turn push on for them if you want it. The exception is a workspace for your own product's customers (you chose My product's users at the start): the first browser you turn push on in also pushes for A customer connects through your widget, because that is the moment you are waiting for. It is an ordinary choice on your notification page, Settings → Notifications (with the new menu, Notification settings in the avatar menu): turn it off there and it stays off.

If you belong to more than one workspace, the bell holds them all, each notification starts with its workspace's name, and opening one switches the console to that workspace.

A domain going live is the one worth leaving the page for. While a domain waits for DNS, its page offers Get a ping when it is live, so you can close the tab and be told the moment it is connected. It turns push on for that one thing; you choose the rest under Settings → Notifications (with the new menu, Notification settings in the avatar menu). A domain a customer connected with the widget has no card, because those stay in the bell.

The welcome asks the same thing on its last screen, while a domain you just added waits for its DNS records: Get a ping when acme.com is live, or "when your domains go live" after you pasted a list, with Notify me and Not now. Notify me is the click that makes your browser ask, and it turns push on for a domain going live and for nothing else. Turning push on there, or blocking notifications at your browser's prompt, ends the offer in that browser, so the one on Overview does not ask again. Not now counts like Not now on Overview (below), so that offer comes back a few days later. Signing out of a browser that had push on takes the answer back, so you are offered it again the next time you sign in there. Where the browser cannot do push or has blocked it, the screen says nothing about it.

Turn push on

After you sign up, Overview also offers Get notified in this browser, with Turn on and Not now. It shows only where the browser can do push, and only after the other one-time offers on Overview (such as adding Google or GitHub) have been answered. Turn on is the click that makes your browser ask.

Not now brings the offer back on a later visit to Overview: at least 3 days after the first Not now, at least 7 days after the second, and not by itself after the third. Once you have said Not now in a browser (here or on the welcome), the offer also has Don't ask again. Turning push on, blocking notifications at your browser's prompt, or Don't ask again ends the offer in that browser. A site cannot ask a browser that blocked it again, so the offer then links How to allow them to Settings → Notifications (with the new menu, Notification settings in the avatar menu). You can also turn push on yourself:

  1. Open Settings → Notifications (with the new menu, Notification settings in the avatar menu).
  2. Press Enable notifications on this device. Your browser asks whether to allow notifications; choose Allow. It only asks when you press the button.
  3. Press Send a test notification to see one arrive.

Push is per device. Do the same in each browser you want it in; the list under Devices with notifications on shows every one, and Remove takes one off.

On an iPhone or iPad, notifications work once CustomDomain™ is added to your Home Screen: in Safari tap Share, choose Add to Home Screen, then open CustomDomain™ from your Home Screen and turn push on there. Safari itself cannot receive web push.

If your browser blocks notifications for the site, we cannot turn them on from the page. Open the browser's site settings (the icon next to the address), set Notifications to Allow, then come back and check again.

Choose what you are told

Open Settings → Notifications (with the new menu, Notification settings in the avatar menu). Under What to tell you every kind has two switches, In app and Push. A switch you never touched follows the default above. Changes apply at once and are yours alone: they do not change what a teammate gets.

Turn them off

  • One kind, one place: switch it off under What to tell you.
  • Push on this device: press Turn off on this device, or remove it from the device list.
  • Push on every device: remove each device, or switch Push off for every kind.
  • Everything but the bell: switch Push off for every kind.
  • Signing out takes this browser off the device list, so a shared computer stops getting your notifications.

You can also withdraw the permission in your browser's site settings at any time. A notification never needs you to keep the console open.

Email

Every email CustomDomain™ sends is listed below: what it says and when it goes, who gets it, whether it is always sent or optional, and how to stop it. The console shows the same list, read only and open to every role, so a member sees what an owner sees. Nothing on it switches an email on or off.

  • Open Settings → Notifications. Your own switches are at the top: push on this device, and the bell and push choice for each kind of alert, which the steps above describe. Under them, What we send has one line per kind of email and a closed row, Every email, who gets it and how to stop it, which opens the full list.
  • The same switches are on Notification settings, in the avatar menu.

There is one menu now, so the separate Emails we send page of the old Classic menu is gone. Navigation has the details.

Beside each email the console also shows whether the bell and push ring at the same moment, and what they default to. They go to every owner and admin, so when an email goes to one person, such as the person who gave an agent access, the page adds "for owners and admins". You choose them under What to tell you, above, not here.

How to stop an email

The last column of each table says how. There are three cases:

  • Always sent. Security and account email cannot be turned off. Its row says what to do instead: revoke an agent, change a person's role on the Team page (Team & roles in the new menu), fix the domain, or ignore the email.
  • Optional: tips and product updates, domain alerts, the weekly digest. Each has one switch in your Email preferences. Open it from the Email preferences link in the footer of one of those emails (no sign-in needed), or from the link at the top of the console's list. Unsubscribe from all optional email turns all three off at once.
  • Optional: set for each application. Email to your customers is stopped by the application's own setting, not by anyone's preferences: choose Don't send under Who sends DNS update emails, in End user email on the application's settings. See Who sends it.

Domain emails

Certificate and DNS alerts go to owners and admins. Certificates and Monitoring describe them, Routing describes the move email, and End user notices describes the two emails to a customer.

EmailWho gets itSentHow to stop it
A domain needs attention. A domain has waited a day for its DNS records and they are still missing. Not sent once the domain is a week old.The workspace ownerOptional: domain alertsTurn off domain alerts in your email preferences.
A domain's setup failed. A domain's setup failed and stayed failed for two hours. Not sent once the failure is a week old.The workspace ownerOptional: domain alertsTurn off domain alerts in your email preferences.
Your first domain is live. The first time a domain goes live, within a week of it.The workspace ownerOptional: tips and product updatesTurn off tips and product updates in your email preferences.
Certificate problems. A certificate could not be issued, keeps failing to renew, is about to expire or has expired.Owners and adminsAlways sentCannot be turned off. Fix the domain and the alerts stop. To stop it for one person, change their role to member on the Team page.
DNS records changed. A record CustomDomain™ manages changed or went missing and you have to put it right. It is also sent when a domain's nameservers were changed at the registrar after a nameserver move.Owners and adminsAlways sentCannot be turned off. Fix the records and the alerts stop. To stop it for one person, change their role to member on the Team page.
A domain moved to other routing. A domain was moved to other routing and its DNS records changed.Owners and adminsAlways sentCannot be turned off. It is sent once for each move. To stop it for one person, change their role to member on the Team page.
DNS records sent to someone. Someone asked us to email a domain's DNS records, from the widget or the console.The person it is forAlways sentCannot be turned off. It is sent only when someone asks, to the address they typed. Ignore it and nothing changes.
The weekly digest. Once a week, early in the week, when the week had widget activity, a new domain or something that needs attention.The workspace ownerOptional: the weekly digestTurn off the weekly digest in your email preferences.
New DNS records for a customer. A domain was moved and its records have to change, sent to the customer who connected it.The customer who connected the domainOptional: set for each applicationChoose Don't send under Who sends DNS update emails in the application's settings. It stops the reconnect email too. Or leave the customer's address off: it goes only to the address you gave us.
Reconnect notice for a customer. The key we made at a customer's DNS provider is about to end or has stopped working.The customer who connected the domainOptional: set for each applicationChoose Don't send under Who sends DNS update emails in the application's settings. It stops the new DNS records email too. Or leave the customer's address off: it goes only to the address you gave us.

Billing emails

Billing emails go to owners and admins. Billing emails describes the trial, payment and plan ones.

EmailWho gets itSentHow to stop it
Your trial started. A plan's trial starts. Nothing is charged before it ends.Owners and adminsAlways sentCannot be turned off. It follows the workspace's plan. To stop it for one person, change their role to member on the Team page.
Your trial is ending. Three days before the trial ends and the card is charged.Owners and adminsAlways sentCannot be turned off. It follows the workspace's plan. To stop it for one person, change their role to member on the Team page.
A payment failed. A payment for the plan did not go through.Owners and adminsAlways sentCannot be turned off. It follows the workspace's plan. To stop it for one person, change their role to member on the Team page.
Choose a plan. A grace period starts and a plan has to be chosen or billing set up.Owners and adminsAlways sentCannot be turned off. It follows the workspace's plan. To stop it for one person, change their role to member on the Team page.
Choose a plan reminder. Seven, three and one day before the grace period ends.Owners and adminsAlways sentCannot be turned off. It follows the workspace's plan. To stop it for one person, change their role to member on the Team page.
Adding domains is paused. Billing paused adding new domains. Domains already connected keep working.Owners and adminsAlways sentCannot be turned off. It follows the workspace's plan. To stop it for one person, change their role to member on the Team page.
Billing is back in good standing. A payment went through or a plan was chosen, and new domains work again.Owners and adminsAlways sentCannot be turned off. It follows the workspace's plan. To stop it for one person, change their role to member on the Team page.
Your subscription ended. A subscription ended. Domains already connected keep working. Where lapsed plans are on, Your plan ended is sent instead.Owners and adminsAlways sentCannot be turned off. It follows the workspace's plan. To stop it for one person, change their role to member on the Team page.
A refund is under review. A payment was refunded and a person is looking at it. Nothing changes on its own.Owners and adminsAlways sentCannot be turned off. It follows the workspace's plan. To stop it for one person, change their role to member on the Team page.
A payment dispute. A payment was disputed with the card issuer, and again when the dispute is settled.Owners and adminsAlways sentCannot be turned off. It follows the workspace's plan. To stop it for one person, change their role to member on the Team page.
Your plan ended. Where lapsed plans are on, a plan ended and nothing replaced it. Domains keep working until the date it names.Owners and adminsAlways sentCannot be turned off. It follows the workspace's plan. To stop it for one person, change their role to member on the Team page.
Your domains pause soon. Where lapsed plans are on, a reminder before the date the domains of an ended plan are paused.Owners and adminsAlways sentCannot be turned off. It follows the workspace's plan. To stop it for one person, change their role to member on the Team page.
Your domains are paused. Where lapsed plans are on, the date passed and the domains of an ended plan are paused until you subscribe again.Owners and adminsAlways sentCannot be turned off. It follows the workspace's plan. To stop it for one person, change their role to member on the Team page.

Agent emails

The email goes to the person who gave the agent access. Its bell and push go to every owner and admin. Owner emails describes them.

EmailWho gets itSentHow to stop it
A new agent was connected. Someone gave an AI agent access to the workspace. It lists what the agent can do.The person who gave the agent accessAlways sentCannot be turned off. It is sent once, when access is given.
Routine agent actions. An agent connected, disconnected or re-applied a domain, used a saved key, or moved a domain's nameservers.The person who gave the agent accessAlways sentCannot be turned off. Revoke the agent's access under Agents and these stop.
An agent hit its spend cap. A purchase was blocked because it would go over the agent's monthly spend cap. No money moved.The person who gave the agent accessAlways sentCannot be turned off. Revoke the agent's access under Agents and these stop.
An agent spent money. An AI agent bought a domain and was charged.The person who gave the agent accessAlways sentCannot be turned off. Revoke the agent's access under Agents and these stop.
An agent's access ended. An agent's access to the workspace was revoked, by a person or by the agent.The person who gave the agent accessAlways sentCannot be turned off. It is sent once, when access ends.
An agent's credential was reused. An old agent credential was used again after it was replaced. The agent's access is revoked.The person who gave the agent accessAlways sentCannot be turned off. It is sent once, when the agent is cut off.

Account emails

Sign-in, password and invite emails go to the person they are for. The tips and nudges go to the workspace owner. The last two are operator notices: they go to whoever runs this deployment.

EmailWho gets itSentHow to stop it
Confirm your email address. You signed up and the address has to be confirmed.The person it is forAlways sentCannot be turned off. Ignore it if you did not sign up: the account stays unverified.
Password link. Someone asked to reset a password, or to add one to an account that signs in with Google or GitHub.The person it is forAlways sentCannot be turned off. Ignore it if you did not ask: your password stays as it is.
Your password was changed. After a password reset or a change in Settings, so you know it happened.The person it is forAlways sentCannot be turned off. If it was not you, reset your password under Security.
A new way to sign in. A passkey, Google or GitHub was added to your account.The person it is forAlways sentCannot be turned off. If it was not you, remove it under Security and reset your password.
A way to sign in was removed. A passkey, Google or GitHub was removed from your account.The person it is forAlways sentCannot be turned off. If it was not you, reset your password and check Security.
Confirm a new email address. You asked to change the address you sign in with. It goes to your current address.The person it is forAlways sentCannot be turned off. Ignore it if you did not ask: your address stays as it is.
An invite to a workspace. An owner or admin invited you to join a workspace.The person it is forAlways sentCannot be turned off. Ignore it and nothing happens until you accept.
Your role in a workspace changed. An owner or admin changed your role in a workspace.The person it is forAlways sentCannot be turned off. Ask an owner or admin of the workspace if you have questions about it.
You were removed from a workspace. An owner or admin removed you from a workspace.The person it is forAlways sentCannot be turned off. Ask an owner or admin of the workspace to invite you again.
An invite to finish a domain. Someone invited you to help finish one domain. The records to add come with it.The person it is forAlways sentCannot be turned off. Ignore it and nothing happens until you accept.
A test message from your mail server. Someone pressed Send test on an application's own mail server settings.The person it is forAlways sentCannot be turned off. It is sent only when you press Send test, to the address you type.
Your first steps. Right after the welcome questions, or half an hour after sign up without them. Never after two days.The workspace ownerOptional: tips and product updatesTurn off tips and product updates in your email preferences.
Open the widget. One to three days after sign up, when nobody has opened the widget.The workspace ownerOptional: tips and product updatesTurn off tips and product updates in your email preferences.
Add your first domain. Three to seven days after sign up, when the workspace has no domain.The workspace ownerOptional: tips and product updatesTurn off tips and product updates in your email preferences.
Start a trial. Only when the people who run CustomDomain™ send it by hand, when the workspace has no plan or trial.The workspace ownerOptional: tips and product updatesTurn off tips and product updates in your email preferences.
Connect your server. Only when the people who run CustomDomain™ send it by hand, when your server never asked for a widget token.The workspace ownerOptional: tips and product updatesTurn off tips and product updates in your email preferences.
Your first customer domain. Only when the people who run CustomDomain™ send it by hand, when the widget was opened and no customer's domain is live.The workspace ownerOptional: tips and product updatesTurn off tips and product updates in your email preferences.
Add a second domain. Only when the people who run CustomDomain™ send it by hand, when the workspace has exactly one domain.The workspace ownerOptional: tips and product updatesTurn off tips and product updates in your email preferences.
A note when you have gone quiet. A free workspace with no live domain was quiet for two weeks. Never to people who pay or in regions that need opt in consent.The workspace ownerOptional: tips and product updatesTurn off tips and product updates in your email preferences.
One last note. Two weeks after the first note, when the workspace is still quiet. Never sent to someone who came back.The workspace ownerOptional: tips and product updatesTurn off tips and product updates in your email preferences.
A DNS provider's checks changed. A check of a DNS provider changed status. One email for each monitor run.Whoever runs this deploymentAlways sentCannot be turned off. Whoever runs this deployment sets where these go.
Browser minutes are at 80 percent. Once a month, when the secure sign-in has used 80 percent of its monthly browser time.Whoever runs this deploymentAlways sentCannot be turned off. Whoever runs this deployment sets where these go.

What we keep

To send push we store your browser's push endpoint and keys, the name of the browser (such as Chrome on macOS) so the device list can tell your devices apart, and when each was added and last used, linked to your account and workspace. Your browser's user agent is read to make that name and is not kept. Remove deletes them. The bell's notifications are kept for about four months. See the privacy policy for the rest.

On this page