> For the complete documentation index, see [llms.txt](https://knowledgebase.autorabit.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://knowledgebase.autorabit.com/product-guides/integral-zone/iz-suite/administration/global-settings/job-types.md).

# Job Types

A job type is one kind of work an agent runs, for example a platform sync, an asset assessment, a health check or an AI evidence investigation. The **Job types** tab lists every job type with the scheduler and executor release behind it, and shows which agents are equipped to run it.

Open it from **Administration** → **Global Settings** → **Job types** in the sidebar.

{% hint style="info" %}
In multi-tenant instances, this is managed by your platform administrator.
{% endhint %}

<figure><img src="https://content.gitbook.com/content/9vAxMuDrkUkB4OXlH9CL/blobs/CfFlD5niTzkUci8TYJhG/.gitbook/assets/gs-job-types-list.png" alt="Job types tab with the Job types, Enabled and Disabled tiles and the runtime catalog"><figcaption><p>Job types</p></figcaption></figure>

{% hint style="warning" %}
You need a role that can view job types to open this tab, and a role that can edit job types to change a runtime.
{% endhint %}

## How Job Types Fit Together

* **Agents**: each agent accepts only its **Eligible job types**, chosen when you register it. See [Agents](https://knowledgebase.autorabit.com/product-guides/integral-zone/iz-suite/administration/global-settings/agents.md).
* **Schedules**: a schedule says when to run a job type and for which organizations or environments. When it is due, an agent that can run that job type picks it up. See [All Schedules](https://knowledgebase.autorabit.com/product-guides/integral-zone/iz-suite/operations/schedules/all-schedules.md).
* **Runtime**: each job type has a scheduler, which creates the work, and an executor, which performs it. This tab holds their versions, artifact locations and configuration.

[How Assessments Run](https://knowledgebase.autorabit.com/product-guides/integral-zone/iz-suite/supported-platforms/how-assessments-run.md) describes the job types each platform uses and what each one does.

## Counts and Search

| Tile          | Description                                                        |
| ------------- | ------------------------------------------------------------------ |
| **Job types** | Job types matching the current search. Click to list all of them.  |
| **Enabled**   | Job types available in the job catalog. Click to list only these.  |
| **Disabled**  | Job types kept for configuration review. Click to list only these. |

Use **Search job types or modules** to find a job type by name or module. **Reset filters** clears the search and the tile selection, and **Refresh** reloads the list. **Export this page** downloads the job types on the current page as CSV.

## Runtime Catalog

| Column        | Description                                                                   |
| ------------- | ----------------------------------------------------------------------------- |
| **Job type**  | The job type's name, with its module underneath. Click the name to review it. |
| **Status**    | **Active** or **Disabled**.                                                   |
| **Scheduler** | The configured scheduler version, or **Not configured**.                      |
| **Executor**  | The configured executor version, or **Not configured**.                       |
| **Review**    | **Review runtime** (eye icon) opens the job type's details.                   |

The versions describe the configured release. They do not prove what every connected agent is running at the moment.

## Review a Job Type

Click a job type to open **Job runtime evidence**:

| Item                            | Description                                                                                                                                                               |
| ------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Facts                           | **Job type**, **Identity**, **Module**, **Status**, **Scheduler version**, **Executor version**, **Last updated** and **Origin** (**Built in** or **Custom**).            |
| **Edit runtime**                | Opens the runtime editor. Shown for enabled job types when your role can edit job types.                                                                                  |
| **Execution history**           | Opens [Execution History](https://knowledgebase.autorabit.com/product-guides/integral-zone/iz-suite/operations/schedules/execution-history.md) filtered to this job type. |
| **Runtime artifacts**           | **Scheduler binary** and **Executor binary**: where each artifact is taken from, or **Not configured**.                                                                   |
| **Recorded configuration**      | The job type's configuration as stored. **Download configuration** saves it as a JSON file.                                                                               |
| **Agents with this capability** | The agents that have this job type enabled, with their recorded state. Click an agent to open it. Check each agent's heartbeat and workers before you count on it.        |

## Edit a Job Runtime

There is no form to create a job type: job types are supplied with IZ Suite. You can change the runtime of an existing one.

1. Open the job type and click **Edit runtime**.
2. Change the fields in **Edit job runtime** (see below).
3. Click **Save runtime and restart agents**, or close the dialog to discard your changes.

| Field                         | Description                                                                                            |
| ----------------------------- | ------------------------------------------------------------------------------------------------------ |
| **Job type name**             | The name shown in lists and schedules. Up to 50 characters. **Required.**                              |
| **Scheduler version**         | The release of the scheduler component.                                                                |
| **Scheduler binary location** | The URL or path of the scheduler artifact your deployment expects.                                     |
| **Executor version**          | The release of the executor component.                                                                 |
| **Executor binary location**  | The URL or path of the executor artifact your deployment expects.                                      |
| **Configuration JSON**        | The job type's configuration. It must be valid JSON, or empty. **Format JSON** tidies the indentation. |

The job type's identity and module do not change, so existing schedules and results stay attached to it.

{% hint style="warning" %}
Saving asks the agents to restart, which can interrupt the work they are running. Check the versions, artifact locations and configuration before you save, then follow the agents' status on [Agents](https://knowledgebase.autorabit.com/product-guides/integral-zone/iz-suite/administration/global-settings/agents.md).
{% endhint %}

## Next Steps

* [Agents](https://knowledgebase.autorabit.com/product-guides/integral-zone/iz-suite/administration/global-settings/agents.md): choose the job types each agent can run.
* [All Schedules](https://knowledgebase.autorabit.com/product-guides/integral-zone/iz-suite/operations/schedules/all-schedules.md): run a job type on a schedule.
* [How Assessments Run](https://knowledgebase.autorabit.com/product-guides/integral-zone/iz-suite/supported-platforms/how-assessments-run.md): the job types each platform uses.
* [Global Settings](https://knowledgebase.autorabit.com/product-guides/integral-zone/iz-suite/administration/global-settings.md): the other configuration screens.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://knowledgebase.autorabit.com/product-guides/integral-zone/iz-suite/administration/global-settings/job-types.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
