Teams and agencies

The Team plan is for two kinds of work: a team collaborating on the same brands, and an agency running brands for clients. Both use the same handful of pieces.

What Team adds

• Shared brands: brands belong to the organization, so everyone in it can work on them.
• One pool: 25,000 credits a month and 250 GB of storage, shared across the org.
• Auto-join by email domain: claim your company domain and new signups with that email join automatically.
• Extend a brand to a client's domain: give one client's team access to one brand without adding them to your whole org.
• A shareable brand page: a read-only view of a brand to send to clients.

Onboarding a brand into the team

When you belong to a team, the drop screen that sets up a new brand asks where it should go, and defaults to the team. Anyone in the team can do this, not just admins. That default is deliberate: a client brand belongs to the whole team from the moment it exists, and any member should be able to bring one in without an admin moving it afterwards.

Pick Private to keep a brand in your own account instead. Your choice is remembered for next time.

Two consequences worth knowing:

• A brand in the team draws on the team's pool for credits and storage, and everyone in the team can use it. There's no cap on how many.
• A private brand is yours alone, and your personal plan caps how many you can have (Free and Team member: one). If you're at that cap, the answer is usually the team, not an upgrade.

Changed your mind after the fact? Brand settings has a Brand location control that moves a brand between your account and a team. Moving is stricter than creating: you must own the brand and be an admin of the team it's moving into or out of. Picking the right destination up front saves the round trip.

Auto-join for in-house teams

Claim your company's email domain on the org's billing page, and anyone who signs up with that email joins as a member. Common email providers (gmail, outlook, and the like) can't be claimed. If two orgs claim the same domain, the second goes to a review queue.

Extending a brand for agencies

Say you're an agency and your client is WWF. You want WWF's team on the WWF brand, but not in your whole org. Turn on their email domain for just that brand, and their new signups land as collaborators on that one brand. You keep owning it, and your other clients stay private.

Who pays, for agencies

Even when you extend a brand to a client, the agency still owns it and pays for everything that touches it. That works well when you bundle braaand into a retainer and bill costs back using the per-brand breakdown. If you'd rather the client pay, let them own the org and add yourself as a collaborator. See who pays for what.

Seats

Team is a flat price per org, not per seat. Add or remove people freely; the bill doesn't change. The limits are on credits and storage, not headcount. To control who can do what, brand roles (admin, editor, read) apply per brand.