IT playbook · AI Employee: Ivy

Slack Channel & Group Management

Channel provisioned within policy inside 60s

Install this playbookBack to marketplace
The problem

Slack accumulates: channels for every project, group for every function, archived channels resurrecting when someone joins, DM groups that turn into channels, private channels nobody remembers making. After 3 years the workspace has 4,000 channels, 400 user groups, and organizational drift that makes finding the right conversation impossible. Every reorg creates new duplicates; nobody cleans up old ones; IT gets 20 tickets a day for "add me to X channel" or "can you set up Y group."

At a glance
Trigger
Chat
Approvals
Workspace admin auto-approve within policy
What it does
Writes to your systems
Systems
Slack Admin · Okta
How it feels in production

An hour-by-hour walkthrough.

Sarah requests in Slack: "@Ivy set up #proj-titan-eng-2026 for the Titan project, add engineering team leads." Ivy resolves "engineering team leads" from HRIS + org structure, creates the channel with the requested members, applies the standard project-channel template (topic, description, permission model, retention policy), and confirms: "Created #proj-titan-eng-2026, added 8 members (list). Standard project-channel policy applied. When the project ends, I'll suggest archival." Ongoing hygiene: - Every quarter, Ivy scans for stale channels (no messages in 90+ days) + surfaces archival recommendations - User group membership auto-updates from HRIS (new hire in eng auto-joins @eng-all) - Duplicate channel detection ("#titan-project" + "#titan-proj" + "#project-titan") - Access reviews: private channels reviewed by owner quarterly for stale members - Naming convention enforcement (new channels flagged if they don't match #topic-team-context pattern) Weekly IT ops digest: channel count trend, archive candidates, duplicate suggestions, user group drift. Workspace stays organized rather than sprawling.
How it works

Step by step.

  1. 01

    Handle channel + group requests

    Slack DM or command intake. Resolve member expressions ("engineering team leads") from HRIS. Apply naming + template.

    Slack · HRIS · Channel template library
  2. 02

    Enforce naming + template + policy

    Naming convention checks, retention policy application, default membership, description + topic. Standard-per-type templates.

    Slack API · Naming validator · Template registry
  3. 03

    Auto-manage user group membership from HRIS

    New hires auto-join role-based groups (@eng-all, @sales-all). Departures auto-remove. Team changes auto-reflect.

    HRIS · Slack user groups
  4. 04

    Quarterly hygiene: archive + dedupe + review

    Stale channels surface archival. Duplicate channels surface merge candidates. Private channels get owner-review prompts.

    Slack · Hygiene scans · Owner-review flow
  5. 05

    Weekly digest + trend

    Channel counts, growth rate, archival candidates, duplicate patterns. IT ops visibility on workspace health.

    Analytics · Slack digest
Systems and wiring

What you connect to make this run.

Slack · Microsoft Teams

read+write

Channel + user group lifecycle. Read state; write creation, archival, membership changes.

HRIS · Directory

read

User group membership derivation from role + team + department.

Channel template library

read

Standard templates per channel type: project, team, function, incident, customer. Applied at creation.

Analytics · Hygiene scans

read+write

Scheduled scans for staleness, duplicates, orphaned channels. Ownership reassignment flow.

What changes

Before and after, honestly.

Time to create channel + add members
Before
1-24 hours
After
Under 60 seconds
Stale-but-active channels in workspace
Before
40-70%
After
Under 10%
IT hours per week on Slack admin
Before
8-20 hours
After
1-2 hours
User group drift (members wrongly in / out)
Before
15-35%
After
Under 3%
Related

Playbooks that pair with this one.

IT

Identity Group Management

Group management pattern applies across Slack, Okta, Google Workspace.

HR

Manager Change Cascade

Manager changes trigger Slack group membership updates.

HR

Employee Offboarding

Offboarding removes Slack access; part of the cascade.

Frequently asked

Answers about this playbook.

What if a channel needs unusual permissions or retention?

Custom channels supported with explicit approval. Standard template is default; custom is one-click override with reason.

How does it handle Slack Connect (external company channels)?

Slack Connect has stricter policy: legal + security review for new external channels. Ivy routes through legal-vendor review for approval.

What about incidents that need immediate channel creation (P1 outage)?

Incident-response templates for #inc-YYYY-MM-DD-N channels. Fast path with auto-membership from on-call + incident-response team.

How does user group derivation handle matrix orgs?

Primary + dotted-line memberships supported. Some groups auto-include dotted-line (project working groups); others primary-only (team ops channels).

Can we enforce channel-naming conventions retroactively?

Yes — retroactive rename campaign supported with owner approval per channel. Non-compliant channels flagged in digest for owner action.

See it run on your data.

Free plan, no credit card. Connect the systems this playbook needs and run it against a past event first.

Book a demoMore IT playbooks