Setting Up Notifications in Sked
Sked notifications work across four delivery channels, two preference levels, and a configurable set of notification types. This guide covers how to set everything up and what to expect from each option.
Notification channels
There are four ways Sked can reach you:
- In-app feed: the bell icon in the top bar of your Sked dashboard. A running log of everything that's happened, filterable by read and unread.
- Email: sent via Sked's new notification system. These will replace some of the existing Sked emails you may already receive.
- Mobile push: alerts delivered to your phone via the Sked mobile app.
- Chat: Slack and Microsoft Teams. Both can be connected at the same time, and each group in Sked can be routed to a different channel within your workspace.
Two levels of preferences
User notifications
User notifications are personal – they're triggered by things that involve you directly, regardless of which accounts or groups you manage.
Where to manage them: Profile → Notification
The following notification types are available at the user level:
|
Notification |
What triggers it |
Default channels |
|
Post Teamwork Comment |
A team member mentions you in an internal comment on a post |
Email, In-app feed, |
|
Idea Assigned |
An idea on the Idea Planner is assigned to you |
Email, In-app feed |
|
Idea Teamwork Comment |
A team member mentions you in an internal comment on an idea |
Email, In-app feed |
These are on by default. If you're an existing Sked user, your preferences have been migrated into the new system, check this page to confirm the setup looks right for you.
Group notifications
Group notifications cover activity across the social accounts in a specific group – posts, keywords, approvals, and more. Each user manages their own preferences per group, so team members can choose different notification setups for the same group.
Note: Notification preferences are controlled at a group level, individual social account preferences within a group are not supported.
Where to manage them: Manage Accounts, open a group and click the pencil icon to edit the group. The preferences shown are your own unique user preferences for the group selected, and making changes only affects your own user.
We've automatically subscribed all users to the most essential group notifications as a starting point. You can expand or narrow these at any time by opening a group, enabling the Group Opt-in toggle, and adjusting the channel toggles for each notification type.
[IMAGE: Screenshot of the Group Opt-in toggle and the notification preferences grid]
The full list of group-level notification types, with their default channels:
|
Notification |
What triggers it |
Delivery |
Default channels |
|
Account Disconnection |
A connected social account is disconnected and needs reconnecting |
Batched |
Chat, Email, In-app feed, |
|
Comment Negative Sentiment |
A comment with negative sentiment is detected on an account you manage |
— |
Chat |
|
Comments Processed |
Social Listening finishes processing comments for a social account |
Batched |
Chat, In-app feed |
|
Keyword New |
A new keyword is detected in Social Listening for a group you manage |
Batched & throttled |
None |
|
Keyword Trend |
A tracked keyword trends up or down significantly in Social Listening |
Batched & throttled |
Chat, Email, In-app feed |
|
Post Failed |
A scheduled post fails to publish |
Batched |
Chat, Email, In-app feed, Push |
|
Post Notification |
A manual (reminder) post is due to be sent |
— |
Chat, In-app feed, Push |
|
Post Sent |
A post is successfully published |
— |
None |
|
Post Status Change |
A post's status label is created or changed |
Batched & throttled |
None |
|
Post Status Change Approvals |
A post's approval status changes — approved or returned for changes |
Batched |
Chat, In-app feed |
|
Idea Assigned |
An idea on the Idea Planner is assigned to you |
— |
Email, In-app feed |
|
Idea Create |
A new idea is created in Ideas |
— |
None |
|
Idea Move |
An idea is moved to a different column on the Idea board |
— |
None |
Some notification types have no destinations by default (e.g. Post Sent), but can be enabled as needed on a group by group basis.
Note on Negative Sentiment: Sked doesn't process comment sentiment in real time , comments are analysed on a daily cycle. The notification will fire when that processing is complete, so there'll be a delay between a comment being published and the alert reaching you.
Connecting Slack and Microsoft Teams
Both Slack and Teams can be connected simultaneously. Once connected, each group can be routed to a different channel within your workspace.
Where to set up: Profile → Integrations
To connect Slack:
- Go to Profile → Integrations
- Select Connect to Slack and authorise Sked in your Slack workspace
- Once connected, open each group under Manage Accounts and select the Slack channel you want notifications routed to
To connect Microsoft Teams:
- Go to Profile → Integrations
- Select Connect to Microsoft Teams and authorise Sked in your Teams organisation
- Once connected, open each group under Manage Accounts, select your Team, then select the channel
If you see a connection error on a group, go back to Profile → Integrations and reconnect. It takes about 30 seconds.
How batching and throttling work
Some notification types don't fire instantly. We utilise batching and throttling to avoid flooding you when a lot happens at once, and will deliver a single alert with additional information over multiple sequential alerts in succession.
Batched notifications have a short delay before delivery. If multiple qualifying events happen in quick succession, they're grouped into a single notification rather than arriving one at a time.
Throttled notifications go one step further: they're batched and capped at once per 24 hours. This applies to high-frequency-burst events like keyword changes or post status updates, where you want to know something happened — but not every single time it happens.
The delivery column in the table above shows which notification types use batching, throttling, or both.