Differences between Basic Projects and Jobs

Basic projects are used for a simple workflow, enabling an easy collaboration on content and simple task assignments. For more information on Basic Projects, please see Basic Projects.

Jobs are a single space in which teams and departments can collaborate yet still work independently with a focus on their responsibilities. The main building blocks to articulate workflows are state flows. For more information on Jobs, please see Jobs.

While it might appear the Jobs (BlockType) and Basic Projects can be used interchangeably, there are fundamental differences between the two.

This difference, at the most fundamental level, is that Basic Project has defined planning and management functionality:

Whereas a Job is associated with Quick actions:

Basic Projects

Basic Projects have the following management capabilities:

  • Full task management (duration, workload, etc.).

  • Budget and resourcing capabilities.

  • Task chaining.


Jobs are enabled for State flows, for more information on State flows please see State flows. A State flow supports business logic automation settings that can be optionally set on each state transition within a job. For each job state, the following factors can be automated:

  • Assignment: Assign the skilled resources to perform specific granular activities within a job.

  • Quick action: Select individual action buttons that are available for the dedicated collaborator in each State.

  • Status: Automatic transitioning of the job status after completion.

Jobs can utilize the following Quick Actions:

  • Quick actions

  • Like

  • Upload version

  • Annotate

  • Global review

  • Localization variant

  • Parallel review

  • Local review

  • Upload files

  • Download


To decide whether to use a job or a project, use the best practices.

Can we improve this article ? Provide feedback