PranavNagrecha/AwesomeSalesforceSkills / skills/admin/chatter-group-governance
chatter-group-governance
VerifiedUse when admins are governing the Chatter group lifecycle — creation policy, public/private/unlisted visibility decisions, group ownership transfer when owners leave, archived vs inactive vs deleted state changes, auto-archive behavior, naming conventions, group templates (Information Templates), and orphan-group cleanup after user terminations. Triggers: 'we have 800 dead chatter groups', 'group owner left the company who owns it now', 'should this group be public private or unlisted', 'when does a chatter group auto-archive', 'how do I delete vs archive a chatter group', 'we need a chatter group naming convention'. NOT for Chatter notification / digest / feed-noise tuning (use admin/chatter-notification-tuning), NOT for Chatter REST API integration patterns (use apex/apex-connect-api-chatter), NOT for Custom Notifications API (use apex/apex-custom-notifications-from-apex), NOT for Experience Cloud / Customer Community group access (different sharing model).
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 21.4 KB |
| references/examples.md | markdown | 15.5 KB |
| references/gotchas.md | markdown | 21.7 KB |
| references/llm-anti-patterns.md | markdown | 10.8 KB |
| references/metadata-examples.md | markdown | 18.7 KB |
| references/well-architected.md | markdown | 10.4 KB |
| scripts/check_chatter_group_governance.pyexecutable | script | 22.6 KB |
| templates/chatter-group-governance-template.md | markdown | 4.1 KB |
templates/chatter-group-governance-template.md
View on GitHub# Chatter Group Governance — Engagement Worksheet
Fill this in as you run workflow steps 1–5 in `SKILL.md`. It is the artefact you hand back; the checker
output pastes straight into sections 2 and 4.
**Skill:** `admin/chatter-group-governance`
**Org / sandbox:** _______________ **Date:** _______________ **Run by:** _______________
---
## 1. Request
**What was asked for (one sentence):**
**Scope** — tick one:
- [ ] Org-wide governance baseline (settings + permissions + policy)
- [ ] Targeted cleanup of an existing group population
- [ ] Offboarding response for a named user or deactivation wave
- [ ] Compliance / discovery request over the group population
---
## 2. Metadata baseline — workflow step 1
```bash
sf project retrieve start --metadata Settings:Chatter,PermissionSet,Profile --target-org <alias>
python3 scripts/check_chatter_group_governance.py --manifest-dir force-app/main/default
```
| Setting | Value found | Action |
|---|---|---|
| `allowChatterGroupArchiving` | | |
| `unlistedGroupsEnabled` | | |
| `allowRecordsInChatterGroup` | | |
| `enableInviteCsnUsers` | | |
| Permission | Granted where (profiles / permission sets) | Holder count | Action |
|---|---|---|---|
| Create and Own New Chatter Groups | | | |
| Manage Unlisted Groups | | | |
| Modify All Data (transfer capability) | | | |
**Blocking findings** (`CGG-UNLISTED-UNGOV`, `CGG-ARCHIVE-OFF`) — paste the checker lines, and what you
did about each:
---
## 3. Answers to the pre-configuration questions
Copy the answers, not just the questions. An unanswered row is a risk you are carrying into step 5.
| Question | Answer | Consequence if wrong |
|---|---|---|
| Who holds Manage Unlisted Groups? | | Group inventory is incomplete and says nothing about what it omitted |
| Is org-wide archiving on? | | Delete becomes the only cleanup lever |
| Which groups are read-mostly rather than post-mostly? | | They auto-archive while genuinely in use |
| Which groups hold files shared elsewhere? | | Deleting the group deletes those files everywhere |
| Who is the transfer target, person or service account? | | Ownership re-orphans on the next departure |
| Is a batch user deactivation in flight? | | Reciprocal follow relationships are hard-deleted, unrecoverable |
| Any group already has `CanHaveGuests = true`? | | The flag cannot be set back to false |
---
## 4. Group population — workflow step 2
```bash
python3 scripts/check_chatter_group_governance.py \
--manifest-dir force-app/main/default \
--group-inventory groups.csv \
--name-prefixes <agreed prefixes> \
--inactive-days 365
```
| Bucket | Checker code | Count | Disposition |
|---|---|---|---|
| Active, active owner | — | | leave |
| Active, inactive or missing owner | `CGG-INV-ORPHAN` | | transfer (step 4) |
| Active, no feed activity > threshold | `CGG-INV-STALE` | | archive |
| Active, no activity ever, ≤ 1 member | `CGG-INV-EMPTY` | | delete after confirming direct member count |
| Off-convention names | `CGG-INV-NAMING` | | rename or accept as legacy |
| Unlisted groups | `CGG-INV-UNLISTED` | | confirm a permission holder exists |
| Already archived | — | | leave |
**Naming convention agreed for this org:**
**Auto-archive exemptions** — groups getting `IsAutoArchiveDisabled = true`, with the reason each:
| Group | Reason it must not auto-archive |
|---|---|
| | |
---
## 5. Disposition decisions
**Transfer target chosen:** _______________ **Why this target and not a department head:**
**Groups delete-approved** — each row needs a file check before it is executed:
| Group | Member count (direct COUNT, not `MemberCount`) | Files shared elsewhere? | Approved by |
|---|---|---|---|
| | | | |
**Deviations from the standard pattern, and why:**
---
## 6. Post-change verification
- [ ] Checker re-run on the *re-retrieved* metadata tree — clean, or every remaining finding explained
- [ ] `CGG-INV-ORPHAN` count is zero on a fresh export
- [ ] `Chatter.settings` and the permission-set files committed to source control
- [ ] Offboarding runbook updated so ownership transfer precedes deactivation
- [ ] Next quarterly re-measure scheduled, with today's counts recorded as the baseline
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| receiving-code-reviewobra/superpowersUse when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementation | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |
| requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirements | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |
| using-git-worktreesobra/superpowersUse when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallback | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |
| verification-before-completionobra/superpowersUse when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |