All articles
On this page
Teams & Cloud
Setting Up HQ for Multiple Brands
Holding companies, venture studios, and anyone running several brands or businesses under one parent who wants to build skills once and use them everywhere.
If you run several brands, you probably want two things from HQ: build your skills and workers once at the parent level, and let each brand keep its own context (its knowledge, brand voice, projects, and files). HQ supports two setups for this. Which one fits depends on one thing: whether everyone on your team works across all the brands, or some people should only see one.
How HQ keeps things separate#
- The company is the main wall. People are added to a company, and that decides what they can see.
- Inside a company, folder permissions can hide a folder from members and guests. Owners always see every folder. Admins see nearly everything too.
So if some people must only see one brand, each brand needs to be its own company. If the same team works on everything, one company is simpler.
More on companies and access in Companies, Projects, and Repos and Permissions in HQ: Who Can See What.
Which setup fits you#
| Your team | Setup |
|---|---|
| The same core team works across every brand | One parent company, with a folder for each brand |
| Some people should only see one brand | One company per brand, plus the parent |
| Not sure yet | Start with one parent company. It's the simpler setup. |
Option 1: One parent company (recommended)#
This is the simplest setup, and it works well when the same people work across all your brands.
- Create one company for the parent.
- Give each brand its own folder for its context: knowledge, brand voice, projects, and files.
- Build your shared skills and workers in the company. To set who can use or edit each skill, open the company's Skills page in the HQ console. Every brand can use them.
Each skill can be set to:
- Open: everyone can edit it.
- Locked: everyone can use it, and only the people you choose can edit it.
- Private: only the people you choose can see it.
You can use folder permissions to hide a brand's folder from members and guests. Owners still see every folder, and admins see nearly everything.
Option 2: One company per brand#
Use this when some people should only work on certain brands, like a brand manager or an agency partner who shouldn't see the others.
- Create one HQ company for each brand, plus one for the parent.
- Build your skills once in the parent company.
- Copy them into each brand company with the Client Service pack, from the HQ Marketplace. See Capability Packs.
- Invite people only to the brand companies they should see.
The trade-off: copied skills don't stay in sync. When you update a skill in the parent, you install the update into each brand again.
If you're an owner of several companies, /team-access --all-owned sets your team's default folder access in all of them in one pass. You still invite people to each company separately.
Already have one brand set up as its own company?#
Going with one parent company: the easiest path is to turn the company you already have into the parent.
- Rename it to the parent's name (see below).
- Move that brand's content into its own folder.
- Add a folder for each of your other brands.
Nothing else has to move, and your billing stays the same.
You can also create a brand-new parent company and move the brand into it. That means moving files, skills, secrets, connected apps, and members, plus a billing change. If you want to do it that way, reach out to the HQ team first so we can help.
Going with one company per brand: keep your existing brand company as it is, and add the parent company alongside it.
Renaming a company
An owner can change a company's name by typing this in Claude Code or Codex:
hq company rename "New name"This changes the name people see. The company's short ID (the one in folder paths and commands) stays the same and can't be changed.
What not to do#
Don't publish your skills to the HQ Marketplace to share them between your own companies. Marketplace packs are public, so anyone could install them. Use the Client Service pack instead.
Common questions#
Can a skill be shared live across companies, without copying?
Not yet. It's planned, but for now each brand company needs its own copy.
Does each brand company need its own plan?
Each company has its own billing and pays for its own usage. One company's plan never covers your other companies. Reach out to the HQ team before making changes so your plan is set up the right way.
If you get stuck#
See The "I'm Stuck" Guide, or report it with /hq-bug. It packages the details for the team automatically.