Assigning work to your team

When you assign a project or task to a teammate, you are doing two things at once: scheduling the work and putting it in front of the right person. By default, members see the projects and tasks assigned to them, not the whole company's list.

That default keeps a field tech's view focused. They sign in, land on Projects, and see their own jobs and their own task list. Admins work with the full list across the organization.

Projects take a whole crew. The Assign to field in the Create Project dialog accepts multiple teammates, so everyone on the job shares it.

Tasks take one person. Set the assignee with Assign To when you create the task, or change it later by opening the task with the pencil icon on its row. One name per task keeps it clear who owns each visit.

Assignment and permissions work together. Assignment puts a specific job in front of a specific person. Permissions set the boundaries of what a member can reach at all. By default, members can view and update their assigned projects and tasks, and nothing else.

Admins can widen either side. A member can be granted access to all projects and tasks, not just assigned ones, or given access to other areas like the client list. The details live in Member permissions.

If someone says a job is missing from their view, check two things in order. First, is the project or task actually assigned to them. Second, do they have access to projects and tasks at all. Assignment puts work in view; permissions decide what is reachable.