Purpose Understand how Structured AI notifications are triggered, delivered, and controlled.
This internal reference explains how notifications work across the StructuredAI platform, including who receives each notification, when it is triggered, whether it is delivered by email or in-app, and which notification settings users can customize.
How Notifications Work Review delivery channels, user notification settings, and locked critical alerts.
Every user has a Notifications section in their profile settings where they can toggle specific alerts.
Notifications are delivered via two channels:
- Email: Sent to the user’s registered email address.
- In-App: Appears under the bell icon in the platform header.
Locked
Locked notifications are considered critical. They cannot be disabled by the user and will always be delivered.
Tenant Notifications Review tenant-wide alerts for campaign expiration and Content Library publishing activity.
Tenant-level notifications are broadcast to all users within the tenant. Every user receives updates about all tenant content, regardless of ownership, though most can be toggled off individually.
Campaign Expiration Alert (Real-Time)
Sends countdown warnings at 90 days, 30 days, and 10 days before a campaign expires.
- Behavior: If a campaign is shorter than a trigger window, such as a 20-day campaign, earlier alerts are skipped. Only alerts falling within the campaign’s actual lifespan are sent.
- Email/In-App: ON by default · Editable
Library Publishing Digest (Weekly — Thursdays)
A weekly roll-up of all content published to the Content Library. This is the recommended way for users to stay informed without receiving individual alerts for every upload.
- Email/In-App: ON by default · Editable
Library Publish — Real-Time
Fires immediately when an asset is published for the first time. It also fires during republishing only if the group selection changes, alerting users when groups are added or removed.
It does not fire for standard content updates where groups remain the same.
- Email/In-App: OFF by default · Opt-in
Partner (Account) Notifications Review user-specific lead, social, campaign, and content notifications for partner accounts.
Partner notifications are specific to users within a partner account and are generally tied to content ownership or specific user actions rather than a global broadcast.
Lead Form Submission (Real-Time)
Triggered when a lead form is submitted. The recipient is determined by the traffic source:
- Scheduled Campaigns: The partner who initiated the campaign gets the alert.
- Organic/Direct: The partner who created the landing page or form gets the alert.
- Email/In-App: ON · Locked — cannot be disabled.
Social Publishing Failure (Real-Time)
Fires when a scheduled social post fails due to expired tokens or API errors. Sent only to the owner of that specific social connection.
- Email: ON by default · Editable
- In-App: ON · Locked
Social Connection Expiry (Real-Time Warnings)
Warns the connection owner to re-authenticate before their token expires.
| Timing | In-App | User Can Disable? | |
|---|---|---|---|
| 14 Days Before | ON | ON | Yes |
| 7 Days Before | ON | ON | Yes |
| Day 0 (Expiration) | ON | ON | No — Locked |
Campaign Schedule Digest (Weekly — Thursdays)
A personal summary of the upcoming week’s scheduled email and social campaigns. Users only see the campaigns they personally scheduled.
- Email/In-App: ON by default · Editable
Post-Campaign Performance Summary (Weekly — Mondays)
A batched summary of all campaigns that reached a Finished state during the previous week, ending Sunday night.
- Timing: Campaigns finishing on Monday will appear in the following Monday's digest.
- Email/In-App: ON by default · Editable
New Content Available (Weekly — Thursdays)
A digest of new assets added to the library, filtered by the partner’s assigned group. Users only see content relevant to them.
- Email/In-App: ON by default · Editable
Quick Reference: User Control Matrix Compare each notification, its recipient, and whether the user can disable it.
| Notification | Recipient | User Can Disable? |
|---|---|---|
| Campaign Expiration Alert | All Tenant Users | Yes |
| Library Publishing Digest | All Tenant Users | Yes |
| Library Publish (Real-Time) | All Tenant Users | Yes (Off by default) |
| Lead Form Submission | Campaign/Page Owner | No |
| Social Publishing Failure | Connection Owner | Email only (In-App is Locked) |
| Social Connection Expiry | Connection Owner | Early warnings only (Day 0 is Locked) |
| Campaign Schedule Digest | Partner User (Own) | Yes |
| Post-Campaign Performance | Campaign Owner | Yes |
| New Content Available | Partner User (Group) | Yes |
Common Support Questions Use these checks when users report unexpected notification behavior.
“A tenant user says they’re not getting campaign expiration alerts.”
Check their profile settings to see if they toggled them off. Also, verify the campaign duration; if it’s a 7-day campaign, it won't trigger the 10, 30, or 90-day alerts.
“A partner says they got a lead notification but they didn’t schedule the campaign.”
Check if the lead was organic. If no campaign was involved, the notification defaults to the creator of the landing page or form.
“A partner wants to stop getting lead form notifications.”
This is not possible. Lead notifications are locked to ensure immediate follow-up on potential business.
“A partner says their Campaign Schedule Digest includes campaigns they didn’t create.”
Escalate this to Engineering. The digest is designed to be strictly personal to the user who scheduled the campaign.
“A tenant user got a real-time library publish alert for content that was already published.”
This happens if the assigned groups were changed during a republish. The system alerts users when content availability changes for specific groups.
“A tenant asks to preview what a notification looks like before enabling it.”
There is currently no preview or test-send functionality. This is a known product gap.