Team Assignments
The One Projects has a two-level team model: organization-level team members who are available for any project, and project-level assignments that define each person's role and permissions on a specific project.
Organization Team Members
The Team page in the left sidebar shows everyone in your Projects organization. These are the people who can be assigned to projects and tasks.
Adding a Team Member
- Go to Team in the left sidebar
- Click Invite Member
- Enter their email address
- Select their organization-level role (this is their default access level)
- Click Send Invite
The invited person receives an email invitation. They accept via the invite link and set up their account.
Organization Roles
| Role | Default Permissions |
|---|---|
| Owner | Full access to all projects, settings, team management, and billing |
| Admin | Full access to all projects and settings; cannot change billing |
| Manager | Can create and manage projects; can approve time entries |
| Member | Can be assigned to projects; can create tasks and log time |
| Viewer | Read-only access to all projects they are a member of |
Project-Level Assignments
Each project has its own member list. A team member must be added to a project to access it (unless they are Owner or Admin, who have implicit access to all projects).
Adding Someone to a Project
During project creation: Use the Members section in the create wizard.
After creation:
- Open the project
- Go to the Team tab
- Click Add Member
- Search for the team member by name
- Select their project role
- Save
Project Roles
Project roles are the same as org roles but scoped to that project:
| Role | Permissions on This Project |
|---|---|
| Owner | Full control including archiving the project |
| Admin | Create, edit, and delete all content within the project |
| Manager | Manage tasks, milestones, documents; approve time entries |
| Member | Create and update tasks; log time; post comments |
| Viewer | Read-only: view tasks, milestones, time, documents |
A user's project role cannot exceed their org role. A user who is Member at the org level cannot be given Admin on a specific project.
Removing a Member from a Project
- Open the project → Team tab
- Find the team member
- Click the three-dot menu → Remove from Project
Removing a member does not delete their tasks or time entries. Tasks remain assigned to them; they simply lose access to the project. Reassign tasks after removing a member if needed.
Changing a Member's Role
- Open the project → Team tab
- Click the member's current role badge
- Select the new role from the dropdown
Workload View
The Team page at the org level shows each team member's current project assignments across all projects. This gives project managers a way to see who is overallocated before making new assignments.
For each team member you can see:
- Which projects they are assigned to
- Their role on each project
- Number of open tasks assigned to them across all projects
Capacity Planning
When assigning work, consider:
- Go to Team in the sidebar
- Click a team member's name
- View their current task count and active projects
Members with more than 20–30 open tasks across projects may be overloaded. Reassign or reprioritize before adding more.
Tips
- Assign a PM (Manager role) to every project — Projects without a clear manager tend to drift
- Use Viewer role for stakeholders who need visibility but not edit access — This prevents accidental changes by people who only need to monitor progress
- Remove members when their phase of work is done — This keeps the active member list clean and reduces notification noise
- Don't over-assign — The Team workload view only shows task counts, not hours. A member with 5 tasks that each take 2 days is more loaded than one with 10 quick tasks.