Hand a project over to a client workspace
Transfer a completed project only after the client authorizes its repository and accepts ownership.
Last updated 2026-08-18
What you'll achieve
- Prepare a client handoff
- Accept with the correct repository
- Avoid accidental ownership changes
Prepare the handoff
Ask the client to add your Agency account to their destination workspace first. Open the connected project's Source control settings, then find Agency client handoff. Choose the client's workspace, decide whether the repository connection should continue and type the confirmation shown in the form.
Nothing transfers at this point. The handoff remains pending and the Agency can cancel it.
Client acceptance
A client workspace owner or administrator opens Client handoffs in Source control. They must choose a repository already authorized for their workspace. When preserving the connection, it must be the same repository used by the project.
Acceptance moves the project and its source-control connection to the client workspace together. Old repository role grants are removed so the client can assign fresh access. The client workspace's plan, limits and billing apply after transfer.
Review domains, paid add-ons, database ownership, collaborators and future support responsibilities with the client before acceptance. Contact billing@blinkhost.me before accepting if a commercial entitlement needs to move separately.
Help improve this page
Sign in to send page-specific feedback. For account-specific help, email support@blinkhost.me.