Assignments: who works on what
Putting people on a project, what an assignment carries, and how it interacts with time tracking.
An assignment puts one of your employees on a project, in a role, for a period, optionally at their own rate.
Adding someone
On the project, under Assigned people, pick an employee and assign them. Everyone already assigned is filtered out, and when there is nobody left the picker says so rather than offering an empty list.
What an assignment carries
- A role, what they do on this project.
- An hourly rate, which overrides the project's rate for that person's hours. This is the reason assignments carry money at all: a team billing one rate for everyone is a team leaving money on the table or losing it.
- Start and end dates, where the person is on the project for part of its life.
Why it matters for time tracking
Assignments are what makes a shared timesheet meaningful. Without them a project is a bucket anyone can log against; with them you can see who was supposed to be on it, at what rate.
They also feed the restricted time tracker role: an external contractor sees only the organizations and projects granted to them, and an assignment is usually the reason a project is granted.
Removing someone
Removing an assignment does not touch the hours they already logged. Those stay on the project, still attributed to them, still invoiceable. An assignment describes the arrangement going forward, not the history.