# Permissions and Roles
Team Projects has two roles: owner and member. Every project has exactly one owner with full control. Members can also receive focused permissions for the parts of the project they help manage.
![[team-members-permissions-expanded.png]]
> [!quote] The idea
> Everyone on the team can work from the board. The owner keeps full control and can delegate specific responsibilities without turning another member into an owner.
## Owner
The project owner has full control over the project.
- Project settings and configuration
- Managing membership: who is on the project and what role they have
- Everything a member can do
## Member
A member has the access needed to do their work on the board.
- Creating and editing tasks
- Managing tasks: assignees, statuses, and the other day-to-day work of a task
- Creating and editing Project Docs
- Any additional permissions the owner grants, such as managing project settings or coordinating selected team views
## Timesheet reporting access
An owner or a member with **Manage project settings** can choose which active teammates another member may include in [[Timesheets and Time Reporting|the detailed Timesheet]]. The member's own time is included automatically.
Open **Settings > Members**, expand a member, and use **Timesheet visibility**. A settings manager cannot change their own reporting scope.
This visibility controls the detailed Timesheet, its entry details, and the corresponding detailed exports. It is separate from Full project reporting.
## Full project reporting
Full project reporting opens project-wide surfaces in [[Reports and Insights]], including Overview, Time, Delivery, and the reporting portions of downloads.
- Owners have full project reporting
- An owner can grant it to an active member from **Settings > Members**
- Members without it see their own contribution where the report supports a contribution view; Delivery needs full reporting
A full report can show named people and their Team Project time. It does not include private Planning tasks, schedules, Deep Work scores, reflections, or personal insights. Detailed time entries still follow Timesheet visibility, even in a larger report download.
## Saved reports and report notes
A project member with full reporting can create a report in the project's **Custom reports** tab. The creator or project owner can edit it. Other members run it with their own access.
A cross-project report shared with a named member also runs with that recipient's own access. Sharing the report does not change project membership or reporting permissions. See [[My Reports]].
Team report notes are visible to members with full reporting on that project. Their author or the project owner can edit or remove them.
## Team Today: view-only access
An owner can grant a member **view-only access** to [[Team Today]]. They see the full board (columns, planned tasks, ordering) but can't drag, reorder, assign, or remove anything from it.
![[team-today-view-only-toggle.png]]
- **Set per member**: Turn it on for a specific member from **Settings → Members**
- **Read the board**: View-only members can see the full board; controls for changing it are unavailable
> [!tip] Give visibility without giving control
> Use view-only access when someone needs to see what the team is working on today, such as a stakeholder or a lead who isn't managing this board, without the ability to change it.
## Deactivating a member
Owners can deactivate a member instead of removing them from the project outright.
- **History preserved**: Past assignments and comments stay intact and attributable, greyed out to show the member is no longer active
- **Excluded going forward**: A deactivated member drops out of the assignee picker and @mention suggestions, and their access to the project is revoked
- **Reversible**: Reactivate a member at any time from **Settings → Members**
> [!tip] Deactivate instead of remove
> Deactivating keeps a departing teammate's past contributions attributable instead of orphaning them. Use it when someone leaves the team or moves off a project, rather than removing their membership outright.
## Why two roles
Keeping the roles simple means less setup and less to think about when you invite someone new. The owner shapes the project. Members get everything they need to work without needing to ask someone else to change a setting on their behalf.
## Service Desk membership is separate
A [[Service Desk]] is a different kind of project with its own member list. Being a member of a Team Project gives you no access to a desk, and the reverse is also true. This means support work can be handled by a smaller group than the team it sits alongside. People who submit through a public [[Intake Forms|intake form]] are not members of anything and cannot see the desk.
---
**Next:** See how to [[Setting Up a Team Project|configure a project]] as the project owner.