How often should you recommend that your client conduct a guest and channel clean-up?

The correct recommendation is Monthly . Guest and channel cleanup is an operational governance activity, not a one-time launch task. Slack environments evolve quickly: projects end, external partners change, guest access expires, channels become inactive, and sensitive collaboration spaces may no longer require the same membership. A monthly cleanup cadence is frequent enough to reduce access risk and channel clutter without creating excessive administrative burden. Option A is weak because ad hoc cleanup is reactive and usually happens only after a problem occurs. Option B may be too frequent for most organizations and can create unnecessary admin overhead unless the environment is unusually high-risk. Option D is not frequent enough; annual reviews allow stale guest access and unused channels to accumulate for too long. The point of guest and channel cleanup is to keep collaboration intentional, secure, and manageable. This cadence should be owned through the governance structure and executed by the appropriate admin or owner roles.

Reference topic: Governance Structure (Owner and Admin Roles) — operational governance cadence, guest lifecycle management, channel cleanup, and administrative accountability.

==========