Infinity Documentation

What are you looking for?

Get Started User Guide Administrator Guide

Explore the major capabilities and documentation areas available in Infraon Infinity.

Can't find what you're looking for? Explore the documentation or contact the Infraon support team for assistance.

To add a new software license, navigate to the top panel and select New License.

Software licenses can be added using two methods:

• Manually

• Import from CSV

Manually

Fill in the basic license information as described below, then click Next.

License Information | Basic Details

Additional Details | Add Additional Information

Once all required details are entered, click Submit to add the software license to the platform.

It allows administrators to bulk add or update software licenses using a predefined CSV template.

Step 1: Go to Software License Management and click New License → Import from CSV from the top panel.

Step 2: Click Download CSV File to download the empty CSV template. Use this template to prepare software license data in the required format.

Step 3: Open the downloaded CSV file and fill in the required license details.

Step 4: Upload the prepared CSV file. On the Column Matching screen, map each CSV column to the corresponding software license field in the system, then proceed.

Step 5: The system validates all uploaded records. If issues are detected—such as missing mandatory fields, invalid values, incorrect date formats, duplicate licenses, or unsupported file types—appropriate error messages are displayed.

Step 6: If validation errors exist, download the invalid records for review and correction.

Only valid records will be processed. Click Proceed with Valid Records to continue.

Once the import is successful, the system displays a confirmation message. The imported software licenses are added to the Software License Management page and are available for review and further updates.

The Dedup Rules page allows administrators to define the conditions used to identify duplicate asset records and determine how those records should be handled.

What you see on the screen

The rule list displays information such as:

Click New Dedup Rule to open the Rule Builder. Users can configure condition groups, similarity thresholds, perform a dry run, and publish the rule.

The Two Records Are Duplicates When section allows users to define the conditions used to determine whether two asset records should be considered duplicates. Users can add one or more conditions and combine them using AND or OR operators.

• AND requires all specified conditions to match before two records are identified as duplicates.

• OR requires at least one of the specified conditions to match.

Users can also organize conditions into groups to create more flexible duplicate-matching rules.

Example

Consider two asset records with the following details:

• Asset 1: Dell Laptop, Serial Number SN12345, MAC Address AA:BB:CC

• Asset 2: Dell Laptop, Serial Number SN12345, MAC Address XX:YY:ZZ

If the rule is configured as:

both the Serial Number and Asset Name must match for the records to be identified as duplicates.

If the rule is configured as:

the records can be identified as duplicates when either the Serial Number or MAC Address matches. This is useful when one identifier may not be available for every asset.

The Infraon Platform is the central hub for configuring and managing various aspects of your Infraon Infinity environment. It provides a user-friendly interface for accessing and managing sub-modules that cater to different administrative tasks.

Let's see each one in detail:

Once the necessary configurations have been completed in the ARC module, such as enabling prediction and/or forecasting and selecting the appropriate change point scale, business profiles, and other parameters, the system begins processing and modelling the data.

After completing the configuration:

1. Go to Assets → IT Asset and open the relevant asset from the list.

2. In the left panel, click on the Resources section.

3. Select the specific resource (e.g., Ethernet, Virtual Memory) for which AIOps was configured.

4. Choose the statistic or metric (e.g., CPU Utilization, Bandwidth) you want to monitor or analyze.

Let's see in detail.

Roles define the level of access, responsibilities, and actions a user can perform within a project. They act as a control layer that determines how users interact with projects, tasks, workflows, and other configurations.

Each role is mapped to specific privileges (configured in the Roles & Privileges module) that control permissions such as viewing, creating, editing, deleting, and performing workflow actions like approval or review.

Roles are assigned to members either directly or through teams, ensuring that users have clearly defined responsibilities within a project.

It helps in identifying:

• What actions a user can perform within a project

• Which users are responsible for specific activities

• How access and control are distributed across the project

Infraon provides a set of default roles within the Project Management module to simplify initial setup and ensure standardized access control. These roles come with predefined permissions and can be directly assigned to members or teams.

The default roles available are:

Default Roles | Basic Details

Privileges | Basic Details

A role can be assigned to multiple members, and a member can have different roles across different projects. Roles are reusable and can be applied across multiple teams and projects to maintain consistent access control and responsibility mapping.

• List of roles with:

  • Role Name

  • Description of the role

  • Associated permissions (based on configured privileges)

To create a new role in Project Management:

• Click the + Add option available on the top-right corner and select Add Roles.

• The Add Role sidebar opens.

• Enter the Role Name.

• Provide a Description to define the responsibility or purpose of the role (optional but recommended).

• Ensure that the required privileges are already configured in the Roles & Privileges module.

