Skip to main content

Understanding Task Management in Orchestrate

Understand how tasks, personal planning, shared views and access settings work together.

Written by Lena Semmler

Task Management in Orchestrate consists of three main layers:

  1. The task itself
    The actual work item, including its assignees, status, priority, related objects and access settings.

  2. My Tasks
    Your personal task workspace, built around the principles of Getting Things Done (GTD), helping you organize the tasks assigned to you and decide when to work on them.

  3. Team Tasks
    Shared views and boards for organizing work across teams.

A task can appear in several places at the same time. It is always the same task. Changing it in one place changes the task everywhere.
​

My Tasks

My Tasks is your personal task workspace. It is based on the Getting Things Done (GTD) framework and helps you organize your own work by deciding what needs attention and when.
​

Your tasks are organized into five views:

  • Inbox: Tasks that have not been planned yet

  • Today: Tasks planned for today or earlier

  • Upcoming: Tasks planned for a future date

  • Anytime: Tasks without a planned date that are ready to work on

  • Logbook: Completed tasks

Tasks created directly in one of these views are placed there automatically. For example, a task created in Today is planned for today, while a task created in Inbox starts unplanned and private to you.
​

A simple workflow is to regularly clear your Inbox, plan tasks for Today, Upcoming or Anytime, and use Today as your daily working list. Completed tasks automatically move to the Logbook.
​

💡My Tasks is for personal planning. It determines when you want to work on a task. The same task can still appear in Team Tasks, on a related Content, Frame or Story, or in another view.
​

Team Tasks

Team Tasks gives teams shared ways of organizing and working with tasks. There are two types of Task Views:
​

A Standard Task View is a saved set of filters. You can create views based on properties such as:

  • Teams, Assignees, Priorit, Storyboards, Frames, Content, Tags etc.

All accessible tasks matching those filters appear automatically.
​

The Standard Task View itself can be assigned to selected teams. This controls who can open the view, but it does not change who can access the tasks shown inside it.

A restricted task can therefore match a Standard Task View while still only being visible to users who have access to that task.
​

💡Use a Standard Task View when you want a shared filtered overview of existing work.
​

A Restricted Board is a protected task workspace for selected teams.

Only those teams can access the board. Tasks created inside it automatically inherit the board access.
​

Individual tasks can still be shared with additional teams or people without giving them access to the entire board.
​

Tasks from a Restricted Board can also appear elsewhere, for example in My Tasks, other task lists or inside related Content, Frames or Stories. Their restricted access remains in place wherever they appear.
​

💡Use a Restricted Board when a group of tasks should be managed together in a protected team workspace.
​

Task Access

Every task has its own access settings. A task can be visible to Everyone in the company or restricted to selected teams and people.
​

The initial access depends on where the task is created. For example:

  • a task created in My Tasks can start private to you

  • a task created in Team Tasks receives access based on the relevant team context

  • a task created on Content, a Frame or a Story can inherit that object's access

  • a task created inside a Restricted Board inherits the board access

Access can be changed later if needed.
​

Assigning someone to a task and giving them access are separate actions. If an assignee cannot access the task, Facelift warns you so you can adjust the access settings.
​

💡Task Access determines who can see the task, regardless of where that task appears.
​

Tasks connected to Content, Frames or Stories

Tasks can be linked directly to other objects in Orchestrate, such as Content, Frames, Stories or Post Sets.
​

This connects the task to the work it belongs to without creating another copy of it.

For example, a task can simultaneously appear:

  • on its related Content

  • in a team's Standard Task View

  • in your personal Today view in My Tasks

  • in another task list where it matches

Task lists also show the object's path, for example: Storyboard › Story › Content. This makes it easier to understand where the task belongs and navigate back to the related work.

A task still has its own access settings. When it is linked to an object with different access, Facelift can offer to align the task's access with that object.
​

How everything fits together

Imagine a task assigned to you that belongs to a campaign:

  • In My Tasks, you plan it for Today

  • It appears in a Standard Task View for your team because it matches that view's filters

  • It also appears directly on the related Content

  • Its Task Access determines which users can see it in all of those places

If the task was created inside a Restricted Board, the board's teams remain part of its required access wherever the task appears. It is still one task throughout Orchestrate.

The easiest way to think about the different layers is:

  • My Tasks determines when you want to work on it

  • Task Views determine how work is organized

  • Related objects provide the work context

  • Task Access determines who can see it

Which option should I use?

  • Want to organize your own work and schedule? Use My Tasks

  • Want a shared filtered overview of tasks? Use a Standard Task View

  • Want a protected workspace for a team and its tasks? Use a Restricted Board

  • Want to control who can see a specific task? Use Task Access

Did this answer your question?