Ivanti Automation Glossary




An Agent is a service running on a computer and can execute Ivanti Automation Tasks.

Administrative role

An administrative role determines the level of access that a Console user has to the various parts of the Console.

Building Block

A Building Block can be used to export or import objects in an environment's Library (Modules, Projects, Run Books and Resources), for backup purposes and to transport objects from one Ivanti Automation environment to another.


A condition determines, based on one or more expressions, whether a Task, Module or Run Book Job should be executed, skipped or failed.


The Console is the application from which Ivanti Automation is configured and used, from setting up the Ivanti Automation environment to the execution of Tasks.


The Datastore is a database that contains all the settings and Resources of your Ivanti Automation environment.


A Dispatcher is a service running on a computer, and communicates information from the Datastore to Agents. A Dispatcher can cache Resources in order to reduce network traffic.


An evaluator can only be used in query Tasks. Based on the query results, it determines the status of the query Task after it has been executed.


A function generates (partial) input for text-based properties of Tasks. This makes it possible to create information in various fields in Tasks automatically.

Global Settings

Global Settings determine the general behavior of your Ivanti Automation environment, and the default behavior of Dispatchers and Agents.

Instant Reports

An Instant Report is a detailed report of your Ivanti Automation environment and includes all settings of the documented item(s). It can also include additional information about the current Ivanti Automation version.


A Job is the execution of Tasks at a specific time on specific Agents.

  • For Modules and Projects, both the time and the Agents are set at the moment of scheduling.
  • For Run Books, the timing is set at the moment of scheduling. The Agents may already have been set for some or all of the Modules and Projects contained in the Run Book. In that case, Agents are not set at the moment of scheduling, or only for the items not yet given a target.

Management Portal

The Management Portal is the web-based application for scheduling Jobs in your Ivanti Automation environment.


A Module is a container for one or more Tasks. To execute the Tasks in a Module, the Module can be scheduled as a Job on a set of Agents at a specific time.


A parameter functions as a placeholder for values in various fields, such as text, file paths, credentials, etc. The actual values of these fields can be provided when the Task is used in a Job. This makes it possible to create generic Modules, Projects and Run Books that can be customized to each situation when required.


Projects are containers for Modules. By combining several Modules into one Project, those Modules can be scheduled on a set of Agents as one Job instead of separately as a series of Jobs.


A Resource can be any file that is needed to perform a certain Task, such as an MSI file, a setup file, a patch, a hotfix, etc.

Run Book

Run Books are containers for Jobs. Run Books can contain Modules and Projects plus (optionally) the Agents on which they should be executed. To execute the Tasks in the containers in the Run Book, the Run Book is scheduled as Job for a specific time.

By combining Modules and Projects and their Agents in a Run Book, a sequence of actions can be scheduled consecutively on different sets of Agents.


A Task is a specific action that can be performed by an Agent. Tasks are part of a Module.


A Team is a group of Agents. Teams can also contain other Teams.


A Trust allows a customer representative to enforce that only Resources and Modules that have been explicitly authorized can be used on that customer’s Agents. When Trusts are enabled, Modules and Resources can only be used by Agents if a full Trust exists.


A Variable acts as a placeholder for a customer-specific value, such as, for example, server names, passwords or credentials. Besides a global, default value, a Variable can also have an Agent-specific and a Team-specific value. A Variable is resolved at the moment of Job execution.