The Software License module helps track and manage software licenses across the organization. It allows administrators to record license details, monitor allocation and usage, and maintain compliance by mapping licenses to software, publishers, and vendors.

How does it work

These are added manually or imported using CSV and mapped to the relevant software and publisher. The system tracks purchased and allocated permits in real time and supports scheduled usage checks to monitor thresholds. Licenses can be searched, filtered, edited, or updated in bulk to maintain accurate and compliant license records.

What you see on the screen

The page displays all available licenses in a centralized list. From the left panel, users can view licenses grouped by publisher categories, making it easier to navigate and manage licenses across different software vendors.

Software License | Basic Details

The Actions button in the top panel provides options to manage software licenses in bulk.

This option allows administrators to configure scheduled notifications when software license usage exceeds a defined threshold.

Schedule Usage Alerts | Basic Details

Once configured, the system automatically monitors license usage based on the defined schedule and sends notifications to the selected recipients whenever the usage threshold is exceeded.

This option allows administrators to update existing software licenses in bulk using a CSV file.

Using Bulk Edit, users can modify license attributes, including license count, cost, validity dates, compliance details, notification settings, and allocation information, for licenses already in the system.

Refer to for detailed steps on file preparation, column mapping, and validation rules.

The Template Configuration module allows administrators to manage and customize predefined email templates used across the Infraon Infinity platform. These templates are used for asset allocation, deallocation, hardware and software change notifications, ticket escalations, reassignment notifications, and SLA escalation alerts.

Administrators can edit the available templates to modify email content, field mappings, privacy policy text, and notification details based on organizational requirements. The module also supports enabling a comment field in allocation and deallocation templates for end-user acknowledgment workflows.

Available Templates | Basic Details

Once the initial customization is saved, you can use Infraon. Your default landing page looks like the below:

There are three default sections across all Infraon modules/pages.

Let's see these in detail:

The top panel has the below options to view:

The left menu panel can be expanded to view menu labels.

A notification icon, visible across all Infraon modules, displays your number of new alerts. Clicking this icon reveals a panel containing both informational updates and task-related notifications.

In the section, you can view messages from this panel, approve or reject requests, and check product updates. The panel includes alerts and information about recent changes or additions to the product.

The CI Rule Configuration empowers administrators to automate how Configuration Items (CIs) are discovered, categorized, and managed in your environment. Admins can select and configure specific rules based on different criteria to streamline CI management.

Department Rule

This rule automates department assignments for your Configuration Items (CIs). With this rule enabled, whenever a department is linked to an asset within the system (mapping can be enabled or disabled), a CI relation is automatically created. This eliminates manual assignment, ensuring accurate and up-to-date departmental ownership of CIs throughout your IT infrastructure.

Location Rule

The Location Rule automated location assignment for your Configuration Items (CIs). Similar to the Department rule, admins can enable or disable location mapping on assets. When enabled, this rule automatically creates a CI relation whenever a physical location is linked to an asset. This eliminates manual effort, guarantees CIs are accurately assigned to their corresponding locations within your IT infrastructure, and improves organization and location-based reporting.

Requester Rule

The Requester Rule automates by enabling or disabling requester mapping on assets. Admins can configure this rule to automatically create CI relations whenever a service request or incident is linked to a specific user. This eliminates manual assignment and ensures CIs are associated with the appropriate requester, providing valuable insights into departmental or user-based IT asset usage.

Software Rule

The Software Rule simplifies CI management by automating the creation of CI relations for discovered software. Admins can turn software mapping on or off on assets within the system. With this rule active, a CI relation is automatically created whenever software is identified or manually linked to an asset. This eliminates manual effort and ensures accurate tracking of software assets associated with specific hardware, improving overall visibility into your IT infrastructure.

The User Rule automates CI relations based on designated technicians or managing users within your ITSM system. By enabling or disabling "manage by/technician" mapping on assets, you can configure this rule to create CI relations automatically. Whenever a specific user is assigned as the technician or manager for an asset, this rule triggers the creation of a CI relation. This eliminates manual assignment, ensuring CIs are linked to the appropriate technicians, which can be crucial for service accountability and troubleshooting workflows.

Teams represent logical groupings of users within Project Management, organized based on function, department, or project requirements. They help in structuring collaboration by grouping members who work together on similar tasks or responsibilities.

A team consists of multiple members and is associated with specific roles that define responsibilities within a project. Teams simplify assignment and management by allowing users to be handled collectively rather than individually.

It helps in identifying:

• Which group is working on the project

• How members are organized within a project

