---
title: "Job Blueprints"
description: "Save a job's configuration as a reusable blueprint and start new jobs from it."
url: "https://www.contentstack.com/docs/lytics/job-blueprints"
product: "Contentstack"
doc_type: "guide"
audience:
  - developers
  - admins
version: "current"
last_updated: "2026-11-05"
---

# Job Blueprints

Save a job's configuration as a reusable blueprint and start new jobs from it.

## What is a Job Blueprint?

A **Job Blueprint** is a saved snapshot of a job's configuration (its settings, authorization, quiet window, and monitoring) that you can reuse to create new jobs for the same integration. Instead of filling out the job wizard from scratch each time, you start from a blueprint and the fields come pre-filled, ready to review and adjust.

Blueprints are scoped to your account and tied to a specific integration (the provider and job type they were saved from). A blueprint is a starting point for new jobs, not a live link to a running job. Editing a blueprint does not change jobs already created from it.

## Saving a job as a blueprint

Open any configured job and choose **Save as job blueprint** from the job's actions (**⋯**) menu.

![The job detail actions menu with "Save as job blueprint" highlighted](https://images.contentstack.io/v3/assets/blt2d43f51baca745a8/amc13ff7e7840d755d/6ae6f3128361c43f770d99b9/feeeb45e5689dfbad82918d3c0f4c20435ffcdc8a19cf25d6e54e62d44f9bc2d-01-save-menu.png)

This opens the blueprint wizard pre-filled from that job. Give the blueprint a name, review or adjust the authorization and configuration (including any field mappings), and save it. The job you saved from is left unchanged.

![The blueprint wizard's configuration step, pre-filled from the job — including any field mappings](https://images.contentstack.io/v3/assets/blt2d43f51baca745a8/am754b10264cb47820/dbc1d8c31f42869dcd16d1d4/02-save-wizard.png)

To change a blueprint you already have, edit it from the **Job Blueprints** list instead of saving a new one — see [Managing blueprints](#managing-blueprints).

## Creating a blueprint from scratch

You don't need an existing job. In the **Job Blueprints** section of an integration's **Manage Integration** page, click **Create blueprint** to open the same wizard with empty fields. Because a blueprint is a template, its configuration isn't enforced as you build it — you can leave fields (such as the audience) empty and fill them in when the blueprint is later used.

## Managing blueprints

Each integration's blueprints live in the **Job Blueprints** section of its **Manage Integration** page, above the Jobs list, with a **Create blueprint** button. The section lists every blueprint saved for that integration, with its **Created by** and **Last modified** details. Each row has a **Use** button, with **Edit** and **Delete** in its **⋯** menu:

*   **Use** — start a new job pre-filled from the blueprint (see below).
*   **Edit** — open the blueprint in the wizard to change its name, authorization, quiet window, and configuration. Saving updates the same blueprint; a new one isn't created.
*   **Delete** — remove the blueprint. Jobs already created from it are unaffected.

![The Job Blueprints section on an integration's Manage Integration page, with the Create blueprint button above the Jobs list](https://images.contentstack.io/v3/assets/blt2d43f51baca745a8/am376623ff709506b7/b37fcc5a223d24ee0b663f9b/03-manage-section.png)

## Starting a new job from a blueprint

Click **Use** on a blueprint to enter the [job-creation wizard](/docs/lytics/creating-a-job) with its configuration applied:

*   The wizard opens at the **Expiration & Auth** step, where a **Start from a job blueprint** card shows the selected blueprint. You can switch to a different blueprint for the same integration from here.
*   The blueprint's stored [authorization](/docs/lytics/keys-authorizations) is applied automatically if it is still valid for the integration, and shown as selected. If it is no longer available, it is left unset so you can pick a current one. Some integrations use a shared, built-in authorization that isn't stored in the blueprint — for those, select it on this step.
*   On the configuration step, a banner notes that the fields were pre-filled from the blueprint and prompts you to review them before creating, since options can change over time.
*   If the blueprint captured [monitoring](/docs/lytics/monitoring-a-job), it is applied to the new job after the job is created.

![The Expiration & Auth step with the "Start from a job blueprint" card](https://images.contentstack.io/v3/assets/blt2d43f51baca745a8/amc22804f7f0f8ff81/40e86a5eda6b5c9ad1454dfb/c2cfe1b29393f1831b66526bce6471a0716de721403a04ecb71cf55ad22a3a5f-04-seed-jobdetails.png)

![The configuration step with a banner noting the fields were pre-filled from a blueprint](https://images.contentstack.io/v3/assets/blt2d43f51baca745a8/am813217622cdd77d6/a3a8380f0842bdc5b35521c2/d2fa94d98bc8b9d0e83910532ec96924cee5d12a6be834b823bf71abf7b0a8b2-05-review-banner.png)

Review the pre-filled values, make any changes, and create the job as usual.

## Permissions

Blueprints follow your existing job permissions: creating, using, editing, and deleting blueprints require the same access as creating, editing, and deleting jobs.