Skip to main content
All documentation

Manage notifications

Find in-app history, set account and ticket preferences, and maintain optional delivery endpoints in your protected profile.

Workflow
  1. Read historyFilter notices by unread or read state.
  2. Set preferencesChoose locale, time zone, theme and channels.
  3. Tune ticket alertsSet channel preferences for support activity.
  4. Register endpointAdd protected details for optional delivery channels.
  5. Verify changesSave settings and check the resulting page or history.

In-app notification history

The full dashboard history is paginated and filterable by unread or read. Opening a notice marks it read and follows its local dashboard destination. Missing or unsafe destinations go to a safe dashboard page. Mark all read updates every unread notice. The header dropdown shows only a small recent subset, so older items remain in full history.

  1. Open Notifications and filter when needed.
  2. Open a notice to mark it read and follow its link.
  3. Use Mark all read after checking items needing action.

Account preferences

Profile preferences include supported locale, time zone and light, dark or automatic theme. General notification choices include email and SMS. Saving a locale updates your current session as well as your preference. Available languages and channels depend on the options shown to you. A preference does not by itself register an SMS or messaging endpoint.

  1. Choose a listed language, valid time zone and theme.
  2. Set general email and SMS choices deliberately.
  3. Save and confirm the displayed settings.

Ticket notification channels

Ticket activity preferences separately control email, in-app, browser push, SMS, messaging and digest. Email and in-app default on; other channels default off. Some channels require an endpoint and provider setup. A digest setting changes ticket delivery preference; it is not an unread filter in notification history.

  1. Select only ticket channels you can receive.
  2. Register required endpoint before enabling its channel.
  3. Save preferences and check them after reload.

Manage delivery endpoints

The profile endpoint form accepts browser push, SMS or messaging, provider and address, plus optional token and metadata. Registration enables or updates the matching account endpoint. Treat tokens as credentials and enter them only in the protected form. Removing an endpoint deletes that destination; it does not automatically change all preference switches.

  1. Choose the available channel and provider.
  2. Enter address and required token in the protected form.
  3. Remove retired endpoints and adjust preferences separately.

Choose what stays enabled

Turning off a channel does not delete the related invoice, ticket, job update or dashboard record. Keep a reliable channel enabled for notices requiring action. Marketing email has a separate preference and defaults off. Ticket settings apply to support activity; they do not change service or payment state.

  1. Distinguish account, ticket and marketing settings.
  2. Keep at least one reliable channel enabled.
  3. Check the underlying record for current status.

Troubleshoot missed alerts

Check in-app history first, then verify the channel preference, endpoint, provider, browser permission or device access. A link may lead to a protected record unavailable under your current account or organisation. Never send endpoint tokens or private payloads to support; report event type, approximate time and a safe record reference.

  1. Search read and unread history for the event.
  2. Check channel preference, endpoint and device permissions.
  3. Contact support with time and non-sensitive reference.

Frequently asked questions

Where are older notices?

Use full Notifications history, not only the header dropdown.

Does disabling email delete alerts?

No. Preferences control delivery, not stored records.

Why is SMS missing?

Check both preference and registered endpoint.

Can I mark all read?

Yes, after checking items needing action.

Does locale affect others?

No. It changes your account preference and session.

Should I share an endpoint token?

No. Give support a time and safe reference only.

Related pages