On this page
- How an agency manages ChatGPT Business Hub for a client (short answer)
- Get written authorisation per client before you touch anything
- Who claims the business, and how the agency gets access
- Access hygiene: own accounts, least access, offboarding
- Reporting Hub data to clients under the Insight Data terms
- What agencies must never do with client Hub data
- Where Revnu fits: tracking AI answers and acting on gaps
- FAQ for agencies on ChatGPT Business Hub
- Make the client the owner, and make your process the product
- Related Business Hub guides
An agency manages ChatGPT Business Hub for a client by getting written authorisation, having the client claim and verify the business, taking access through the client's own invitation, and reporting Hub data back to the client only as a service provider under equivalent restrictions. That is the whole safe loop. Everything below is how to run it repeatably across a roster.
Business Hub is OpenAI's beta product for businesses in ChatGPT, and the terms behind it are specific about who can see what. Agencies that treat it like a normal analytics login will eventually create a problem for a client. Agencies that write down the process once and follow it every time can sell Hub management as a clean service. This guide, as checked on 18 November 2026, covers the process, the access rules, the reporting rules and the things you must never do with a client's Hub data. For background on the product itself, start with ChatGPT Business Hub: What It Is and Who Can Use It.
How an agency manages ChatGPT Business Hub for a client (short answer)
Use the same four steps for every client, in this order.
Authorise. Get written permission from the client to manage their Hub presence and to see their Hub data.
Claim. The client, or their authorised representative, claims the business with an account they control and completes verification.
Invite. The client's admin invites the agency through Business Hub and grants access to manage the business or its agent. Each person on your team signs in with their own ChatGPT account.
Report. You report Hub data back to the client, and only to the client, as a service provider acting under restrictions equivalent to the ones OpenAI places on them.
The order matters. An agency that claims the business itself, or logs in on a shared client account, has skipped the two steps that make the arrangement defensible. Keep the claim in the client's hands and the paper trail in yours.
This is also separate from ChatGPT Business workspace roles such as Owner, Admin, Analytics Viewer and Member. Workspace roles do not automatically grant Business Hub access, so a seat in the client's workspace doesn't mean you can see the Hub.
Get written authorisation per client before you touch anything
Get a signed, client-specific authorisation before you open Business Hub. The Insight Data terms put the permission question on the business, not on you.
Under section 6 of OpenAI's Businesses in ChatGPT Terms, any Insight Data OpenAI provides may be used only to measure, analyse, optimise and report on the business's own use of Businesses in ChatGPT and the services (Businesses in ChatGPT Terms). Your client is the party bound by that. You are a third party until they bring you in.
Put four things in the authorisation, per client, not as a blanket agency template:
Scope of management. Which parts of the Hub you will touch: the business profile, product information, the Business Agent, or reporting only.
Data access. An explicit statement that the client is giving you access to its Hub data so you can measure, analyse, optimise and report on its use of the Hub.
Service-provider restrictions. A clause committing you to restrictions equivalent to the ones the client is under: use only for the client's own purposes, no disclosure to anyone else, no commercial exploitation.
Duration and offboarding. When access ends, who removes your team, and what you delete.
Keep the signed copy where an account lead can find it in a minute. If a client later asks what you were allowed to do, or OpenAI queries an arrangement, that document is the answer. If a client's contract is vague on any of this, fix the contract first. The Hub is a beta, so the rules can change, and a per-client record lets you adapt without renegotiating from scratch.
Who claims the business, and how the agency gets access
The client claims the business, and the agency gets access through the client's own invitation in Business Hub. Never borrow the client's login.
A business owner or authorised representative claims the business in ChatGPT Business Hub and verifies it using one of the methods offered, such as business phone, email, website domain or Shopify. After approval, the claiming admin can invite teammates and grant an agency access to manage the business or its agent. Each person uses their own ChatGPT account. The full claim flow is in How to Claim and Verify Your Business in ChatGPT.
For a typical client, run it like this:
Have the client claim the business using an account they control, not an agency-owned or shared one.
The client completes the claim and any required identity verification themselves.
The client's admin invites your named staff through Business Hub.
Do not forward the personal claim invitation. It belongs to the person it was sent to.
Depending on how the business was claimed, invitees may need to belong to the associated ChatGPT workspace. If so, the client adds you there first.
If an invitation is blocked, contact OpenAI Support rather than working around it.
The reason to insist on this is ownership. If the agency claims the business, the client's presence in ChatGPT sits behind your account, and the day the contract ends you have a handover problem. If the client claims it and invites you, ending the contract is a removal, not a migration.
Is there an OpenAI partner program for agencies?
Whatever you find, a partner badge does not replace client authorisation. You still need written permission from each client and access granted by the client's own account owner. Do not claim any official partner status to clients unless OpenAI's published terms clearly support it.
How do we set up a ChatGPT workspace for a client?
Have the client create or own the workspace and sign up with a company email, then invite your team as named users. First get written authorisation, agree which roles each of your people need, and confirm who the owner is. After the invites go out, check that each person sees only what they should. Write down the setup steps so you can repeat them for the next client without improvising.
Access hygiene: own accounts, least access, offboarding
Every agency person uses their own ChatGPT account, gets the least access that does the job, and is removed the day they leave the account.
Three rules cover most of it.
Own accounts only. Never share one agency login across the team and never use a client's personal credentials. Individual accounts mean the client can see who has access and remove one person without disturbing the rest.
Least access. Grant management access only to the people who need it. An analyst who only compiles the weekly report does not need the same rights as the person editing the business profile. Keep a short list per client: name, role, date invited, reason.
Offboarding on a schedule. Run a standing check each quarter, and a same-day check when someone leaves your agency or moves off the client. Removal is done by the client's admin in Business Hub. When a client contract ends, offboarding is the last deliverable: confirm in writing that your team's access is removed and that you have deleted any client Hub data you held.
Keep your own storage tidy too. Because Hub data is restricted, treat anything copied out of it as sensitive: keep it in the client's folder, with the client's access list, and nowhere else. There is no documented Hub export or API, so most of what you hold will be notes and weekly figures you typed or copied. That makes your own filing discipline the control. For the weekly rhythm those notes feed, see ChatGPT Business Hub Metrics and Weekly Reporting.
Can one agency workspace manage several clients?
Keep each client in its own separate space rather than pooling them. Whether you work inside the client's ChatGPT workspace or Hub profile, the client should own it, and you join as a named user with limited access. Never run several clients through one shared login, because you can't cleanly remove one client's data or access later. Keep a simple register of which person on your team has access to which client, and review it monthly.
How do admin roles work for agency staff?
Give agency staff the lowest role that still lets them do the job, and keep owner or admin rights with the client. The exact role names and options change, so check OpenAI's current admin documentation before you set anything up. As a rule, assign each person an individual seat tied to their own work email, never a shared mailbox. Every action then traces to one named person, and removal at offboarding takes one step.
Should agencies use SSO, SCIM and connectors?
Use them only if the client's plan offers them and their IT team approves. SSO ties sign-in to the client's identity system, and SCIM automates adding and removing users, which makes offboarding your agency far safer. Treat connectors cautiously: each one can expose client data to the tool, so enable only what the work needs and have the client sign off. Confirm exact availability in OpenAI's current admin documentation.
Reporting Hub data to clients under the Insight Data terms
You may report Hub data to the client it belongs to, as their service provider, and the report stays inside that client relationship.
Here is what the terms say that matters for reporting. Insight Data is OpenAI's Confidential Information. Under section 6 it may be shared with service providers acting for the business under restrictions equivalent to the business's own, and the business may use it only to measure, analyse, optimise and report on its own use of Businesses in ChatGPT and the services (Businesses in ChatGPT Terms). An agency reporting to its own client, with a signed authorisation that carries those restrictions, fits that arrangement. Anything beyond it needs OpenAI's written authorisation.
Build the client report around three separate populations of data, and never blend them into one claim:
| Data population | What it is | How to label it |
|---|---|---|
| Hub activity | Aggregated activity shown inside Business Hub | "As shown in Hub, data through [date]" |
| Synthetic checks | Answers from prompts you deliberately chose | "Sample of chosen prompts, not real user activity" |
| Website outcomes | Sessions and sign-ups measured on the client's own site | "Measured on site analytics" |
There is no user-level join between these, so do not infer which prompt sent which visitor, and do not claim that Hub mentions caused site sessions. Report each number with its source and say plainly what it cannot tell the client.
Treat the exact Hub controls, date ranges, how many topics are shown and which countries are supported as items to recheck each month, because this is a beta. If you only observed a behaviour in a screenshot, say "observed" and do not present it as guaranteed product behaviour. For turning the numbers into decisions rather than slides, see Turn ChatGPT Business Hub Data Into Revenue Decisions.
What agencies must never do with client Hub data
Never take a client's Hub figures out of the client relationship, and never treat them as agency marketing material.
The list is short and absolute:
No case studies or public results. Do not publish a client's Hub figures, or anything derived from them, in a case study, blog post, social post or pitch deck. Without OpenAI's written authorisation, Insight Data and its derivatives are not yours to disclose.
No screenshots in sales material. A cropped Hub dashboard in a new-business deck is still disclosure.
No cross-client benchmarks. Do not average Client A's numbers into a chart shown to Client B, or to a prospect.
No using one client's data to pitch another. Even anonymised, it is a derivative of Confidential Information.
No commercial exploitation. The terms rule out using Insight Data to build a product or service of your own on top of it.
No identifying individuals or building audiences. Hub activity is aggregated for a reason. Do not try to work out who is behind it or assemble audience lists from it.
No sharing with anyone outside the arrangement. That includes freelancers and subcontractors who are not covered by equivalent restrictions in writing.
If you want a worked example for a training session or a thought-leadership piece, invent one. Label it clearly as a hypothetical, with made-up numbers unrelated to any real client, rather than rounding or disguising real figures. Nobody should be able to read an agency's public content and reverse out a client's Hub performance.
And be straightforward with clients about the beta: OpenAI does not guarantee that Businesses in ChatGPT will remain available or receive any particular placement, ranking or visibility. Never sell Hub management as a guaranteed position.
Where Revnu fits: tracking AI answers and acting on gaps
Revnu is the growth agent that turns what you learn about a client's AI visibility into published pages, outreach and ads, run within the owner's approvals.
Be precise about what it is and is not. Revnu does not connect to Business Hub and does not pull Hub data. It also runs lead research, outreach and paid campaigns across connected accounts. Nothing spends without approval.
For an agency, that means the Hub work and the growth work stay cleanly separate. Hub data stays inside the client relationship under the authorisation you signed. The AI-answer tracking and the content that follows from it come from Revnu's own measurement of ChatGPT, Claude, Perplexity and Gemini answers and Google, so with the client's permission those findings can go in a case study without touching Insight Data.
On the agency side, Revnu produces client blogs, LinkedIn posts and outreach under your agency's name, and you approve everything before it goes out. If you want the reporting side of that, read AI Search Reporting for Agencies: What Clients Need. Pro is $99 a month, self-serve, so you can start with one client's business and a single job.
FAQ for agencies on ChatGPT Business Hub
These are the questions agency owners ask most when they set this up for the first time. Each is answered in full in the FAQ that follows the conclusion, so use that as the quick-reference version for your team and your clients.
How do Business, Team and Enterprise admin controls compare?
Plan names and admin features change often, so verify against OpenAI's current plan comparison before you advise a client. In general, larger plans add more centralised controls such as identity management and audit options, while smaller plans keep admin simple. Ask the client what they actually need: who manages users, how access is removed, and what records they must keep. Choose the plan from those needs, and record your reasoning in the client file.
Make the client the owner, and make your process the product
The agencies that win ChatGPT Business Hub work won't be the ones with the cleverest dashboards. They'll be the ones that can show a client the signed authorisation, the client-owned claim, the named access list and a report that keeps Hub data inside the relationship. Write that process down once and run it for every client. Then start the growth work that sits beside it: connect one client's business to Revnu at $99 a month, let it track how that business shows up in ChatGPT, Claude, Perplexity and Gemini answers and Google, and approve the first pages it writes to close the gaps.
Related Business Hub guides
Written by
Co-founder and CEO, Revnu
