Source CMS allows organization administrators to securely transfer site ownership from one organization to another. This feature streamlines agency workflows, supports privacy during development.

Use cases

The following table describes common scenarios for transferring site ownership:

Prerequisites

Before initiating a transfer, ensure the following requirements are met:

• Administrative permissions: Only users with admin permissions can initiate or receive a site transfer.

• Site entitlements: The recipient organization must have an available site entitlement.

• Valid recipient: The recipient must have a valid, registered email address associated with an organization.

Transferring site ownership

Step 1: Initiate the transfer

1. Log in to Source CMS to open the Sites Dashboard.

2. On the Sites tab, locate the site that you want to transfer.
3. Click the Kebab menu icon on the site card.
4. Select Transfer Ownership.

5. Enter the email address of the recipient organization and click Continue. 

   Note

   Source CMS does not validate the recipient email address. The sender must ensure that the email address belongs to a valid organization and verify the transfer with the recipient. 

6. Click Transfer Ownership to confirm the transfer request.

Step 2: Recipient acceptance

1. The recipient receives a notification through Sites Dashboard.

2. The recipient must accept the transfer for it to complete. 

   If the recipient declines or does not respond, the sender can cancel the transfer.

Step 3: Completion and entitlement changes

• After the recipient accepts the invitation, Source CMS moves the site to the recipient organization.
• This action consumes the site entitlement for the recipient and frees the site entitlement for the sender.

• All platform-level site management permissions transfer to the new owner.

  Note

  CMS roles and permissions remain unchanged after a transfer and the recipient must review and manage user access manually.

• All transfer activity is logged in the Activity Feed for auditing and support.

Security and limitations

• Audit trail: All transfer activity is logged in the Activity Feed for auditing and support.

• Domains: Public and internal domain names are not transferred; recipients must configure these manually.

• Entitlement errors: If the recipient lacks an available entitlement, the transfer cannot proceed and an error message will display.

• Regional restrictions: Source CMS does not support transferring sites across AWS regions because subscriptions are not multi-region aware. AWS regions operate as independent, physically separated hubs.

Transferring site ownership