The Meeting module allows users to create, schedule, and manage meetings directly from the Workspace Calendar. It supports one-time, instant, and recurring meetings with attendee management, location selection, meeting associations, calendar views, filters, and meeting lifecycle operations such as starting, joining, canceling, and ending meetings.

The module also supports multiple meeting types, including video conferences and conference room meetings, while allowing meetings to be associated with operational entities such as Tickets, Requests, Changes, and Assets.

What you see on the screen

This page displays a calendar-based meeting management interface that lets users schedule and track meetings across the Month, Week, Day, and List calendar views.

Users can create meetings, refresh calendar data, and apply status and meeting-specific filters. The calendar also lets users navigate between dates and view meetings by status, attendee email, VC location, region, meeting type, and associated records.

Meeting | Basic Details

Meeting | Filters

Meeting | Calendar Legend

The calendar uses color coding to indicate meeting status and type.

Use this option to create and schedule a new meeting from the Meeting calendar.

The meeting creation process is organized into the following four sections:

• Meeting Details

• Location & Invitees

• Host & Contact Person

• Agenda & Attachments

Add Meeting | Field Descriptions

Add Meeting | Locations & Invitees

Add Meeting | Host & Contact Person

Add Meeting | Agenda & Attachments

Once all required details are added, click Schedule Meeting to create and schedule the meeting.

The page displays assets that have been archived from the active IT Assets and Fixed Assets pages. You can archive assets when they are no longer required for active asset management, such as when an asset is retired, disposed of, or becomes inactive. Archiving removes the asset from active asset views while retaining its asset information for future reference and management.

What You See on the Screen

The Archived Assets page provides separate tabs for IT Assets and Fixed Assets. Each tab displays only the archived assets of the selected asset type.

Archived Assets | Basic Details

The Shift Calendar module in Workspace allows users to view and manage configured team shifts directly from the Calendar section. It provides a timeline-based view of shift schedules, assigned members, shift duration, shortages, and leave details for different teams within the department.

For detailed information about configuring shifts, business hours, and shift schedules, refer to the Shift Configuration documentation.

What you can do here

Using the Shift Calendar module, users can:

• View configured shifts for different teams within their department.

• View shift timings, working duration, shortages, and leave details.

• View members assigned to a particular shift.

• Add users to a shift.

• Remove users from a shift.

• Monitor operational coverage using the timeline-based shift view.

• View on-duty and off-duty member details for the selected shift.

When devices are discovered using Infraon (inventory agent), the software installed in them is listed under the asset module as Software.

What do you see on screen?

Download, view, and manage software entries, also blacklist/whitelist and uninstall software.

The discovered software is categorized based on the manufacturer. You have the option to blacklist or whitelist a specific software.

Check the Blacklist and Whitelist and Software License Management module for details.

Add New Audit

Use this option to create a new IT Asset Audit record for performing physical and/or logical verification of assets.

To add a new audit:

• Navigate to IT Asset → IT Asset Audit Record.

• From the top panel, select Add New Audit.

• Configure the audit using the fields described below.

Add Audit | Audit Details

Click Next to proceed to asset mapping.

This step associates assets with an audit record. In this step, users select the IT or Fixed Assets that must undergo verification as part of the audit. Multiple assets can be linked to a single audit to ensure comprehensive coverage.

Assets are added through a dedicated selection window, where users can search, filter, and select the required assets. Once linked, these assets become part of the audit scope and are evaluated using the assigned audit checklist.

To add the asset, select Add to proceed.

Link Asset | Add Audit

Now select the assets to link them to the Audit records.

Links the selected assets to the audit record, adds them to the audit scope, and then moves the workflow to the Audit Checklist stage.

Here, users can select the required to configure the checklist that will be used for audit execution. The selected template defines the verification fields and checkpoints that auditors must complete for the mapped assets.

Once the configuration is complete, click Save to finalize and create the audit record in the system.

Once an audit record is created and assigned, the designated auditor can perform the audit for the mapped assets. The audit process allows auditors to verify asset location and condition using the configured checklist and record audit results for each asset.

From the IT Asset Audit Record list page, auditors can initiate the audit directly from the Action column.

• Navigate to IT Asset → IT Asset Audit Record.

• In the Action column, select Audit for the required audit record.

• The audit workspace displays the mapped assets and the associated audit checklist.

• Auditors can Export asset and checklist data in XLSX format, if required.

• Select an asset and click Asset Audit to begin auditing the selected asset.

The Audit details page has three tabs:

The Audit Details screen is used to perform the actual audit for an asset. It captures location verification, condition checks, audit status, and checklist responses based on the selected template.

Audit Details | IT Asset Audit Record

After completing all required fields and checklist entries, click Submit Audit to save the audit results for the selected asset.

