PranavNagrecha/AwesomeSalesforceSkills / skills/admin/chatter-notification-tuning
chatter-notification-tuning
VerifiedUse when admins are reducing Chatter signal-to-noise across an org — covers org-level Chatter Email Settings, per-user Email Settings preferences, group-level email digest frequency (Daily / Weekly / Every post / Never), bell-icon Custom Notifications vs Chatter feed-post tradeoffs, automated-feed suppression on record types via Feed Tracking config, and the Chatter Settings org defaults that control whether new users start with everything-on. Triggers: 'chatter feed full of automated posts nobody reads', 'users complain about chatter email volume', 'turn off chatter notifications for a specific group', 'change default chatter digest frequency', 'stop process builder posts from filling the feed', 'NotificationFrequency invalid value', 'ChatterEmailsMD.settings will not deploy', 'custom notification recipient limit'. NOT for Custom Notifications API design (use apex/apex-custom-notifications-from-apex), NOT for Connect API / Chatter REST API integration patterns (use apex/apex-connect-api-chatter), NOT for Chatter group lifecycle, archiving, ownership and unlisted-group governance (use admin/chatter-group-governance).
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 22.0 KB |
| references/examples.md | markdown | 13.8 KB |
| references/gotchas.md | markdown | 17.0 KB |
| references/llm-anti-patterns.md | markdown | 10.7 KB |
| references/metadata-examples.md | markdown | 20.2 KB |
| references/well-architected.md | markdown | 9.4 KB |
| scripts/check_chatter_notification_tuning.pyexecutable | script | 26.2 KB |
| templates/chatter-notification-tuning-template.md | markdown | 3.1 KB |
templates/chatter-notification-tuning-template.md
View on GitHub# Chatter Notification Tuning — Work Template
Fill this in as you run workflow steps 1–4 in `SKILL.md`. It is the artefact the change record
points at.
## Scope
**Skill:** `chatter-notification-tuning`
**Request summary:**
**Who is complaining, and about which channel** (feed volume / email volume / bell / all three):
---
## 1. Diagnosis — where the volume actually comes from
Run as a View All Data holder (`FeedItem` direct queries require it — object_reference.txt
L136505–136507).
```sql
SELECT Type, COUNT(Id) posts
FROM FeedItem
WHERE CreatedDate = LAST_N_DAYS:30
GROUP BY Type
ORDER BY COUNT(Id) DESC
```
| `FeedItem.Type` | 30-day count | Routes to |
|---|---|---|
| `TrackedChange` | | Feed Tracking pruning — workflow step 3 |
| `TextPost` (automation ids) | | Flow / Apex migration — workflow step 4 |
| `TextPost` (human ids) | | Digest frequency, not suppression — step 5 |
| `ApprovalPost` | | `enableApprovalRequest` — gotcha 12 |
| other | | |
**Checker baseline** — paste the finding codes and counts:
```
python3 scripts/check_chatter_notification_tuning.py --manifest-dir force-app/main/default
```
---
## 2. Answers to the Questions to Ask table
| Question | Answer |
|---|---|
| Which channel is loud — feed, email, or bell? | |
| Who holds Modify All Data, and are they running the load? | |
| Which of the four frequencies (`P`/`D`/`W`/`N`) is the intended default, and why not `N`? | |
| Is the volume automated or human? | |
| Are we changing what new joins inherit, or rewriting existing members' choices — or both? | |
| Does the org have Experience Cloud / digital experiences enabled? | |
| What does "quiet enough" look like, measured? | |
---
## 3. The policy
`notification-policy.json` — lint with
`python3 scripts/check_chatter_notification_tuning.py --policy notification-policy.json --group-inventory groups.csv`
| Scope | Frequency | Reason |
|---|---|---|
| Org default (`User.DefaultGroupNotificationFrequency`) | | |
| Broadcast / announcement groups | | |
| Project groups | | |
| Social / interest groups | | |
**If any row is `P`:** the written justification, and the member-count headroom against the
10,000-member auto-switch (gotcha 3):
---
## 4. Changes, by surface
| Surface | Artefact | Change | Reversible? |
|---|---|---|---|
| `Chatter.settings` | | | |
| `ChatterEmailsMD.settings` | | | |
| Feed Tracking (`enableFeeds` + `trackFeedHistory`) | | | |
| `CustomNotificationType` + Flow `actionType` | | | |
| `CollaborationGroupMember` CSV | | | |
| `User` CSV | | | |
**Deliberate non-changes** — what you looked at and left alone, and why (this is the half that gets
questioned later):
---
## 5. Deviations and open items
Record anything that departed from the workflow, any `UNVERIFIED` claim you had to act on, and any
finding the checker raised that you accepted rather than fixed.
---
## 6. Re-measure
Date to re-run step 1: (two weeks after the change)
| Metric | Before | After | Target |
|---|---|---|---|
| 30-day `FeedItem` count by dominant `Type` | | | |
| Members on `P` | | | |
| Active users with `UserPreferencesDisableAllFeedsEmail = false` | | | |
| Checker ERROR/WARN count | | | |
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| writing-skillsobra/superpowersUse when creating new skills, editing existing skills, or verifying skills work before deployment | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |
| xlsxanthropics/skillsUse this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .xltx, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |
| shipping-and-launchaddyosmani/agent-skillsPrepares production launches. Use when preparing to deploy to production, or when asking what needs to be in place before shipping. Use when you need a pre-launch checklist, when setting up monitoring, when planning a staged rollout, or when you need a rollback strategy. | Stars: 119k | Updated | Claude CodeCodex | Verified | Install |
| childhoodthedotmack/claude-memBabysit a shipped release after merge, publication, or deployment. Verify published packages, production behavior, installed plugins, and late CI or user reports until the observation window is clean; use babysit for PR readiness before release. | Stars: 118k | Updated | Claude CodeCodex | Verified | Install |