Every person in your workspace carries an employment classification of either employee or contractor. It is a label that records how each person is engaged, and nothing more. This article explains where to set it and, just as importantly, what it does not change.
The classification lives on each person's page in Team, in their Basic info, under Employment type. An administrator selects either Employee or Contractor.
Setting it is an admin-only action. Managers and members cannot change their own or anyone else's employment type. When you invite or import someone, they start with a classification you can adjust at any time from their page.
The classification is a label. Its job is to let you distinguish permanent staff from external help when you look at your team.
Where the label surfaces, a contractor is marked in the roster — for example, their row reads "· Contractor" after their name and role. This makes it easy to scan the team list and see at a glance who is internal and who is engaged as a contractor. You can also ask the assistant about it — "list the contractors", or "how many hours did the contractors in Engineering track last month?" — because it can filter people by classification.
No report in the app groups or filters by it yet, and the Team page has no filter for it.
This is the part that trips people up, so it is worth being explicit: employment type does not change permissions, access, or visibility in any way.
In short, permissions come from the role (member, manager, admin, or owner); the employee-versus-contractor label sits alongside the role purely as a record. Changing someone from employee to contractor, or back, is safe and has no effect on their day-to-day use of Time Trakkr.
If you bring your team across from Harvest, the classification comes with them. Harvest's own employee-versus-contractor setting is treated as the authoritative source, so imported people arrive with the right label, and re-running the import keeps it current — even for people who were imported before this field existed. That means you generally do not have to set the classification by hand for migrated team members. For the full migration process, see migrating from Harvest.
Set the classification once for each person. Because it never touches permissions, you can classify freely to match how you actually engage people, confident that the only thing changing is how they are labeled. To bring new people in and give them the right role, see inviting people.
Updated 2026-11-08. Still stuck? Contact support or return to the Help Center.