Handing off a Blanca's Builder project to a client or new owner

In Blanca's Builder, project ownership is primarily linked to the account that created it. This account is responsible for all billing, subscription management, and overall administrative control. When handing off a project, the goal is to transfer this administrative and financial responsibility to the new owner's Blanca's Builder account.

It's crucial to distinguish between transferring project ownership and simply granting access. Granting access allows multiple users to collaborate on a project without transferring the underlying ownership or financial obligations. A full handover, however, changes the primary responsible party.

The most straightforward way to transfer ownership is through the Blanca's Builder dashboard. Navigate to the specific project you wish to hand over. Within the project settings, you'll find an option to 'Transfer Project Ownership.' This feature typically generates a unique transfer link or requires you to enter the email address of the new owner's Blanca's Builder account.

Once initiated, the new owner will receive a notification or an email with instructions to accept the transfer. Upon acceptance, the project, along with its associated assets and current billing cycle, will be moved to their account. It's vital that the new owner has an active Blanca's Builder account to facilitate this process.

Before initiating the transfer, ensure all outstanding invoices are settled and that the new owner is aware of the current subscription plan and any recurring charges associated with the project.

Domain names are often integral to a project and require separate attention during a handover. If the domain is registered directly within Blanca's Builder, transferring ownership will typically move the domain management to the new owner's account automatically upon project transfer. However, if the domain is registered with a third-party registrar (e.g., GoDaddy, Namecheap), you'll need to coordinate with the new owner to either update the DNS records to point to their Blanca's Builder account or transfer the domain registration entirely to them.

It's highly recommended to provide the new owner with all necessary login credentials for the domain registrar, including control panel access, if they are managing the domain independently. Clearly communicate the current DNS configuration and any specific records (like CNAME or A records) essential for the project's functionality.

Projects often rely on 'secrets' such as API keys, database credentials, or external service tokens. These sensitive pieces of information are stored securely within Blanca's Builder's environment. When transferring ownership, these secrets are typically migrated with the project. However, it's a best practice to review and, if necessary, regenerate these secrets with the new owner. This ensures that any previous access credentials are invalidated and only the new owner has control.

The 'Memory Bank' in Blanca's Builder, which stores AI-generated content, conversational data, and learned preferences, is also transferred with the project. This ensures continuity for any AI-driven features. It's a good idea to inform the new owner about the contents and purpose of the Memory Bank, especially if they will be managing or extending the AI functionalities.

Once the transfer is complete and accepted by the new owner, verify that all aspects of the project are functioning correctly under their account. This includes checking website accessibility, form submissions, and any integrated services. Ensure the new owner has successfully updated their billing information and that future invoices will be directed to them.

Provide the new owner with comprehensive documentation, including any custom code, specific configurations, or external service integrations. A brief training session on managing the Blanca's Builder project might also be beneficial. Finally, remove your own access from the project after ensuring the new owner has full control and is comfortable with the setup. This minimizes security risks and clarifies ownership.