Channel-Organization Migration

❌ This issue is not open for contribution. Visit Contributing guidelines to learn about the contributing process and how to find suitable issues.

Overview

As part of #5786, existing channels will need an intuitive way to be able to join organizations. This creates potential bottlenecks around channel ownership, as many channels have editors that no longer exist, but still hold ownership. This causes ownership conflicts at the organization level, as one channel editor may part of organization A, and another may be part of organization B/none.

To mitigate migration woes, a new channel-to-organization invitation flow will be created for both users, and site administrators.

• Users need to move channels they own to organizations they belong to
• Users need to request administrative help on contested channels
• Administrator need to move channels to organizations manually
• Administrators need to solve channel migration disputes efficiently

Scope

This issue encompasses all subsequent issues related to channel-organization migration. This work is required as part of #5953 to allow users to transfer their channels to newly created organizations.

Guidance

This issue encompasses a new backend-frontend flow, which may include:

Backend

• Modifications of existing backend models to accommodate channel-organization invitations

Frontend

• Allow users to add channels to organizations
• Allow users to request administrator migrations for contested channels
• Allow administrator to manage channel migrations
• Allow Administrators to manage contested channels

AI usage

No AI has been used in the making of this issue.

This is a tracking issue rather than a standalone contribution, and it names no files, tests, or entry points. Start by reading the related issues #5786 and #5953, then review the backend and frontend guidance here. The overall work is done when the planned channel-to-organization invitation, migration, and dispute-management flows are implemented.