Discuss your ads
Agency operations · 3 MIN READ

Managing ChatGPT ads for clients: ownership, access and handoff

Keep client accounts, billing, permissions and campaign approvals clear from onboarding through offboarding.

Who owns the account headline with client and access keys held by a hand.
Original AI-generated editorial artwork. Illustrative, not a platform screen or an actual campaign result.

The client should know who owns the ad account, who pays the media bill and who can change spending settings. Set that up before exchanging creative files.

Shared logins make it difficult to see who changed the account. Use supported named-user access and give each person the access needed for their work.

Record ownership and payment responsibility

Write down the advertiser entity, account owner and payment approver. Advertiser availability depends on the relevant legal and billing entity, so an agency should not substitute its details simply to avoid a client’s restriction.

Keep the client in control of their account and underlying assets. Your service agreement can explain what you manage, the approval process and how access ends.

Choose the correct kind of access

OpenAI’s identity and access guide distinguishes organization-wide roles from ad-account roles. ChatGPT workspace or API organization access does not automatically grant Ads Manager access.

Inspect the role at the correct level and test that the named user can complete the intended work. Use a viewing role for someone who only needs reports where the available role supports that.

A person can have direct access and group-based access. Record both when reviewing permissions. Removing one route can leave the other active.

Keep approvals next to the campaign record

Save the approved offer, destination, creative, country, conversion definition and spending ceiling. Record who can approve material changes and how the approval is documented.

For each review, show spend, outcomes and the proposed next action. If the agency recommends increasing budget, include the reason and the new ceiling. Do not bury the change inside a performance screenshot.

Keep API credentials in the supported server or secure credential store. Do not paste them into an onboarding document or a screenshot sent for review.

Agree on the handoff before work starts

Agree how the client receives the final campaign record and approved assets, which access is removed and who checks any remaining spend. The account should still have an appropriate owner after the agency leaves.

Review named users and groups together. Check the actual remaining permission after removal. Keep a brief completion record so the client knows the handoff is finished.

The launch checklist covers readiness checks for the next operator. A clear handoff leaves them with current settings, measurement definitions and open issues, rather than a pile of unexplained screenshots.

Sources and review date

Official documentation checked on 2026-10-12. Availability and features can change; confirm them before launch.

← All insights

Choose whether to allow optional cookies. You can change your choice at any time.

Read our privacy policy