This action records the audit outcome and updates the audit progress for the overall audit record.

The Attachments section allows auditors to upload and manage supporting evidence related to the audit. This helps validate audit findings and maintain verifiable records for compliance and future reference.

Auditors can upload files such as asset photos, barcode/QR code images, condition evidence, or audit documents directly from this section.

Add Attachments

To add an attachment:

• Navigate to Audit Details.

• Open the Attachments section.

• Click Add to upload files.

• Select the appropriate category and provide an optional description.

Attachments | Fields Description

Uploaded attachments are displayed within the Attachments section and remain linked to the audited asset for reference.

The Recent Activities section displays a chronological log of all actions performed on the audit record. It captures key events, including audit creation, asset mapping, status updates, attachment uploads, and audit completion.

This section provides clear visibility into who performed each action and when, ensuring traceability and accountability throughout the audit lifecycle.

Once all assigned assets have been audited and the required details are recorded, the auditor can select Mark as Completed to finalize the audit. This action confirms that the audit activities are complete and updates the audit status accordingly.

To add a new Purchase Requisition, click + Add Purchase Requisition available at the top-right corner of the Purchase Requisition page.

In Purchase Requisition, there are three tabs available for configuration:

• Purchase Requisition Properties

• Item Details

• Terms and Conditions

This module is designed for initial user registration within the Infraon Infinity platform. Administrators can verify their accounts by providing essential details like their email address, company name, and mobile number. This information is stored securely within the Infinity data, allowing registered administrators to access and utilize the various functionalities.

The Merge History page provides a record of previous deduplication actions and allows users to review what happened to duplicate clusters.

Merge History | Top Panel

History Details

Once Software Metering rules are configured and data is collected from agents, the Software Metering Summary page provides an aggregated view of application usage across devices. This view helps analyze how frequently applications are used, for how long, and across how many endpoints.

For each rule, the summary grid displays:

A Space is a logical grouping within a project that organizes tasks, teams, and activities. It helps segment the project into manageable sections such as phases, modules, departments, or workstreams.

Spaces enable better work structuring by allowing teams and roles to be assigned at a more granular level, ensuring clear ownership and controlled access across different parts of the project. It helps in identifying:

• How project work is divided into logical sections

• Which teams or users are responsible for specific areas

Auto Deduplication identifies and consolidates duplicate asset records created through multiple discovery sources, manual entry, imports, or integrations. It helps maintain a single trusted asset record (Golden Record) while preserving historical data and audit traceability.

Navigate to IT Asset/Fixed Asset → Action List →Deduplication to open the Duplicate Cluster page. The system groups potential duplicate asset records into clusters based on duplicate signals and similarity. Users can review the clusters, select the appropriate surviving record, resolve field conflicts, preview the impact, and then merge, split, mark the cluster as not duplicate, or leave it for later.

Asset Deduplication provides capabilities to:

• Identify potential duplicate asset records.

A Purchase Requisition (PR) is used to formally request the procurement of items or services required for business operations before a Purchase Order is created. It helps organizations track, review, approve, and manage procurement requests through a structured workflow.

For example, an employee can submit a Purchase Requisition to request laptops, software licenses, networking devices, office equipment, or vendor services. Once submitted, the PR moves through the configured approval workflow before proceeding to the procurement or Purchase Order stage.

It is commonly used for:

• Hardware procurement requests

• Software or license requests

• Vendor service requests

• Office and operational purchases

• Internal approval-based procurement processes

Unlike a which is issued to a vendor to confirm procurement, a Purchase Requisition is an internal request used for approval and procurement planning before the actual purchase process begins.

A Purchase Requisition follows a workflow-driven process in which each PR moves through predefined stages based on the configured and approval conditions. Users can create PRs, add line items, configure vendor and address details, submit the PR for approval, and track the approval status from the PR view page.

Workflow Stages | Purchase Requisition

The Purchase Requisition page displays all created PR records in a grid view. Users can search, filter, create, edit, delete, and manage Purchase Requisitions. The page also provides quick access to PR details, including priority, requested date, total amount, workflow status, and vendor information.

Purchase Requisition | Basic Details

Members represent all users who are associated with projects through teams and roles. It defines who is involved in project execution, how responsibilities are assigned, and how task ownership is managed.

Members are the actual users who perform work within a project. They are mapped to roles and teams, which determine their responsibilities and participation across different projects.

It helps in identifying:

• Who is working on the project

• Who is assigned to specific roles

• Who is responsible for tasks

A member can belong to more than one team and can have different roles across different projects. Task ownership and assignment are mapped to members, ensuring each task is assigned to a responsible user based on their role within the project.

