TikTok LIVE Alerts: review creator monitoring and Discord delivery
Configure the network’s private alert destination, understand creator monitoring states and manage owner-only requirement overrides.
This guide describes the available features. Your account role, assigned modules, signed contract and network plan determine which controls you can use. Reading a guide does not change your access.
Start here
- Owners: open TikTok LIVE Alerts and save a valid Discord webhook for the channel that should receive LIVE notifications.
- Search the Creators table by name, username or status, and use Creators per page to adjust the list.
- Review Status and Last checked for a creator. A Disabled row does not indicate active monitoring.
- Owners: use Override only when that individual creator should be checked regardless of administrator monthly requirements; use Use admin requirements to restore them.
- Confirm the expected alert when a monitored creator next goes LIVE and investigate any Check failed or Webhook required state.
Scope and access
The table lists active creators available to the signed-in account. The owner can see the network; a sub-user is limited by their manager hierarchy and assigned creator ownership. If the list is empty, check active roster membership and manager assignment rather than assuming the whole network has no creators.
The Discord webhook is private to the main owner’s controls. Managers cannot view, replace or remove it. Requirement overrides are also restricted to the owner or administrator.
Save or remove the notification destination
New webhook URL is a password-style input. Paste a complete valid Discord webhook and choose Save webhook. The saved URL is never displayed again; entering a new one replaces it. The configured badge indicates whether a destination exists.
Remove webhook clears the destination. Without a configured webhook the service cannot deliver network notifications. This module’s destination is separate from the per-message webhooks in Discord Alerts and from TikTok App Updates.
Understand creator status before expecting alerts
Disabled means that monitoring is not enabled for that row. Criteria filtered means administrator monthly requirements filtered the creator. Check failed means the latest check could not be completed; the short error text may explain why. Webhook required means the alert destination is missing. LIVE means the latest observed state is live; Offline means a completed check found the creator offline; Monitoring means checking is enabled without another displayed state.
Last checked is your freshness indicator. Not checked yet is different from Offline. The visible page provides a requirements override action, not a per-creator enable switch. If a creator is Disabled, ask the owner or administrator to review the monitoring setup; clicking Override alone should not be treated as enabling monitoring.
Apply and remove an individual requirements override
Administrator monthly requirements apply by default. Override marks one creator as exempt from those requirements; the badge becomes Overridden. Use admin requirements restores the normal criteria for that creator. This does not change everyone’s requirements.
An alert is intended once each time a creator goes LIVE, rather than on every repeated check during one broadcast. Use search, sortable columns and Previous/Next or the table’s pagination to find the relevant creator and inspect the latest status before reporting a missing notification.
Frequently asked questions
Where is the enable switch?
This page’s visible creator action is Override or Use admin requirements. It does not expose a general monitoring enable switch. A Disabled row requires the owner or administrator to review monitoring setup.
Does Override change the whole network?
No. It exempts only that creator from the administrator’s monthly criteria.
Why can I not see the Discord webhook?
Only the main account owner can manage it, and even for the owner the saved URL is not displayed again.
Why was there only one notification during a long LIVE?
The module sends an alert once per detected LIVE occurrence, rather than on every monitoring check.
Still stuck? Note the page name, the step you tried and the exact message shown. Managers and sub-users should contact their network owner; owners should contact their platform administrator. Never include passwords, webhook URLs, recovery links or private identity documents in a general support message.