# Ivanti Neurons

### Overview

The Veza integration for the Ivanti Neurons HRIS system streamlines identity governance by automatically synchronizing employee data with Veza's Identity Security platform. This integration enables organizations to:

* Maintain current employee data across your identity security infrastructure
* Enrich Veza search results with up-to-date employee information
* Streamline access reviews with accurate organizational context
* Support automated lifecycle management workflows using Ivanti Neurons as a source of identity

This guide will walk you through creating the required API credentials in Ivanti, configuring the integration in Veza, and including custom employee attributes (optional).

### Configuring Ivanti

The Veza Ivanti Nurons connector requires an API key to connect and collect the employee information. Follow the steps in the Ivanti [documentation to create a Key Group and API key](https://help.ivanti.com/ht/help/en_US/ISM/2022/admin/Content/Configure/API/Web-Services-API.htm)

Create the API key for a user with administrative read permissions to view all employees.

#### Configuring the Ivanti Nurons Integration on Veza

Most customers will require a Veza Insight Point to be deployed in their environment to access their Ivanti Nurons instance. Follow the steps <> for more on deploying a Veza Insight Point.

1. On the Veza **Integrations** page, click **Add Integration** and locate the Ivanti Nurons HR tile.
2. Configure the integration with the following fields:
   1. **Set the Insight Point** - Select the Insight Point that will have access to the Ivanti Nurons instance
   2. **Name** - Name for the integration
   3. **URL** - URL for Ivanti Nurons instance
   4. **Additional Properties** - Additional employee properties to collect from the API response. See below.
3. Provisioning Source (optional): Check to enable Ivanti Neurons as a provisioning source for Life Cycle Management Workflows.

### Notes and Supported Entities

#### Ivanti Employee

When enabled as a provisioning source, Veza ingests Ivanti Neurons employees as `CustomHRISEmployee` entity types for use in [Lifecycle Management](/4yItIzMvkpAvMVFAamTf/features/lifecycle-management/integrations.md) policies.

The Veza connector gathers employee metadata from the `employees` business object. Business Objects can be viewed from the Ivanti Configuration console, under **Build > Business Objects**

The following Employee properties are collected by default and mapped to the Veza Employee object.

| Employee Property | API Field        | Notes                                  |
| ----------------- | ---------------- | -------------------------------------- |
| ID                | RecID            |                                        |
| Name              | DisplayName      |                                        |
| First Name        | FirstName        |                                        |
| Last Name         | LastName         |                                        |
| User Name         | NetworkUserName  |                                        |
| Employee Number   | LoginID          |                                        |
| Email             | PrimaryEmail     |                                        |
| Employment Status | Status           | value of string                        |
| IsActive          | Status           | boolean true if string equals "Active" |
| Title             | Title            |                                        |
| Department        | Department       |                                        |
| Department ID     | DepartmentCode   |                                        |
| Cost Center       | ConstCentre      |                                        |
| Hire Date         | HireDate         |                                        |
| Terminated Date   | TerminatedDate   |                                        |
| Manager           | ManagerEmail     |                                        |
| Work Location     | EmployeeLocation |                                        |
| Team              | Team Email, Team |                                        |
| Display Full Name | DisplayName      |                                        |

**Collecting Additional Fields**

Any additional field from the employee business object can be extracted as a string by adding it to a comma-separated list in the **Additional Properties** field during integration configuration. These values will be added as custom properties on the Employee object shown in Veza.

For example, to collect the employees DN and extensionAttribute1 set **Additional Properties** to `DN,extensionAttribute1`


---

# Agent Instructions: Querying This Documentation

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

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.veza.com/4yItIzMvkpAvMVFAamTf/integrations/integrations/ivanti_nurons_hr.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.