• List of users with:

  • Username

  • Associated projects

  • Team

To add members and assign them to roles within Project Management:

• Click the + Add option available on the top-right corner and select Add Members.

• The View Members sidebar opens, displaying existing member-role mappings.

• Each row represents a role with associated members.

• To create a new mapping, click Add Items.

• In the newly added row:

  • Select one or more users from the Members dropdown.

  • Select the corresponding Role from the Select Role dropdown.

• You can add multiple rows to map different members to different roles.

• Use the delete icon to remove any mapping if required.

Click Save to apply the changes.

This configuration ensures that selected users are assigned appropriate roles within projects and can participate in task execution in line with their assigned responsibilities.

There are multiple types of assets in an organization. The first step of asset management is the categorization of assets. Broader categorization enables better management. The default categorization of assets within Infraon is as follows:

Asset Type -> Asset Category -> Asset Sub-Category -> Asset

The process of managing an asset depends on its type. Based on asset type, Infraon assets have been split into four modules.

IT Assets are physical assets or devices used in an organization's business activities that fall under the responsibility of IT staff. For example, computers, servers, routers, scanners, fax machines, printers, modems, hubs, and IoT (Internet of Things) devices.

Fixed Assets are any physical objects or vehicles you consider 'assets' to your organization. It can be easily converted into cash—for example, vehicles, machinery, equipment, etc.

Consumables are assets that organizations use. They must be replaced regularly because they wear out or are used up—for example, mouse devices, external keyboards, computer cables, printer toners, etc.

Software Assets are any functional software in an organization that requires service level agreement to ensure compliance with software licenses. For example, software assets may be internal or external, on-premises, or in the cloud.

Within these asset Types, assets are further classified into:

Categories – Categories are also referred to as 'parent' categories. A category is the first division of assets within the selected asset type. For example, within IT assets, there can be categories like laptops, desktops, etc.

Sub-Categories - Sub-categories are also referred to as child categories. The sub-category is the next level of asset division within the category. For example, if the categories are laptop or desktop, sub-categories within IT assets can be Dell, Lenovo, Apple, etc. Assets or asset items can be added here.

Refer to the and sections for details and instructions.

• Expand the left menu panel.

• Click on Assets

• Select the respective asset type.

• Click on the respective asset category or asset to view more details.

SBOM provides a consolidated view of applications, software components, assets, and vulnerability information, enabling users to review software composition and assess associated risks.

Top Panel Details

The CMDB part of ITSM is incorporated as Assets within Infraon. Infraon Assets allows administrators/asset managers to view and manage all organizational assets, i.e., all IT and non-IT assets, in one place.

Any device with an IP is known as an IT Asset or Node. It can be a Server, Router, Storage Device, Transport Device, Wireless controller, Access point, etc.; as part of an Asset, Infraon collects and maintains the complete inventory details for an asset.

Infraon collects basic yet important inventory information for each device, server, hypervisor, and application. The inventory information includes:

• IP Address

• Hostname

• Device Type

• Vendor

• Model

• Serial Number

• Operating System and Version

• MAC Address

• CPU Information

• Memory

• HDD Details

• Port Level information

Etc.,

• For Hypervisors,

• CPU Socket

• No of Processor

• CPU Speed

Etc.,

The Infraon Admin Guide is explicitly designed for administrators responsible for configuring, managing, and maintaining the Infraon Infinity platform. This guide focuses on modules and functionalities exclusive to the Management Admin role, such as system configuration, user management, and platform settings.

Why do I see only a few modules here?

This guide includes only those modules and features that are exclusive to Management Admin users, such as:

• Platform Configuration

• User & Role Management

• System Settings

The remaining modules are shared between both users and admins. To avoid duplication and provide a clear, role-based experience, these shared modules are documented under the section.

If you’re an Admin looking for detailed documentation on all other modules:

• Navigate to the for technician-level modules and operational features.

• Use the left-side navigation menu to explore topics by module.

• Use the search bar at the top of the page to quickly find specific content.

The Notification module allows you to configure project-specific notification rules and templates to automate notifications for project events and activities. These notifications help keep project members informed about important updates and workflow events throughout the project lifecycle.

Using the Notification module, you can:

• Configure notification rules to define when notifications are triggered.

• Create and manage notification templates for consistent notification messages.

It is used to define and manage the people involved in project execution. It provides a structured way to organize users into teams, assign roles, and control responsibilities within projects.

This sub-module ensures that each project has clearly defined ownership, role-based responsibilities, and proper access control. The Teams & Roles structure follows this hierarchy:

Each level defines how users are grouped and how responsibilities are assigned within a project.