Notifications

The Notifications tab in Settings is where you decide what we contact you about and how we reach you. Things like security alerts, billing receipts, ticket replies, and incident updates all run through here.

There are two layers to it. At the top you turn the delivery methods on or off - email and webhook. Below that you pick, per notification, which of those methods to use. By default every notification follows whatever methods you have switched on; you only have to touch an individual notification if you want it to behave differently from the rest.

A few notifications are required and can't be turned off - payment receipts, ticket replies, things you'd want to know about even if you forgot you wanted to know about them. Those are marked Required with a small lock.

1. Click your profile button at the bottom of the sidebar, a small menu opens upward.

2. Click Settings. The Settings page opens on the Account tab.

3. Click the Notifications tab in the row of tabs at the top.

The page has two sections, stacked top to bottom:

• Delivery methods [1]: Email and Webhook, as two cards side by side. These are the defaults that cascade into every notification below.
• Notifications [2]: grouped into categories (General, Support, Security, Billing, Service status, Maintenance). Each row is a collection of thing we might contact you about.

Email is always on. You can see the lock icon and the "Always on" label next to it - there's no toggle to switch it off, because we need at least one guaranteed way to reach you about things like payment failures.

The address used is whatever's on your account. The field is read-only here; to change it, head to the Account tab and use the pencil icon next to the email field. See Changing your email address.

A webhook is a URL on your own server that we POST JSON to whenever a notification fires. Useful if you want to feed notifications into Slack, PagerDuty, an internal dashboard, or wherever else you watch things.

1. Toggle Webhook on. An input box appears.
2. Type the URL you want us to POST to (e.g. https://example.com/hooks/synteq). It has to start with https://.
3. Click Save & reveal secret.

The first time you save a webhook URL, we generate a signing secret and show it to you once. Copy it now and store it somewhere safe - we can't show it to you again. Your server will use this secret to verify that incoming requests are really from us.

After you've saved, the URL field stays editable. If you change the URL, the Save URL button reappears - click it to persist the new URL. The secret doesn't change when you update the URL.

If your signing secret might have been exposed, rotate it:

1. Find the Signing secret strip below the webhook URL (it shows the secret partially masked, like whsec_…abc1).
2. Click Rotate on the right side of that strip.

3. Confirm in the dialog. The new secret is shown once - copy it and update your receiver's configuration immediately.

The old secret stops working the moment you confirm. Any of your receivers still using the old one will start rejecting our webhooks until you update them.

Toggle Webhook off. The URL is cleared on our side and we stop sending. The signing secret stays associated with your account - if you turn webhooks back on later with the same URL, you'll need to save again to generate a fresh secret.

Below Delivery methods is the Notifications list, grouped into categories. Each row shows the notification name, a short description, and a summary on the right of which methods are currently active for it (e.g. "Email", "All methods", "Off").

By default every row follows your delivery methods at the top - so if you only have Email on, every row sends by Email only.

To customize a single notification:

1. Click the row to expand it. A panel opens with one toggle per delivery method.

2. Flip the toggles to match what you want for this notification.

Once you make any changes to a category of notifications, a Revert to default delivery button will appear. You can click it to revert to the default methods inputted under the Delivery methods section.

Required methods on a row show a small lock and Required label. The toggle is fixed on and can't be switched off. Examples:

• Payment succeeded, Payment failed, Upcoming renewal: email required.
• Ticket replies: email required.

Category-level changes (the per-notification toggles) save automatically a moment after you stop clicking. There's no Save button for those - if you're seeing the toggle in the state you want, it's saved.

The webhook URL and the signing secret are the exception: those are user-initiated saves, because generating or rotating a secret is a sensitive action.

• General: Product news and platform updates. Off by default for most accounts.
• Support: Replies on tickets you've opened, and changes to their status.
• Security: New sign-ins, password changes, 2FA changes. We strongly recommend leaving these on.
• Billing: Invoices, payment outcomes, upcoming renewals.
• Service status: Incidents that affect services on your account, including resolution and ongoing degraded-performance reports.
• Maintenance: Scheduled and completed maintenance windows for services you use.

• My webhook never fires: Confirm the master Webhook toggle at the top is on, the URL has been saved (no pending Save URL button), and the individual notifications you care about have the Webhook toggle on inside their expanded panel.
• I lost my signing secret: We only show it once. Rotate it (see above) and update your receiver with the new value.
• I'm not getting emails: Check the address shown on the Email card matches the inbox you're watching. If it doesn't, update your account email on the Account Tab. If it does, check spam - our sender is [email protected].