How can a community owner transfer administration before leaving?

Plan the handoff around three things: who will take over, how the platform transfers ownership, and what the successor needs to know. Don’t assume an administrator role is enough to transfer the highest-level ownership; a service may reserve that action for a particular role. For example, Slack says only its current workspace Primary Owner can transfer workspace ownership, and there can be only one Primary Owner at a time. Those are Slack-specific rules, not rules for every platform. [S1] [S2]

Choose someone willing and authorized to manage the community. Agree on a handoff date and list open issues, recurring tasks, and important settings to review. Consider who will handle routine administration, account or licensing responsibilities, and billing-related tasks. Share only information the successor needs, through an appropriate channel; don’t put passwords or sensitive details in a general handoff note.

Check the platform’s current help pages or administrative controls for its exact eligibility rules. Verify whether the successor needs a particular role or account status, and whether your own role can perform the transfer. These are points to check, not universal requirements. If the service distinguishes between a workspace, organization, or another community type, use the instructions for the right type.

For a Slack workspace, the cited guidance says the Primary Owner selects another member, enters their password, and confirms; the transfer takes effect immediately. Slack’s Enterprise organization route is different: the Org Primary Owner contacts Slack with the proposed successor’s email. Slack recommends transferring before deactivating the account. Check the applicable official instructions rather than applying these Slack procedures to another service or assuming they fit every Slack setup. [S1]

Ask the successor to confirm they can access and use the new role. Review who will handle day-to-day administration, what should happen if the successor is unavailable, and whether billing or account contacts need updating. The exact permissions and confirmation steps depend on the platform, so use its controls and guidance rather than relying on a role label alone.

In Slack’s workspace process, ownership changes immediately and the departing Primary Owner becomes an Owner. Slack recommends checking that billing information remains accurate with the new Primary Owner. [S1] Slack describes the Primary Owner role as the highest-permission role and says other Owners or Admins can handle day-to-day work. [S2] These details don’t establish the permissions or billing settings of another service.

Use this sequence, adjusting it to the platform’s documented process:

1. Agree on a willing, authorized successor and a handoff date.
2. Verify eligibility and your authority to transfer ownership.
3. Read the current instructions for the correct community or account type.
4. Complete the transfer before leaving or deactivating your account if the service recommends that timing.
5. Ask the successor to confirm access and review outstanding administrative tasks.
6. Check billing contacts and other account responsibilities where applicable.
7. Record who now holds the role and where the successor can find relevant procedures.

Copyable note: “Administration handoff — [community name]. Proposed successor: [name or account identifier]. Planned date: [date]. Transfer method: [official platform procedure]. Open tasks: [list]. Items for successor to review: [settings, recurring duties, billing contact if relevant]. Confirmation: [successor confirms access on date].”

Treat this as a planning aid, not proof that a transfer succeeded. If the option is missing or the current owner is unavailable, check the platform’s documented escalation route. Support options may have eligibility limits; Slack’s published route for an unavailable Primary Owner is not a universal promise of help. [S1]