The task board, the team chat, the written procedures and the workspace drive are now open. They sit next to the content calendar and the brands, so a task, the conversation that started it and the video you need to finish it are all in one place instead of in three tools that have to be kept invited to the same people.
What opens, and where
One name covers four pieces, and they do not reach every kind of workspace alike. That is worth getting out of the way first, because the name groups them and the plans do not.
| Piece | What it settles | Which workspaces |
|---|---|---|
| Task board | Who does what, with dependencies and a timeline | Agency and the top creator plan |
| Team chat | Channels, a room per client and direct messages | Agency and the top creator plan |
| Written procedures | How something is done here, with an owner and a review date | Agency |
| Workspace drive | Folders with inherited permissions and a bin | Both kinds |
The split is not arbitrary. A board and a chat assume there is more than one person, which is why on the creator side they come with the plan built for a team. Since late September 2026 companies use the Creator plans, and the team, chat, tasks and approval come with that top creator plan. 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 drive, on the other hand, is there for everybody and no plan takes it away.
The board looks like your work
You write the columns. That sounds like a small thing and it decides whether the tool is still standing three weeks later: a board with borrowed statuses forces everyone to translate every move in their head, and what people do about that is stop moving cards.
On top of the columns there is the expected and two things that are less so. The expected is labels, priority, due dates, assignees, comments on the task itself and subtasks when a piece of work splits. The rest is tasks that repeat on their own, which is how the report somebody has to prepare every month gets handled without anybody having to remember, and dependencies between tasks, which stop the calendar 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, and the second question 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 really hold is a separate conversation, and it is in capacity per account manager.
Where each kind of conversation belongs
The chat has three shapes and each one settles something different. Channels by topic, for what concerns several people. A room per client, where everything about that account lives. And direct messages, for what needs no audience.
The client room is the one that changes the working day most, because it is the one that removes the question of where that thing was. When the conversation about a brand lives next to its calendar, its files and its tasks, nobody has to rebuild the context on the way in: it is right there.
Messages are plain text, with attachments and reactions and no decoration. A file can be attached straight from the workspace drive rather than uploaded again, which is the detail that prevents the third copy of the same video. And mentioning somebody shows you exactly who the message will notify before you send it, because waking a whole channel by accident is the fastest way to get it muted.
Who can write where is not decided by the chat: it is decided by the permissions each person holds, the same model that governs the rest of the workspace. A client room is not a secret room, it is a room seen by whoever has access to that client, and that is configured once and holds for the calendar, the files and the conversation at the same time.
Procedures that expire on purpose
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 you can see what it used to say and who changed it.
The next review date is the piece usually missing everywhere else. A procedure with no expiry turns into folklore: still there, untouched for two years, describing a social network that no longer works that way. With a date on it, the ones needing review turn up 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 start seen from the client's side has its own list in the client onboarding checklist.
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 just for you, and from there down everything beneath it inherits that, so visibility is not a decision taken file by file. There is a folder shared with you when somebody grants you access, a bin that keeps deleted items for 30 days, and a ceiling of 25 GB per file, which is enough for a whole video without splitting it. Two folders appear on their own: the publications one, with the files that went out in each piece, and the Google Drive one, where what you bring over from your own account with the picker lands.
And here is the decision worth understanding before comparing this to another tool: there is no public link. A folder cannot be sent to somebody without an account, not even with an expiry. Whoever needs to open a file signs in, and a client does that from their portal, where folders are shared both ways: they upload what is needed to produce and take away what is finished. A loose link is convenient on day one and is exactly the thing still working two years later, when that person no longer works there.
One thing worth knowing before you move your files in: a workspace left without a subscription goes into lock, turns read only and releases its connected accounts, and fourteen days later the drive and the media library are purged, with one warning three days before and another the day before. The data, the history, the invoices, the briefs, the tasks, the chat and the reports stay. The files do not.
What you gain by keeping it beside the calendar
The argument is not the price of the separate subscriptions, which is the one usually made and the weakest. 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 remove their access in three places the day they leave, which is the step almost always 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 you to repeat the context every time somebody new joins. A file that lives outside forces you to maintain 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 built underneath is in tasks, chat and Drive, and the screens, one at a time, are on the module page.
