A piece past its deadline
If you turn it on, each person gets one email a day with their overdue tasks, with the margin you set. It's off by default.
After “will my clients log in?”, the next question is “and my team?”. Here is, step by step, what each person on your team, employed or freelance, receives, sees and does. And a message ready to send them.
Journey reviewed in October 2026 against the version in production.
Nobody on your team signs up anywhere. You (or a manager) invite them with their role, and they get an email.
If you'd rather create their access yourself, you can add them with a temporary password they'll have to change the first time they log in.
When they log in they see their tasks. Not a board with everything in the agency: what depends on them, today.
Each person picks Spanish or English in their profile; the interface and the emails reach them in their language.
Every piece follows its client's workflow, step by step, and every step has an owner.
When a step comes to depend on them, the piece shows up in “My turn” and they get the “your turn” alert by email and in the bell.
They see the piece type, the client, the date, the previous versions, who else is collaborating and the task's conversation. If they have a question, they @mention whoever: that thread never reaches the client.
They upload the new version and mark their step as “Done”. The piece moves on by itself to the next owner (review, approval, publishing). Every delivery is a new version and the previous ones are still there.
Corrections arrive numbered by round, and internal ones are kept separate from the client's. They know what to change and which round they're on; no voice note to hunt for.
Nobody approves their own piece: the approval step is done by the owner or a manager, never by whoever produced it. A manager can also mark a step on someone else's behalf.
The piece becomes Completed (the manager can complete several at once). How long it spent in each status is on record. And if whoever delivered is freelance, their cost becomes payable.
The same thing they do today, but without asking in the group chat where everything is.
A sample piece with made-up data and the suggested “Content” workflow: production, review, approval and publishing. You play one person on the team or the other. Nothing is sent anywhere.
Autumn launch reel · Production · due tomorrow
Autumn launch reelInstagram · due tomorrow · v2
In progressYour turn: the piece is in production and depends on you. You upload v3 and mark your step as done; the piece moves on to review by itself.
Nothing yet: when you mark your first step, it shows up here with your name.
The client's approval is separate: it comes after this one, from the approvals queue. Try it: this is how your client approves
The portal alerts whoever it concerns. Nobody has to chase anybody.
If you turn it on, each person gets one email a day with their overdue tasks, with the margin you set. It's off by default.
They write it in the task's conversation and @mention whoever can answer it; that person gets the alert. No group chat.
Not the team's problem: the portal reminds the client and, when the reminders run out, alerts you and the account manager.
If you connect Google Calendar, the manager sees the team's availability and books the meeting with Meet from the portal; the invitation arrives by email.
Everything comes from your agency's sender, in their language. The wording of each email is changed from your agency settings.
When a step of a piece comes to depend on them. By email and in the bell.
If the client approves or requests changes on one of their pieces, they get the alert; the client's note is kept in the piece's history.
In the bell, straight away: a counter, a pop-up alert and the list of the latest ones.
The agency's weekly summary, by email, to the whole team.
One email a day, only to those with overdue tasks, only with their own.
An automatic greeting, if their date is in their profile.
There are four roles in the agency: owner, manager, editor and client. An editor produces; this is what stays off their screen.
So you don't promise it to your team.
It's the web, adapted to phones, in the browser. Alerts arrive by email and in the portal's bell.
There is no agency chat: conversations live on each task, in its thread, with @mentions.
They log in with email and password. There is no two-factor authentication either.
There is no API and no external automation tools. Google, yes: Calendar and Meet for meetings, and Drive to see your folders from the Library.
The brief goes in the task's description and the materials go in the client's Library. What it should contain is in the brief guide.
The portal is in Spanish and English; each person picks their own.
If your team needs any of these, tell us on the call: better to know before we set anything up. What to put in a brief so the piece comes out right first time
This is what affects your team. The full list of what the product doesn't do, with what there is instead, is in What it doesn't do (yet).
And the answer you can give them.
The ones on this page and on the others, together: every question, on one page
Hi everyone. From [date] we'll be running client pieces in our portal, at [clients.youragency.com]. You'll get an invitation by email: open the link, choose a password and you're in. There is nothing to install; it works in the browser, on your phone too.
Every morning, open your tasks with the “My turn” filter: only the steps that depend on you are there. When you deliver, upload the version and mark the step as done; the piece moves on by itself to whoever reviews it. If something comes back, the corrections are numbered. Questions go in the task's conversation, @mentioning whoever: the client doesn't see it.
If you work freelance: your rate is set per piece type and the cost is generated on its own when the piece is completed; no need to claim anything. Expenses you pay upfront are submitted from the portal and I approve them.
In the demo we show you the portal with sample data, from the owner's view, an editor's and the client's.
Request a demoEverything on this page is in production. What isn't, is listed under “What's not there yet”.
What your team will see · portaliaflow.com/en/what-your-team-sees