One name covers four pieces: a task board, the team chat, the written procedures and a file drive for the workspace. They sit next to the calendar and the brands, so a task, the conversation that started it and the video needed to finish it all live in the same place rather than in three separate tools.
Four pieces, and they do not reach everybody alike
Worth starting there, because the name groups them and the plans do not. The task board and the chat are in agency workspaces and on the top creator plan, which is where several people split the work. The file drive is in both workspace kinds and no plan takes it away. The written procedures belong to agency workspaces.
| Piece | Where it lives |
|---|---|
| Task board | Agency workspaces and the top creator plan |
| Team chat | Agency workspaces and the top creator plan |
| Workspace drive | Both workspace kinds |
| Written procedures | Agency workspaces |
The split is not arbitrary. A board and a chat assume there is more than one person, and a team is exactly what a creator on the smaller creator plans does not usually have; a company running its own marketing signs up as a creator workspace and gets both with the creator plan made for a team. Written procedures show up when somebody has to be told how a thing is done for a brand that is not their own, which is an agency's situation rather than that of a company running its own marketing.
The board looks like your work, not the other way round
You define the columns. That sentence sounds minor and it decides whether the tool is still in use three weeks later: a board with borrowed states makes people translate every move in their head, and what they do about that is stop moving cards.
On top of the columns there is the expected set plus a couple of things that are less so. Labels, priority, a due date and assignees, comments on the task itself, subtasks when a piece of work splits, and the option to mark a task as a milestone. A task can repeat on its own, which is how the report that has to be prepared every month stops depending on somebody remembering. And a task can depend on another, at which point the calendar stops lying: if the edit depends on the shoot, moving the shoot moves everything behind it.
There is also a timeline view for when the dates matter more than the states. A board answers "what is in progress" well and "are we going to make it" badly. Those are two different questions, and the second one is answered by looking at the same work on a time axis.
Everything that happens to a task is written down: who moved it between columns, who changed the due date and from what to what, who assigned it to whom. That is not surveillance, it is the answer to why this still has not gone out, a question that asks itself every week in a team of five people running twelve brands. How many brands one person can genuinely hold is a separate conversation, and the clients per person calculator puts numbers on it.
Where each kind of conversation belongs
The chat has three shapes and each one solves something different. Channels by topic, for whatever concerns several people. One room per client, where everything about that account lives. And direct messages between two people, for what needs no audience.
The per client room is the one that changes the working day most, because it removes the question of where that thing was. When the conversation about a brand sits beside its calendar, its files and its tasks, nobody has to rebuild the context: it is right there.
Messages are plain text, with attachments and reactions and no formatting theatre. A file can be attached straight from the workspace drive instead of being uploaded again, which is the detail that prevents the third copy of the same video. And when you mention somebody, the composer says exactly who the message will notify before it is sent, because notifying a whole channel by accident is the fastest way to get a channel muted.
Who can write where is not decided by the chat, it is decided by the permission each person holds, which is the same model that governs the rest of the workspace and is described in roles and permissions.
Written procedures, and why they expire
A procedure is a document with an owner, a category and a next review date. It is written here as text, or uploaded as a file when it already exists as a PDF and what you want is to have it where the work happens. It stays a draft until it is published, and every change leaves a version behind, so what it used to say and who changed it are both recoverable.
The next review date is the piece that tends to be missing everywhere else. A procedure with no expiry turns into folklore: it is still there, nobody has touched it in two years, and it describes a social network that no longer works that way. With a date on it, the ones needing review appear in their own list and stop being an invisible problem.
For an agency the value is not documentation for its own sake, it is that somebody new can make a brand's first post without sitting next to whoever runs the account. That same kickoff, seen from the client's side, is in the client onboarding guide.
Everything in this article happens in one place in GoFeed.
Try it freeThe drive, and why it has no public links
Files live in folders. Each root folder is created either for the whole workspace or for you alone, and everything below it inherits that, so visibility is not a decision you make file by file. There is a shared with me view for folders somebody gave you access to, a bin that keeps deleted items for 30 days before they really go, and a ceiling of 25 GB per file, which is enough for a full video without cutting it up.
That 30 day bin is worth more than it sounds. Deleting a folder by accident is a boring and fairly common accident, particularly when several people are moving material at the same time, and the difference between a bad afternoon and a lost shoot is that there is somewhere deleted things wait for a month before going for good.
Two folders appear on their own. The posts folder, holding the files that went out with each piece, and the Google Drive folder, where the files you bring across from your Google account with the picker land. That import is a way in and never a way out: it exists so the material you already had arrives here, not so you can publish outwards from it.
And here is the decision worth understanding before you compare this with another tool: there is no public link. A folder cannot be sent to somebody without an account. Whoever needs to open a file signs in, and a client does it from their portal, where folders are shared in both directions: they upload what production needs and they collect the finished work. A loose link is convenient on day one and is exactly the thing that still works two years later, when that person no longer works there.
What you gain by keeping it together
The argument is not the price of the subscriptions, which is the one usually made and the weakest one. The argument is context.
Every separate tool charges a small, constant toll that nobody writes down anywhere. You have to remember where each thing lives, you have to keep the same people invited in three places, and you have to withdraw that access in three places the day somebody leaves, which is the step that almost always gets forgotten in the third one.
A task that does not know which brand it belongs to forces you to put the brand name in the title. A conversation that does not know which client it is about forces somebody to repeat the context every time a new person joins. A file that lives elsewhere forces a naming convention nobody follows. All three work, and all three are paid for in attention, every day.
When the board, the chat and the files share a workspace with the calendar and the brands, most of that bookkeeping disappears by itself. How each piece is assembled, including what the board carries and what the drive does, is on the tasks, chat and Drive page.
