Direct answer
Agree ownership, administrator access, licence status, handover method and ongoing responsibility in the proposal or contract before work begins. Treat domains, hosting, repositories, analytics, source files, fonts, plugins, images, datasets and subscriptions separately: access to an account does not automatically mean that every asset or licence can be transferred.
Why it matters
Website projects combine work created for the client with third-party services and licensed components. Confusion often appears at handover, when someone assumes that a login, a source file or an installed plugin carries rights that were never agreed or cannot be assigned.
Clear allocation also prevents operational dependence. The right people should know which account is the source of truth, who can approve changes, who pays renewals, how access is recovered, and what happens if a service or supplier changes.
What to agree
Record the contracting party, the owner or controller of each important account, required administrator access, repository and source-file delivery, third-party licence terms, renewal and billing responsibility, support boundaries, and the handover or exit route. Keep credentials out of public documents and rotate access through the agreed account owner when team members or suppliers change.
For third-party material, confirm whether the licence is transferable, client-owned, supplier-owned, subscription-based or limited to a particular use. If it is unclear, do not promise transfer; resolve it in the project agreement.
Limits
Ownership and licensing depend on the applicable contract, jurisdiction and the terms of each third-party provider. This is practical project guidance, not legal advice. Obtain appropriate legal review for a disputed, regulated or high-value arrangement.
Soft next step
Before signing off a website project, list every account, file and licence that the site depends on, then record its owner, access route, renewal responsibility and transfer condition.