Lesson 2 of 4 · 4 min
Project scope
A contractor sees one client's work and nothing else.
Roles say what someone can do. Scope says where they can do it. Agencies need both, because a freelancer on one account should not see the others.
Steps
- Decide which projects the person needs.
- Give access to those projects rather than the whole organisation.
- Confirm by checking what they can see.
- Remove project access when the engagement ends, before removing the account.
Why scope beats separate organisations
Separate organisations per client means separate billing, separate settings and duplicated setup. Project scope gets the isolation without the overhead.
What to watch for
Access granted for one urgent thing tends to stay. Put an end date in your own calendar when you grant temporary access, because nothing else will remind you.