A workspace is the thing you pay for and where everything lives: the team, the limits and the settings. A brand is what publishes, with its connected accounts and its bio page. A client is the company that commissions the work, with a registered name and a tax number, and it only appears in agency workspaces.
Three rows, and what hangs off what
Most tools in this category have two levels: the account and the profile. There are three here, and the third one is not always present. Knowing which is which saves the single most repeated conversation any team has while moving in, the one that starts with where does this go.
| What it is | What hangs off it | |
|---|---|---|
| Workspace | The unit you contract: one plan, one set of limits, one team | The people, the roles, the settings and the connected accounts paid for |
| Brand | What publishes, with a name and a face of its own | Its social accounts, its bio page, its posts and its metrics |
| Client | The company that commissions the work, with a fiscal identity | Its brands, its portal contacts and its documents |
All three are separate database rows rather than labels on the same object, and that is the difference between being able to split access, invoicing and reporting from one another, and having to pick one of the three to organise by.
The workspace is the unit you pay for
Everything that is paid for is paid per workspace. The limits belong to the whole workspace and not to each person, so adding somebody to the team does not move the invoice on its own: it moves it if that person takes the last seat the plan has. There are five quotas and none of them is the number of brands: members, storage, connected social accounts, ad accounts and the contacts reached by the DM automation. Which one runs out first, and how to read it, is in seats and quotas.
The workspace also decides the vocabulary, because there are two kinds and they do not use the same words internally. An agency workspace works for third parties. A creator workspace runs its own brands: one person with their own brands, or a company running its own marketing with an in house team, which signs up the same way and moves to the creator plan built for a team when the team grows. The kind is chosen when the workspace is created, and it turns out to be the answer to questions that surface a long way from that screen.
One person can belong to several workspaces at once without stopping being the same person: a freelance editor keeps a creator workspace of their own and works inside two agencies' workspaces, holding a different role in each. What changes between one and the next is the membership, never the account. That is why the workspace sits in the address of every screen rather than in a dropdown you have to keep an eye on: glancing at the browser bar tells you who you are working on behalf of.
It is also the boundary of what goes away when the bill stops. There is no free plan underneath: a workspace whose trial ends without a subscription is locked read only, with its connected accounts released. The data and the history come back on paying; the Drive and media library files are deleted fourteen days later, with two warnings first. In the meantime there is no floor holding half a tool upright.
The brand is what publishes
A brand is not a folder and not a colour on the calendar. It is the row that owns the connected accounts, which makes it the row that decides which networks are in front of you when you write a piece: you write once and it goes out to the networks that brand has connected, not to the workspace's entire collection.
It is also the row that owns everything publishing produces. Its link in bio page, its scheduled posts, its messages and comments, its per network metrics and the mode of its monthly report belong to it rather than to the workspace. That is why a brand can be looked at on its own without filtering anything, and why two brands in one workspace can run rhythms, tones and calendars with nothing in common. An agency holding ten brands at once is exactly that case, told from the inside, in one workspace, many brands.
A client only appears when you invoice a third party
A client is a company, not a profile. It carries a registered name, a tax number, an address, a country, the language it is written to in, an EU VAT number when the invoice crosses a border inside the Union, and whether its invoices carry IRPF withholding, the income tax a Spanish invoice retains on account. Those fields exist because documents with consequences are built from them, not because they look tidy.
Its brands, its portal contacts and its documents hang off the client. That is what lets two brands be invoiced together and reported on separately, or the other way round. It is also where the approval switch lives: review is turned on client by client rather than for the whole workspace, because some clients want to see every piece and some would rather not hear about it.
Portal contacts hang off the client rather than off the workspace, which is why the same email address can be a contact of two of the agency's clients without one overwriting the other. A person is a member of an agency once, and a contact of as many of its clients as the work requires.
A creator workspace has no clients. Brands hang straight off the workspace and the word client appears on no screen, which is not a translation and not a preference: the row an agency sees as Clients is drawn as Brands there, and a script checks on every deploy that the wrong word has not slipped through. The team, the conversations and the files work the same way in both kinds, and that is covered in tasks, chat and Drive.
Everything in this article happens in one place in GoFeed.
Try it freeHow many brands fit, and why it is not a plan number
This is where almost everybody looks for a figure that does not exist. No plan says ten brands, because brands are not counted. Connected social accounts are.
The rule is short. Every brand takes at least one connected account, and a brand with several takes as many as it has. With ten accounts contracted and nothing connected there is room for ten brands of one account each; if nine of those ten sit on a single brand, there is room for one more. More brands means more connected accounts, and that is a plan figure, which is why it lives on the pricing page and is read from the live catalogue.
It is a more useful way to count than it first looks. A brand that only publishes on Instagram costs what an empty folder costs, and a brand with six networks costs six, which is roughly the work it makes. Charging per brand would do the opposite.
The workspace kind decides what can be bought
The kind is not a presentational label. It decides which modules a plan can grant at all, and the list is not the same for the two.
Documents addressed to a third party, quotes, contracts, briefs and invoices, belong to the agency plans that include them, as do the CRM and the customisation of the portal and the documents; the client portal and the monthly PDF report are in every agency workspace. That is not a commercial squeeze: a company running its own marketing has nobody to invoice from here, and a screen for doing it would be empty on day one. Approvals, tasks and chat belong to agency workspaces and to the top creator plan, because they need a second hand. Analytics, the calendar, the inbox, bio and ads belong to everybody.
The kind is chosen when the workspace is created and can be changed afterwards. What changes with it is the vocabulary and what a plan may grant, not what has been published and not the history.
Why these three words are so stubborn
Because they were renamed on purpose and the rename went all the way down to the database. What was called the agency for a while is the workspace now, precisely because creators and companies running their own marketing are not agencies and calling them one forced a silent translation on every screen. The same pass turned the solo creator into a kind of its own with vocabulary of its own.
The result is that these three words mean the same thing in the product, in support, in the documentation and on this site, and they are worth using with equal stubbornness. When somebody says the tool will not let them into a client, half the time the problem is the wrong workspace and the other half it is a permission, which is a different question and is answered in roles and permissions.
