Assign a person to a role — and all 100–200 of their tasks in the project are assigned
A new project has hundreds of tasks, and the owner has to be picked in each. When someone in a role is replaced, tasks are reassigned one by one — and some still stay with the old person.
1 record
instead of picking the owner in 100–200 tasks
How it runs at the client: an education company, under NDA
≈4 h
of picking owners by hand on every project
Estimate: 10 roles × ~150 tasks × ~10 seconds to pick a person
10 seconds
to assign five people to 100 tasks — instead of 10 minutes of picking
Demonstrated on the Team Pro template — in the video below
Before
Hundreds of clicks per project
- Person
Filter the project’s tasks by area
- Person100–200 times
Pick the owner in every task
- Person
Repeat for every role
- Person
Someone replaced — reassign it all again
Who owns what in a project is only visible scattered across tasks — and somewhere the wrong person is always set.
After
One record per role
- Person1 record
In the assignments database pick project, role and person
- System
A Notion automation finds every task in the project with that role
- System
The person is assigned to all of them at once
- System
The same record opens the pages they need
How it works
- 1
“What” separate from “who”
In the template every task has a role: coordinator, marketing, finance. There is no person there — the template is the same for every project.
- 2
The assignments database
A separate table where one record is a project, a role and a person. This is the one place where you decide who owns what in a project, and the manager sees it as one list.
- 3
Notion assigns on its own
As soon as a record appears, a built-in Notion automation finds every task with that role in the project and assigns the person. A hundred tasks — one record.
- 4
Further down the chain
The same assignments database drives access and the schedule: every night n8n reconciles them with the assignments, so a removed role really removes access.
- 5
Made a mistake — remove it
Remove a person from a role and they disappear from all its tasks on their own — no need to go through them. A role can have two people — the tasks get both. And a single task’s owner can still be changed by hand.
- 6
When there are only a few roles
A separate database is optional. In my Team Pro template the roles — project manager, designer, developer, copywriter, SMM — are fields on the project card. Put a person in a role field and they are assigned to every task of that role in the project. Under the hood each role has two Notion automations: one fires when the field is filled, the other when it is cleared.
What it is made of
Assignments database
Who plays which role in which project — one table for the whole company.
NotionTasks with roles and a built-in automation that assigns people.
n8nThe invisible helper that grants access from the same assignments and reconciles it nightly.
Live walkthrough
Shown on my Team Pro template (in Russian)
What it looks like
Mock-up with demo 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
A good fit if
- Projects repeat, while the people in roles change from project to project.
- A project has hundreds of tasks and several areas.
- The manager needs to see at a glance who owns what.
Common 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.
What this opens up
The system knows who owns what — the same database can grant access.