Site permissions vs. project permissions
Site permissions control access across your whole account. Project permissions control access within a specific project. Both layers are needed: one sets the ceiling, the other sets the detail.
Run projects consistently and reliably from the start. With the right foundations in place, every project, from setup to delivery, begins with accurate data, the right people, and a repeatable structure your team can trust.
Read time
10 minutes
Goal
Set up your site
Primary Tool
Teamwork.com
The quality of every project decision you make, from who works on what to how work is tracked and whether a project is profitable, depends entirely on the foundations you put in place at the start.
Site permissions control access across your whole account. Project permissions control access within a specific project. Both layers are needed: one sets the ceiling, the other sets the detail.
A team member contributes to assigned work. A Project Admin manages settings, financials, and structure. Anyone who needs to edit the project itself should be a Project Admin.
Assign roles to every team member before creating projects.
Add cost and billable rates upfront.
Keep permissions and project roles consistent across teams to avoid reporting issues later.
Only add people to a project who will actively contribute to it.
Keep teams and roles updated as your organization evolves.
Skipping billing setup. Every hour logged without it creates financial data you can't trust.
Adding too many people to a project. It creates noise and blurs accountability.
Leaving permissions unconfigured. The wrong people editing settings cause compounding problems.