---
title: "Jobs"
slug: "jobs"
abstract: "Introduction to jobs."
---
# Jobs

A job can be associated with one or more [state flows](https://doc.sitecore.com/ch/en/users/content-hub/assign-state-flows-to-a-job.html "Assign state flows to a job"), each representing a recurring process consisting of states, transitions, and actions. Jobs provide a useful space for users to collaborate and include [quick actions](https://doc.sitecore.com/ch/en/users/content-hub/quick-actions-example.html "Quick actions example") for easy access to common tasks. With a state flow, at each state of the process, content is automatically reassigned and the job status is automatically updated. It is also possible to associate different quick actions with each state in the state flow.

You can associate a single job with multiple workflows. Conversely, the task workflow for a project is custom and cannot be reused. Also, unlike projects, there are no planning and management features for jobs.

> [!tip]
> Use a job if there are no complex dependencies or strict time management requirements. You can [compare projects and jobs](https://doc.sitecore.com/ch/en/users/content-hub/comparing-projects-and-jobs.html "Comparing projects and jobs") to better understand when to use each one.

To make it easier to [create jobs](https://doc.sitecore.com/ch/en/users/content-hub/create-a-job.html "Create a job"), you can [make any job a template](https://doc.sitecore.com/ch/en/users/content-hub/edit-job-details.html "Edit job details"), then use that template to create other jobs with identical or similar settings. In the following example, the *Artwork Localization Job* is associated with the localization workflow and uses one quick action - *Create content*. It is also tagged as a template.

![Job example](https://doc.sitecore.com/api/markdown-image/ch/en/users/content-hub/images/job_example.png)

After you create a job, assigned users can collaborate at each state of the workflow.

> [!note]
> If you have custom workflows, filtering by **Assigned to me** on the **Project** > **Jobs** page might not work as expected. This is because the filter checks for jobs that are either **Not started** or **In progress**.