Separate roles of ownership
Identify the contractual account owner, billing responsibility, community lead and operational backup. These may be different people. Record the appropriate organisational contact and review date, not private credentials. A visible host label does not necessarily establish authority over billing, contract changes or account recovery.
Document the legitimate route
Write how an authorised person would contact the provider or use its account-recovery process. Note required organisational evidence without retaining unnecessary private documents in the register. Do not assume that a departing volunteer can transfer every contractual relationship through a role selector. Provider rules and applicable agreements determine what changes are possible.
Review when responsibilities change
Check the register after a committee change, departure or billing transition. Confirm that contact routes remain usable and that access matches current responsibilities. Keep a record of completed changes and unresolved requests. An intended owner is not an established owner until the relevant process has actually completed. Name a responsible reviewer for every pending request.
A fictional ownership gap
A community discovers that its billing notices go to a former volunteer while moderation is handled by a current committee. It records the mismatch and follows the provider’s legitimate change process with appropriate authority. The group does not impersonate the former volunteer or place their password in a shared document. Until confirmation arrives, the ownership change remains pending and the continuity plan reflects that uncertainty.
Before you close this task
Keep a non-secret reference to the evidence that a provider confirmed an ownership change, together with its date and scope. Do not store recovery codes or identity documents in the register. Review access held by former volunteers through the authorised process, while preserving any required organisational records and unresolved provider requests.
Sources used for this page
These records support the facts and comparisons above. Merchant-controlled records are labelled so you can separate product claims from independent evidence.
- Mighty Networks administration — Merchant documentation · mightynetworks.com · Merchant-controlled · checked 2026-09-28
- Mighty privacy policy — Merchant documentation · mightynetworks.com · Merchant-controlled · checked 2026-09-28
- Mighty terms of use — Merchant documentation · mightynetworks.com · Merchant-controlled · checked 2026-09-28