Agency handoff, client access and billing

Client access boundary

Organization membership applies across that workspace. Repository roles and time-limited collaboration grants can narrow source actions, but they are not a substitute for workspace isolation. For clients who must not see another client's projects, use a separate client workspace and grant only the people who should belong to it.

Handoff inventory

The destination workspace's plan, limits and billing apply after it accepts a project handoff. Before acceptance, record the project source and repository authorization, domains and DNS control, database bindings and live-data ownership, project assets, secret recovery responsibility, paid add-ons, collaborators, deployments and future support owner. Commercial entitlements do not silently transfer; contact billing@blinkhost.me before acceptance when an add-on or negotiated entitlement must move.

The client must authorize the intended repository. Acceptance removes old repository role grants so the destination can assign access again. Export source and relevant evidence before the handoff, and verify the destination's capacity before moving a production project.

Evidence and retention

Source activity records identify the action, actor and time. Authorized enterprise administrators can request an integrity-checked source evidence export; the generated download expires after seven days. Collaboration-history retention is the period shown for the workspace plan. Download records needed for a client dispute or audit before those product retention periods expire. A legal hold is exceptional and does not replace customer-controlled records.