Keeping everyone aligned during the content creation process is critical. To save you time, the platform automatically sends notifications to the right people—creators, approvers, and clients—as content moves from the first draft to final publication.
Here is a quick overview of how notifications flow through the content lifecycle:
flowchart TD
A([Content Submitted]) --> B["In-app notice to Approvers"]
B --> C{"Review Decision"}
C -->|"Needs Revisions"| D["In-app notice to Creator"]
C -->|"Approved"| E["In-app notice to Creator"]
E --> F["Branded Email to Client"]
E --> G["Automations Triggered (e.g., Handwritten Cards)"]
E --> H([Content Published])
H --> I["In-app notice to Publisher"]Notification breakdown
Different actions trigger different types of alerts. We prioritize in-app notifications to keep your inbox clean, but we also send branded emails to clients for major milestones like final approval.
| Action | Who gets notified? | Notification Type | What they see |
|---|---|---|---|
| Content Submitted | Assigned Approvers | In-app (High Priority) | A request to review the newly submitted content. |
| Revisions Requested | Content Creator | In-app (High Priority) | A notice that changes are needed, including the reviewer's feedback. |
| Content Approved | Content Creator | In-app | A confirmation that their work was approved. |
| Content Approved | Client (Primary Contact) | A branded email celebrating the approval with a link to view the content. | |
| Content Published | Content Creator | In-app | A notice that the content is now live. |
Smart filtering: To prevent notification fatigue, the system will never notify you about an action you just took. For example, if you approve your own content, you won't receive an approval notification.
Setting up client approval emails
When content is approved, the system can automatically send a beautifully branded email to your client. For this to work, you need to ensure the client's profile is configured correctly.
- 1
Set a Primary Contact
Navigate to your client's profile and ensure they have a designated Primary Contact with a valid email address. If no primary contact is set, the system will try to use the general company email.
- 2
Enable Brand Identity Emails
Go to the client's Brand Identity settings.
- 3
Toggle Notifications
Ensure that Email Notifications are enabled (opted-in). If this is turned off, the system will skip sending the approval email to respect the client's communication preferences.
The approval email includes your custom branding and a direct "View Content" button that takes the client straight to the editor to see the final result.
Approval automations
Approving content does more than just send notifications—it can also kick off real-world workflows.
When a piece of content is marked as Approved, the platform fires an automation event. Depending on your account configuration, this can trigger:
Handwritten Cards: Automatically queue and send a physical, handwritten card to the client's primary contact to celebrate the milestone.
External Integrations: Dispatch webhooks to external tools (like CRMs or project management software) to update the content's status across your tech stack.
Why didn't my stakeholders get a notification when content was published?
By design, the "Content Published" notification is only sent to the user who originally created the content. This prevents spamming the entire account or client team every time a post goes live.
Can I customize the rejection feedback?
Yes! When you request revisions or reject content, the feedback you type into the review prompt is automatically included in the notification sent to the creator.