Assigning Projects and Tasks to Team Members in Atarim

Assignment in Atarim answers two different questions, and it helps to keep them apart. Who can reach this work? is about access. Who is doing this? is about ownership.

Projects handle the first question. Tasks handle the second.

Three Levels of Assignment

You can assign at three levels, and choosing the right one saves a great deal of repeated work later.

Assigning a Project to Team Members

Project assignment decides who can see and work on a project at all. It is the access layer, not the ownership layer.

Go to Projects and find the project.

Open its Project Actions menu.

Select Assign Team Members. The share panel opens on its Team Members tab.

Add the people who should work on this project, typing a name or email to add each one.

Confirm. They now see the project on their own Projects screen and can be assigned its tasks, and their avatars appear on the project card.

Assigning a Task

Task assignment is where accountability lives. Each task has one responsible person — not a list — so there is never a question of who is meant to be doing it.

Open the task from Inbox, Boards, or Collaborate.

Find the Assign Team Member control. It prompts you to select a team member to assign.

Search for the person and select them. The search field narrows the list, which matters once your workspace has more than a handful of people.

To remove them, use Unassign. The task returns to having no responsible person.

Assigning in Bulk

Handing out work one task at a time gets slow after a client review drops forty items on you. There are three ways to work faster, and it is worth knowing which one applies to what.

Bulk Access: Assign a Folder

The most effective bulk action in Atarim is folder assignment, because it covers projects you have not created yet.

Open the folder and go to Folder Settings.

Under Assign Team Members, type a name and press Enter. Add as many people as you need, one after another, without leaving the field.

Save. Everyone added now has access to every project in the folder — and to any project filed into it later.

Bulk Notify: From Boards

You cannot assign a batch of tasks in one action, but you can add people to be notified on a batch — which is the right move when a group needs visibility of a whole round of feedback.

Open Boards and hover a task card to reveal its checkbox.

Select the tasks you want, or use Select all visible tasks to take everything on screen after filters.

Use the notify control on the bulk toolbar and choose the people. They are added to every selected task at once.

Select Deselect all tasks when you are finished.

Bulk Ownership: Use a Workflow

Because ownership is set one task at a time, the way to handle it at volume is to stop doing it by hand.

Create a workflow triggered on Task added.

Add a Change task assignee step naming the person who owns that account.

Attach it to that client’s projects and switch it on. Every task raised on those projects is assigned as it arrives, so a review round lands already distributed.

Assigning Is Not Notifying

This is the distinction people most often get wrong, and getting it right is what keeps a task list meaningful.

Assigning Automatically

If assignment follows a predictable rule, a workflow can do it rather than a person remembering to.

Go to Workflows and create one.

Choose a trigger — Task added or Task comment added are the usual ones.

Add a Change task assignee step and pick the person. Every task matching the trigger is assigned automatically, with no credit cost for the step itself.

Attach the workflow to the relevant projects and switch it on.

Who Can Be Assigned

Assignment is for your own team. External people participate differently.

Benefits of Assigning Properly

Example Use Cases

Known Limitations

A task has one responsible person. Use notifications for everyone else who needs to know.

Only people assigned to the project appear in the task assignee list.

Collaborators and clients cannot be assigned tasks.

Project assignment does not assign existing tasks — it grants access, and tasks are still assigned individually.

Assignment is per workspace, so someone must be in the workspace before they can be assigned anything in it.

There is no bulk assign. Status, priority, tags, notifications, pinning, internal, and delete can be applied to a selection; the responsible person cannot.

FAQs

Common issues

• Someone is missing from the assignee list — they are not assigned to the project. Add them to it, or to the folder it sits in.
• “Failed to update responsible team member” — try again. If it persists, check they still have access to that project.
• “Failed to unassign responsible team member” — reload and try again. The task keeps its current assignee until it succeeds.
• A client cannot be assigned a task — expected. Collaborators and clients give feedback rather than being assigned work.
• Someone cannot see a project you assigned them to — check they are in the right workspace, and that the assignment saved.
• You cannot find a bulk assign control — there is not one. Use a workflow for predictable routing, or assign individually.
• You want several people on one task — assign one and notify the rest. Only one person can be responsible.
• Assign Team Members is missing from the menu — your role does not carry the permission. An administrator can grant it.

Conclusion

Keep the two questions separate and assignment stays simple. Access is granted at folder level and inherited by everything inside; ownership is set task by task, one person at a time. Everyone else who needs to know gets notified rather than assigned — which is what keeps a name against a task meaning something.

Roles decide what someone can do once they have access. Explore User Roles And Permissions