Solution · project launch
Role assignments: one person per role — and all their tasks in the project are assigned
A project has hundreds of tasks, and the owner has to be picked in each one. The solution separates “what to do” from “who does it”: a template task names a role, and one record in the assignments database says who plays that role in this project. A built-in Notion automation immediately assigns that person to every task in the project with that role.
What it looks like
Mock-ups with demo data, no real data
🧩Assignments
| Project | Role | Person | Tasks |
|---|---|---|---|
| Product launch | Marketing | MMaria | 148 |
| Product launch | Coordinator | AAnna | 212 |
| Office opening | Coordinator | OOleg | 196 |
📁
Client website
In progress
- Project manager
- MMaria
- Designer
- IIlya
- Developer
- OOleg
- Copywriter
- AAnna
Tasks — owner set by role
- Homepage prototypeDesigner → Ilya
- Homepage copyCopywriter → Anna
- Build and launchDeveloper → Oleg
- Client sign-offManager → Maria
At a glance
- In production
- At a client
- Fits
- Teams with recurring projects where different people fill the same roles
- Needs
- Notion with database automations; n8n if roles also grant access
Estimate for your company
≈4 h
of picking owners by hand on every project
Assumption: 10 roles × ~150 tasks per role × ~10 seconds to pick a person in a task (our assumption)
This is a calculation, not a promise: plug in your own volumes and the figure changes.
Before
- In every new project the owner is picked in every task — hundreds of clicks.
- When someone in a role is replaced, their tasks are reassigned one by one, and some always stay with the old person.
- It is unclear who owns what in this project: you only see it scattered across tasks.
What was built
A role in the task template
Every template task knows in advance which role does it. No person is named in the template.
Covered separately →The assignments database
One record: project, role, person. It is the only place where you decide who owns what in a project.
A Notion automation
As soon as a record is added or changed, a built-in automation finds every task in the project with that role and assigns the person — 100–200 tasks at once. Remove the person and they are taken off every task of the role the same way.
Then — schedule and access
From the same database n8n sets owners in the schedule and grants access; every night it reconciles everything, so a removed role really removes access.
Covered separately →Stack
- Notion
- Notion automations
- n8n
Where it runs
Questions
How is this better than bulk editing in Notion?
You can bulk-select tasks by hand, but each time you have to filter the database by project and role without mistakes. Here it is one record — and the assignments database shows at once who owns what in every project.
What if I picked the wrong person, or a role needs two?
Remove the person from the role and they disappear from all its tasks. Set two people and the tasks get both.
Can I assign one task to someone outside the role?
Yes, a task can be reassigned by hand. But who owns what in a project is decided in the assignments database — that keeps the picture consistent.