Only this pageAll pages
Powered by GitBook
Couldn't generate the PDF for 203 pages, generation stopped at 100.
Extend with 50 more pages.
1 of 100

NCCM User Manual

Loading...

Admin Guide

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

User Guide

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Loading...

Product Documentation

NCCM Documentation

What are you looking for?

rocket-launchGet Started User Guide Administrator Guide

Quickly access the documentation you need to get started, manage the product, or explore its capabilities.

Start here

New to Infraon NCCM? Follow these steps to find the right documentation and get started.

Each documentation set follows the same order, so the opposite path works for whichever module you begin with.

1

Choose your guide

Start with the User Guide if you are using the product, or the Administrator Guide if you are configuring and managing it.

2

Complete the basics

Follow the getting-started documentation to onboard devices and run your first configuration backup.

3

Explore the product

Use the documentation to explore the configuration management capabilities relevant to your role.

4

Go deeper when needed

Move on to advanced configuration, APIs, integrations, troubleshooting, and release documentation.

Explore Infraon NCCM

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

Cover

Configuration Profiles

Define how device configurations are collected, stored, and versioned.

Cover

Configuration Backups

Schedule and run backup jobs, and restore or roll back configurations.

Cover

Configuration Policies

Define compliance baselines and evaluate devices against them.

Cover

Configuration Rules

Build the rule logic that policies use to assess configurations.

Cover

Configuration Templates

Standardize and push configuration changes across devices.

Cover

CLI Jobs

Run command-line operations against managed devices.

Cover

Vulnerability Management

Identify and track configuration and firmware vulnerabilities.

Cover

Reporting & Analytics

Analyze compliance posture, configuration drift, and job outcomes.

Administration

Configure and maintain Infraon NCCM, manage users and access, and control system settings.

Covers system configuration, user management, roles and permissions, notifications, workflows, integrations, security, and reports.

Open Administrator Guide

What's new

Stay up to date with new features, enhancements, changes, and bug fixes in Infraon NCCM.

Developer resources

Integrate Infraon NCCM with applications and workflows using the available APIs and integration resources.

terminalExplore API Documentation

Need help?

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

Explore Documentation life-ringContact Support

Getting Started

This section will guide you through the initial setup and configuration of Infraon, helping you get up and running with the platform's key features. Follow these steps to customize your Infraon experience and manage your product effectively.

Infraon Platform

The Infraon Platform is the central hub for configuring and managing various aspects of your Infraon 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:

Geomap

Geomap allows for visualization of the location of all the assets by associating a geographic area with GPS coordinates. It enables you to visualize the location of the assets and also provides information about their working condition.

Geomap makes managing assets, identifying opportunities, and providing quick service easy. If the technician's location matches the asset location, assigning the technician becomes straightforward, resulting in a quick resolution. Prompt service, in turn, enhances the customer experience.

Infraon URL

Administrators can customize employees' web addresses (URLs) to access the Infraon portal. This functionality provides greater flexibility and branding opportunities.

For instance, instead of using a generic URL provided by Infraon, administrators can create a custom URL that reflects your organization's name.

This customization enhances brand recognition and potentially improves user experience by making the helpdesk URL more easily recognizable to employees.

Admins can choose a user-friendly and memorable option, such as "EverestIMS" for your full company name or "EIMS" for a shorter version.

Introduction

Infraon NCCM User Manual

Information in this document is subject to change without prior notice. Companies, names, and data used in examples herein are fictitious and for illustration purposes only unless otherwise stated. No part of this document may be reproduced or transmitted in any form or by any means, electronic or mechanical, for any purpose without the express permission of Infraon Corp.

About this Document

This document aims to outline the features of Infraon products and give detailed information on how to customize & use all the modules available within Infraon products. This document contains sensitive information. Access to this document or the content within should be provided only to authorized users of Infraon products software on a need-to-know basis.

Any unauthorized use or sharing of information in this document will be considered a breach of respective confidentiality/copyright and shall be treated accordingly.

Notifications

Infraon is enabled with an intelligent notification system. Infraon Notifications are displayed as floaters across all pages. The respective notification icon is displayed with the notification count when a notification is triggered.

The notifications module is a part of Infraon Configuration and is further split into:

Messenger Audit - View the log of communications sent from and received within Infraon

Configure SMS - Configure SMS gateway to enable SMS notifications from Infraon.

Configure SMTP - Configure your email server details to send and receive emails from Infraon.

Trigger Configuration - Configure a trigger to trigger an alarm or an event.

Let's see each of these in detail.

Configure SMS

The Configure SMS module allows administrators to integrate and manage SMS gateway services within Infraon Infinity. It is used to configure SMS delivery settings for sending notifications, alerts, OTPs, approvals, ticket updates, and other platform messages.

The module supports:

  • Global SMS configurations

  • Customer-specific SMS configurations

  • SMSGateway and SMPPGateway integrations

  • Primary and Secondary gateway setup

  • SMS configuration testing before activation

The Configure SMS module connects Infraon Infinity with external SMS service providers. Administrators can configure the required gateway details, request parameters, authentication headers, and delivery settings based on the SMS provider.

The module supports two SMS configuration types:

  • SMS Gateway – Uses API/HTTP-based SMS integrations.

  • SMPP Gateway – Uses SMPP protocol-based enterprise SMS communication.

Each configuration can include:

  • Primary Gateway

  • Secondary Gateway (Failover)

Once the configuration details are added, administrators can move to the Test section to validate SMS delivery before saving the configuration.

Infraon's Knowledge Base

Infraon's Knowledge Base module enables users to author their articles, curate articles/guides from internal or external sources, and use, share, and manage knowledge across organizations and end-users.

Infraon's KB is categorized into:

  • Article -  The article must contain complete Information with details on all aspects of the selected topic. Articles are usually intended to solve a common problem - How to configure an Email account on Outlook or How to reset an Infraon password, etc., news sourced internally (Updates on the KB module of Infraon)or externally, What to expect with the latest update of MS Office), etc.

  • FAQ - Frequently asked and answered questions.

Welcome to Infraon!

After completing the registration process, log in using the default credentials provided or opt for a Google account login.

For more details on login options, refer to the Login Settings.

Once logged in, you will be directed to the screen below.

The' Getting Started' page lets you easily configure essential settings for new accounts. There are seven key steps in this process:

Customize the portal URL to allow your employees easy access to Infraon. Although it's recommended to stick to the default URL, you can modify it later if needed.

For more information on customizing the URL, refer to the module.

Configure a dedicated support email address to ensure all incoming communications are automatically converted into tickets. This address will also be used for all customer-related responses. You can set up a new email on Infraon's domain or link your existing mail server.

For step-by-step instructions, visit the module.

Vulnerabilities

The module provides detailed insights into vulnerabilities based on device OS, affected nodes, vendor details, CVE, OS version, and more.

to access the detailed Vulnerabilities content and manage your network jobs effectively.

Configuration Templates

Template is a Collection of commands (one or more) with zero or more variables to be executed on devices for specific operations (like ACL Modification, Route ADD, Interface NAC configuration, Interface IP Change, Interface Enable Disable, SNMP/LLDP/CDP enable or Disabling, OS Upgrade).

By substituting different values (to variables) for different Devices, the user can reuse the same template for similar operations on multiple devices. Device Credentials, Device Interface Name/IP Address, and command inputs will become a variable portion in the command template.

to access the detailed Configuration Templates content and manage your network jobs effectively.

Rebrand Infraon

The Rebrand Infraon module within the Infraon Portal allows administrators to customize the platform's appearance to align with the organization's branding. This fosters a more cohesive user experience and strengthens brand recognition.

Here's how it works:

Upload your organization's logo to display it within the Infraon platform prominently. The recommended size (170x96 px) and supported file formats (jpeg, png) are provided to ensure optimal display.

Admins can choose from pre-defined color themes (Fixed or Spaced Out) and light, dark, or semi-dark variations to match your organization's branding preferences.

Administrators can define specific colors for elements like the logo container, navbar, and user interface text for even greater customization. This allows for a highly tailored look and feel.

Admins can select the preferred language (English or Hindi) for the entire platform interface, ensuring user comfort and efficient interaction with the ITSM system.

Once the changes are satisfactory, click “Save” to proceed.

Messenger Audit

Messenger Audit acts as the Notification Log. Displays the complete list of notifications triggered and received within Infraon.

Use the options on the left panel to filter out notifications based on the notification type.

  • Email

  • Slack

  • WhatsApp

NCCM

This enables Network administrators to efficiently manage remote IT networks and IP-enabled security devices from a centralized location.

to access the detailed network configuration and change management content and manage your network configurations effectively.

Calendar View

The calendar view summarizes daily activity, including processed successful, failed, completed, and total configurations.

This is a privilege-based feature: The user can access, view, add, edit, delete, execute, and export only if the administrator has given them privileges. This will be defined under roles and privileges.

As the name states, the calendar view gives a detailed report of the selected parameters. By default, it displays information for the current month. However, arrow keys can be used to navigate to the previous months(s)/year(s).

  • Calendar Views display details based on daily NCCM activity.

  • Complete Count: Displays the Completed device count enabled for the day's download.

Information - A piece of information that can be published to keep others informed about the topic. It can be a problem, instructions for a single step in a process, etc.

  • Known Error - When a problem has been reported and classified as 'Known Error' and contains instructions for a temporary fix or workaround.

  • Solution - When a reported problem has a permanent solution. Known errors must be deprecated when a solution is found.

  • The main page displays all recent articles with an option to sort the highest rated or bookmarked articles.  Information in the knowledge base is grouped into 'Categories' defined in the 'Service Catalog.'

    Below are the actions available on each KB:

    • Bookmark - Bookmark an article used frequently. Bookmarked posts are displayed on the right panel for easy access.

    • Helpful - Mark if the KB was helpful.

    • Rating - If the article was helpful, add ratings and reviews for the article. If not beneficial, add feedback to help improve.

    • Comment - Add a comment on the KB.

    • Like - Like an article.

    • Edit or Delete - Privileged users can edit or delete the KB.

    • Version History - View Version history and changes.

    • Attachments - View documents/files attached to the KB

    The default status of a KB would be Draft, which is changed to “Published” when the KB is published.

    SMS

  • Trash

  • You can view, reply to, or forward messages using the respective icons on the message.

    How does it work?

    Logo Upload

    Color Theme Selection

    Granular Color Control

    Language Selection

    Click here
    Click here
    Click here

    Report

    Data without perspective can be useless. To maximize the use of data, Infraon provides attractive and easily customizable reports that ensure data monitoring is appropriate for everyone within the organization.

    Infraon reports provide a detailed analysis of the performance and fault-related data collected. Reports include:

    • Trending, pattern, and summary analysis to analyze past behavior.

    • Perform trend analysis and pattern analysis with historical data to help predict future behavior.

    Infraon's default reports are highly configurable and flexible. Collecting, summarizing, and pruning historical data makes long-term data easily manageable. The combination of real-time and historical reporting aids in identifying trends, predicting system behaviour, and making well-informed management decisions to drive future expansions.

    Infraon's timescale and data fields in the report filter the asset details at a granular level using the columns, timescale orders, and order by. Improvising asset report functionality, providing enhanced data analysis and filtering capabilities.

    Infraon supports exporting reports and pre-configured auto-reports in PDF/Excel/CSV formats. Advanced real-time and historical reporting capabilities can be customized according to user preferences to help them view essential data.

    General Settings

    The general settings module is a part of Infraon Configuration and is accessible by administrators and other users authorized by administrators.

    This module of Infraon consists of three additional modules. They are:

    • Audits:  Infraon monitors and records every user's actions. Only the administrator can access these audits.

    • Business Hours:  Configure business hours to control SLAs and better efficient work allocation.

    • Tag Management:  Tagging is a way of grouping assets, users, etc. Tags can be applied to multiple categories across Infraon.

    • Template: Lets administrators create predefined templates to standardize and speed up recurring processes across modules like Ticket, Request, Change, Release, and Risk.

    Let's see each of these in detail. 

    Infraon utilizes a dynamic, role-based access control system, offering various default roles with pre-defined access levels such as view, add, edit, delete, and copy. Based on organizational needs, administrators can create new roles, modify existing ones, or delete defaults. Default role names can also be edited.

    For detailed instructions, see the Roles & Privileges module.

    Adding users to Infraon is simple. You can invite users by entering their email addresses and assigning them roles. When adding multiple email addresses, separate them with commas. You can invite multiple users across different roles simultaneously, but only pre-defined roles can be assigned.

    Learn more in the module.

    This step allows administrators to deploy Infraon agents—such as inventory agents and data collectors—that efficiently extract data from desktops and network devices.

    For detailed guidance, visit the Bots module.

    You can input your organization's head office, branch office, and other addresses here. Providing this information simplifies the alignment of users, assets, and services across multiple locations.

    For further details, consult the Address Book module.

    Personalize Infraon by customizing its appearance to match your organization's branding. You can change the theme, adjust the colors of the navigation bar and containers, and select your preferred language. Preview changes in real-time and save your favorite look.

    For more details, refer to the Rebrand Infraon module.

    Now that you are all set with customizing Infraon proceed to Know Infraon

    Note: The view may vary depending on the product or product variant your organization selects.

    Customize Infraon URL

    Setup your Email

    Roles & Privileges

    Infraon URL

    Invite Users

    IT Assets Agents

    Add Location details

    Rebrand Infraon

    Mail Automator

    Total: Displays the total node count added to the NCCM tool (to date).

  • Download Success: Displays the count of successful configuration download devices for the day.

  • Download Fail: Displays the count of failed configuration download devices for the day.

  • New Node: Displays the count of new devices for the day.

  • Vulnerable Count: Displays the count of the day's vulnerable devices.

  • Left Arrow navigates to the previous month’s data.

  • Right Arrow navigates to the next month’s data.

  • Clicking a new node redirects to the newly added device list page.

    Note:

    • Clicking complete count redirects you to the status of the download job enabled for the day.

    • Clicking the Success/Fail count will redirect you to the download result page.

    Attendance Configuration

    This module allows administrators to define how attendance is recorded for users. It provides controls to automate attendance tracking and enforce location-based validation using geo-fencing.

    This configuration is primarily used for field users (technicians), in which attendance is validated against GPS location and predefined work boundaries. Attendance records generated based on these settings are stored and can be accessed for monitoring, reporting, and audit purposes.

    How it works

    Attendance behavior is governed by two configuration options:

    • Force Geo-Fence Restriction ensures that users can mark attendance only within a defined range.

    • Auto Clock-In / Clock-Out allows the system to automatically record attendance based on user location.

    These settings can be enabled independently or together:

    • If both are disabled → users can mark attendance manually without restrictions

    • If geo-fencing is enabled → attendance is restricted based on location

    • If auto clock-in/out is enabled → attendance is recorded automatically

    • If both are enabled → attendance is fully automated and location-controlled

    If a user attempts to mark attendance outside the allowed location, the system may trigger an approval workflow before confirming the entry.

    Label
    Action
    Description / Example

    Configure SMTP

    Configuring SMTP server information is mandatory when sending out email notifications from Infraon. SMTP server configuration is a part of 'Getting Started' with Infraon. Mails sent to this address are converted as Incidents. This email address also acts as a reply to the mail address for all customer communication. Before configuring, ensure that you have the below details from your service provider:

    • Host Name

    • Host Username

    • Password

    • Port

    There are two options within the SMTP server configuration. You can configure your existing email address onto Infraon or set up a new one using Infraon's email server.

    Go to Infraon Configuration -> Notifications -> Configure SMTP

    On the page, either use the Microsoft OAuth login or manually enter API credentials.

    Click to log in using the Microsoft account.

    Enter the Microsoft credentials and grant the appropriate permissions to configure the SMTP configuration easily.

    There are two tabs in the SMTP configuration.

    Configuration | Test

    Configuration | Test

    Once the test is successful, click 'Submit' to save the configuration.

    Infraon Configuration

    The Infraon Configuration module consists of all types of configurations required for the efficient functioning of modules. While there are multiple levels of configurations, few of these configurations are mandatory.

    General Settings: Configure business hours, create tags for grouping assets, users, etc., and review the complete audit log.

    User Management: Invite requesters and users, assign roles, group them as teams or departments, and view their leave information.

    Notifications: Configure and track notifications sent through Infraon.

    Infraon Automation: Configure workflows within Infraon to define a flow of process modules like Incident, Request, Etc.

    Bots: Install agents to enable discovery and monitoring.

    Organization: View and add organization and branch locations.

    IT Operations: Add device credentials to initiate the discovery of devices.

    Infraon Platform: Check and edit account configuration settings.

    A few additional configurations are needed to enable device monitoring. Follow the instructions in the links below to enable protocols as required.

    Upgrade Option for Credential-less Organizations! Users can access the management portal to select services. Selected services, with 193 options, are enabled post-payment.

    Enabling SNMP is vital to initiating the monitoring of the routers and switches. Follow the steps below to enable SNMP on Cisco routers and switches.

    • Connect to the router/switch via telnet.

      • prompt#telnet testrouter

    • Now, enter the password to enable mode.

      • Router>enable

    SLA Management

    An SLA stands for Service Level Agreement. ITIL4 defines SLA as "A documented agreement between a service provider and a customer that defines both the services required and the expected level of service." SLA is a detailed document that defines the standards of services the customer expects from the service provider. SLAs differ across services, vendors, and industries. It is an integral part of a vendor contract because it lists the services agreed upon between the parties and the quality, availability, remedies, and penalties.

    In Infraon, the "SLA" module is an SLA-capturing tool. It is not yet implemented as a full-fledged SLA Management tool. It allows the definition of SLA metrics and service details.

    Benefits of SLA:

    • Sets clear guidelines and expectations - An SLA sets clear guidelines regarding expectations and commitments.

    • Improved customer service - Because of the existence of an SLA between two parties, the service provider monitors and measures whether the terms of the service are being met. Thus, the team works efficiently to achieve the deadlines. There will be a decrease in ticket response time, which will improve customer service.

    • Peace of Mind - An SLA gives customers peace of mind because they have a contract they can refer to in case their demands are unmet.

    • Strengthens Customer Relationships - The above-mentioned benefits enable a strong relationship between the service provider and the customer.

    The two essential components of an SLA are Metrics and Penalties.

    Metrics - Metrics are the criteria for measuring services. It is an agreed-upon measurable target between the customer and the service provider. Metrics make it easier to spot SLA breaches.

    Penalty - Penalty is a disciplinary measure to be followed if the SLA is breached. A penalty could be imposed for monetary refunds, service credits, etc. These terms are captured in an SLA.

    Event Management

    Any change observed and detected within your organization is an event.

    The primary objective of the event management module within ITIL is to detect all changes or activities within the infrastructure, observe for anomalies and raise the alarm, if necessary. Events are Infraon's way of active and passive monitoring of

    • CI items like laptops, desktops, etc.,

    • Software licensing and performance

    • Application performance

    • Server performance

    Monitoring the status and availability of items is part of active monitoring, while detection and correlation of operational alerts based on the configured thresholds and triggers are part of passive monitoring.

    Infraon's Event Management module enables users/organizations to achieve their goals through the below steps:

    • There are constant changes in the infrastructure. Ideally, a user's login, upgrade of software/hardware, or regular maintenance are all events. However, these are not events that need to be notified or taken action upon. When there is a change in the server's performance or availability, it needs to be reported immediately. Infraon extracts the necessary data from the happenings of the infrastructure and detects 'events that need attention on occurrence.

    • These anomalies or changes are run through the default thresholds and categorized as basic, informational, major, or performance. Thresholds can be sorted as minor, major, or critical. Refer to the Thresholds section for details.

    • Anomalies and changes are categorized and reported as events.

    Refer to the section for more details.

    Manual Service Mapping

    This functionality empowers administrators to define automatic ticket assignment rules based on impacted services and requester tags, enhancing the workflow and improving service delivery.

    How does it work

    Business rules automate ticket assignments based on predefined criteria. They are configured to:

    Assign tickets based on impacted service:

    Tickets associated with a specific impacted service (e.g., hardware diagnostics) can be automatically assigned to a designated team or technician based on expertise level.

    Assign tickets based on the requester tag:

    Tickets created by users of a particular requester tag (e.g., front desk) can be routed to a predefined team or technician.

    Creating Business Rules with Manual Service Mapping

    This section guides admins through creating business rules with manual service mapping.

    Define the Business Rule

    • Assign the rule a clear and descriptive name (e.g., "Hardware Diagnostics—Assign to IT Team Level 1").

    • Select the type of rule (e.g., "Impact Service").

    • Briefly explain the rule's purpose (e.g., "This rule automatically assigns tickets related to hardware diagnostics to IT Team Level 1 technicians").

    • Select the specific service impacted by the ticket (e.g., "Hardware Diagnostics").

    • Choose the logical operator for the rule (e.g., "equals").

    • Assign To:

      • Group/Team: Specify the team responsible for addressing tickets related to the impacted service (e.g., "IT Team").

    Considering a scenario where an IT team handles hardware diagnostics. Creating a business rule with the following configuration ensures tickets related to hardware diagnostics are automatically assigned to IT Team Level 1 technicians:

    • Business Rule Name: Hardware Diagnostics - Assign to IT Team Level 1

    • Type: Impact Service

    • Description: This rule assigns tickets related to hardware diagnostics to IT Team Level 1 technicians.

    • Impact Service: Hardware Diagnostics

    Business rules can also be based on requester tags. Here's how to create a rule for a specific requester tag:

    • Assign Tickets from the Front Desk to the Procurement Team Level 1

    • Add the respective Requester Tag as Front Desk Manager.

    • Then Assign To:

      • Group/Team: Procurement Team

    This rule ensures any ticket created by someone with the "Front Desk Manager" tag is automatically assigned to the Level 1 Technician within the Procurement Team.

    Business Hours

    The daily working hours of teams/departments within an organization are called business hours. This, in turn, aids in assigning work based on users' working hours and setting and meeting SLAs.

    When creating a profile, you could choose between specific working days/hours and 24/7 availability.

    Use the Exclude Hours option to add a break in the business hours. This can be the weekend, an official lunch hour/break time, or a change in the Technician's shift. SLAs are adjusted as needed.

    To view the complete list of holidays applicable to your region, add 'Holiday' or click on import holidays. 'Exclude hours and Holidays' are excluded while calculating SLAs for the ticket.

    • Go to Infraon Configuration -> General Settings -> Business Hours.

    Know Infraon!

    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.

    Clicking vulnerable count redirects to the vulnerable list page.

    Password:

  • Router#

  • The next step is to configure your device:

    • Router#configure terminal. Enter one configuration command per line and finish each line with CNTL/Z. Router(config)#

  • Add the Read-Only community string using the following command.

    • Router(config)#snmp-server community public RO ('Public' is the Read-Only community string here)

  • For a Read-Write community, use the below command.

    • Router(config)#snmp-server community private RW ('Private' is the Read-Write community string here).

  • You can now exit the configuration mode and save the settings

    • Router(config)#exit Router#write memory Building configuration... [OK] Router#

  • Additional Configurations

    Enabling SNMP in Cisco Routers/Switches

    Pro feature in Infraon configuration

    Enable SNMP Configurations in Cisco Routers and Switches

    Two Essential Components of an SLA

    Expertise: Define the specific expertise required for handling tickets (e.g., "Hardware").

  • Level: Select the appropriate technician level within the assigned team (e.g., "Level 1").

  • Operator: Equals

  • Assign To:

    • Group/Team: IT Team

    • Expertise: Hardware (Optional)

    • Level: Level 1

  • Level: Level 1 Technician

    Configure Impact Service Mapping

    Example:

    Business Rules for Requester Tags

    Example:

    Users
    Technicians or NOC users can use these events to perform necessary actions.

    Note: If triggers are configured for events, a notification is triggered either at the event's occurrence or after correlating.

    Events

    Policies

    The ‘Policies’ page displays the complete list of policies available on NCCM. Multiple Filter options and a quick action panel are also available.

    Click here to access the detailed Policies content and manage your network jobs effectively.

    Authentication Profile

    The Authentication Profile module manages user authentication for accessing network devices via CLI (Command Line Interface) sessions. It ensures that only authorized users can establish CLI sessions with network devices by verifying their identity before granting access.

    Click here to access the detailed Authentication Profile content and manage your network jobs effectively.

    The service provider usually gives this.

    SMTP Host Password*

    Provide the SMTP password.

    The service provider usually gives this.

    Sender Email*

    Add Sender's email address.

    Mails sent through Infraon are delivered with the specified email address as the sender.

    SMTP Host Port*

    Add SMTP host's port details.

    Use the toggle option to enable SSL or TSL encryption.

    Authentication Type

    Select the authentication type from the drop-down

    Basic Authentication and OAuth2 Microsoft. Configure SMTP with Office 365 is now seamless, requiring Client Secret, Tenant ID, Client ID, and Authority.

    Label

    Action

    Description/Example

    SMTP Hostname*

    Add the SMTP Hostname.

    The service provider usually gives this.

    SMTP Host Username*

    Label

    Action

    Description/Example

    Test

    Test the entered credentials.

    Click 'Test' to send a test mail to authenticate the configured email credentials.

    Instructions to 'Configure SMTP'

    Microsoft OAuth

    Other

    Add the SMTP Host Username.

    Audits

    Infraon records all automated and manual activities that occur within the tool and saves them as Audits.

    Audit records information of the user, the action performed, the IP address, and the time stamp when the action was performed.

    No actions can be performed from this page.

    Force Geo-Fence Restriction

    Toggle enable/disable

    Restricts users from marking attendance outside the defined radius of the work location. When enabled, attendance is allowed only within the configured geo-fence boundary. Example: User must be within 50 meters of the assigned location to mark attendance.

    Auto Clock-In / Clock-Out

    Toggle enable/disable

    Attendance validation is based on work location, and the base radius used for attendance validation is configured in the Address Book.

    Attendance Configuration

    • Attendance validation depends on the user's work location and base radius.

    • Both configuration options can be used independently or together, resulting in different attendance behaviors.

    • When geo-fence restriction is enabled, attendance marked outside the allowed radius may be flagged for approval.

    • Attendance records generated based on these settings are available in My Profile → , where users can view their check-in and check-out logs.

    • These records are also used in attendance reports and dashboard widgets for monitoring and analysis.

    Automatically records attendance when users enter or exit the defined work location. Eliminates the need for manual clock-in and clock-out actions. Example: Attendance is automatically recorded when the user reaches the office.

    Click the 'Add Profile' button

    Label

    Action

    Description/Example

    Profile Name*

    Give a name to the Business Hour Profile.

    Support Team, Main Branch, Tech Support

    Description

    Once all the parameters are added, click 'Submit' to save the profile. Business Hour Profiles can be linked to SLA, Reports, and Discovery.  Please refer to the module below for more details.

    Repeat the process to add multiple profiles. Business Profiles can be edited or deleted using the respective icons.

    Add a Business Hour Profile

    Instructions to 'Add a Business Hour Profile'

    The Alerts tab displays notifications generated by the system for events that require user attention or provide updates on system activities. Alerts help users stay informed about approvals, asset activities, SLA events, workflow updates, and other configured notifications.

    Top Panel

    Left Menu Panel

    Notification Icon

    Alerts

    What's New

    Create Knowledge Base

    Import From CSV

    The Bulk Upload feature lets you import multiple Knowledge Base articles (such as Articles, FAQ, Information, and Known Errors) via CSV files. It supports template download, data validation, and error handling for missing fields, duplicates, invalid file types, empty files, and oversized uploads.

    Step 1: Go to the Knowledge Base page and click Create Knowledge Base → Import from CSV.

    Step 2: Select the required category type, then click Download CSV File to download the empty template for preparing article data.

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

    • Title and Content must be provided.

    • Status must be either New or Published.

    • If the article is marked Private, add at least one User, Team, or User Tag.

    • Dates must follow the YYYY-MM-DD format.

    • Emails, tags, and URLs must be separated using semicolons (;).

    • Save the completed file in .csv format.

    Step 4: Upload the prepared CSV file. Map each column to the corresponding system field on the Column Matching screen, then continue.

    Step 5: The system validates all records. If there are issues—missing fields, duplicate titles, invalid file type, empty data, or oversized file—relevant error Messages are shown.

    Step 6: Download invalid records if needed. Only valid entries will be imported.

    Click Proceed with Valid Records to continue.

    Step 7: Once the import is complete, the system shows “CSV uploaded successfully.” The imported articles will be added to the Knowledge Base and can be reviewed or updated.

    Automatically attaches relevant Knowledge Base (KB) articles to response emails when incidents or requests are created from inbound . It uses AI-based similarity matching to identify and include the most relevant KB articles, helping users resolve issues faster without manual intervention.

    AI-generated Knowledge Base articles provide structured issue-resolution content based on similar incidents or requests. Users can view key details, such as the problem description, root cause, and solution, in a predefined format.

    The Knowledge Base article page displays the following sections:

    Label
    Description / Example

    Additional Information

    • AI-generated articles are automatically structured to include key sections such as problem, root cause, and solution.

    • Tags help in quick filtering and identification of similar issues.

    • To control or manage the creation of AI-generated Knowledge Base articles, refer to the module.

    Topological Links

    What you see on the screen

    Label

    Action

    Description/ Example

    Filter

    Filter can be added based on the Field and Condition from the drop-down box below.

    • Go to the Infraon Infinity page; click the Topology -> Topological Link on the left panel.

    • Navigate to Add -> Add Topology, enter the details, and click Submit.

    • Go to the Infraon Infinity page; click the Topology -> Topological Link on the left panel.

    • Navigate to Add -> CSV File

    • Download the CSV file and enter the details required.

    • Upload the same CSV file and click Next.

    Template Configuration

    The Template Configuration module allows administrators to manage and customize predefined email templates used across the Infraon 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

    Template
    Purpose
    Description/ Example

    The Allocation and Deallocation templates include a Privacy Policy option that allows administrators to include organization-specific privacy or compliance information in notification emails.

    When the Privacy Policy toggle is enabled:

    • The configured privacy policy content is displayed in allocation or deallocation emails.

    • End users can review the privacy terms before acknowledging the request.

    • Organizations can include terms, disclaimers, usage policies, or compliance-related information.

    The Allocation and Deallocation templates also support the Enable Comment Field option.

    When enabled:

    • End users must provide comments while accepting or rejecting allocation and deallocation requests.

    • The entered comments are captured in allocation reports and activity logs.

    • This helps administrators track acknowledgment details and user responses more effectively.

    Add Task

    The Add Task allows users to create a new task, assign ownership, set priority and due dates, configure recurrence, attach files, and extend the task using form templates.

    Tasks created here are immediately available in the Task list and follow the configured notification, audit, and repeat rules.

    Add Task | Field Descriptions

    Label
    Action
    Description / Example

    Trigger Configuration

    Triggers are rules or configurations that trigger an alert or an event within Infraon. Infraon allows adding of conditions to raise alerts or events when the specified rule is met.

    There are two types of trigger configurations within Infraon. They are:

    • Alerts - Alerts are based on configured thresholds (refer to Threshold module for details)

    • Correlation - Infraon correlates events based on multiple conditions to trigger an action.

    There are three steps to adding a trigger:

    Task Management

    The Task Management module allows users to create, track, and manage tasks independently or in association with ITSM records. Tasks help break down work into actionable items, assign ownership, track progress, and ensure timely completion through due dates, priorities, and notifications.

    Tasks can be created and managed directly from the Task module and are also associated with the following modules:

    This enables teams to track operational and follow-up activities linked to ITSM workflows while also supporting standalone task management.

    Task visibility and actions are role-based:

    Leaves

    Displays multiple categories of leaves available within the organization—filter information based on Leave Types or User.

    The right calendar displays leaves taken by the team for the selected period (Month/Week/Day).

    Administrators or privileged users can configure leaves, i.e., configure/allot limit or no. of leave days applicable for each category. Leaves taken by users are displayed in a calendar view with options to view week/day/list. Filters can be applied to both leave types and users.

    • Go to Infraon Configuration -> User Management -> Leave

    • Click on the 'Configure' button.

    Active users

    Active users are currently logged in and actively engaging with activities. They represent the real-time presence of people currently using the system, indicating their availability for interaction or collaboration.

    From this page:

    • You can see a list of users who are currently online.

    Add a brief description of the profile.

    Tech support team from the Head Office.

    Timezone

    Select Timezone applicable for the profile.

    Select 'Timezone' based on the team's work location. Multiple business profiles can be created to align to SLAs of multiple teams supporting multiple locations.

    Work Hours

    Use the option to select if the team works 24*7 or selected working days/hours.

    24*7 - Select exclude hours for your team.

    Select Working Days/Hours - Select weekdays, start and end times. The selected days and hours are taken as official working hours for the organization/team.

    For the 'Select Working Days/ Hours' option, there is an option to add multiple Business Hour profiles. This can define business hours on weekends (Saturday/Sunday) or other holidays.

    Exclude Hours

    Add a reason and select weekdays, start, and end times to add exclude hours.

    This can be the weekend, an official lunch hour/break time, or a change in the technician's shift.

    Use the 'Add Exclude Hours'option to add multiple instances. 'Exclude Hours'are excluded while calculating SLAs.

    Yearly Holiday List

    Add Date and Holiday Name to add a specific day as a holiday.

    To view the complete list of holidays applicable to your region, add 'Holiday' or click on import holidays.

    'Holidays'are excluded while calculating SLAs for the ticket.

    Label

    Action

    Description/Example

    Leave Type - Number of Days

    Add a number in the Number of days column of the respective leave type.

    This data must be based on the leave policy of your organization.

    Once all the details are added, click 'Update/Configure' to save. Once configured, users can see the leaves and apply for the necessary type, as required.

    What you see on the screen

    Instructions to 'Configure Leaves'

    Note: No actions can be performed from this page.

    Authorization Profile

    The Authorization Profile module defines user access levels and permissions for interacting with network devices. It ensures that only authorized users can execute specific commands or modify configurations.

    Click here to access the detailed Authorization Profile content and manage your network jobs effectively.

    Account Signup

    This module is designed for initial user registration within the Infraon 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 Infraon data, allowing registered administrators to access and utilize the various functionalities.

    Source Port

    Select from the respective drop-down box.

    Destination Node

    Select from the respective drop-down box.

    Destination Port

    Select from the respective drop-down box.

    Layer Rate

    Select the OSI (Open System Interconnection) layer.

    Direction

    Bi-directional/ Unidirectional

    Ring Name

    Select a Ring for the Topology.

    Confirm that the selected column matches and click Import.

  • Validate the CSV file and click Proceed with valid records.

  • Add

    For new topologies, you can choose the guided ’Add topology’ option or manually import data from a CSV file.

    To add a new Topology.

    Export

    Choose your export format: Download the topology as a separate CSV file or an Excel-compatible XLS file.

    To Export the configuration

    Edit

    To Edit the changes to a Topology.

    Trace Test

    Click to enter the details in the respective call-out boxes. (Link Name, Description, Source Node, Source Port, Destination Node, Destination Port, Layer Rate, Direction, Ring Name)

    It uses trace data to improve assertion capabilities and validate relationships between two nodes.

    Label

    Action/ Description

    Link Name

    Add a name for the Link.

    Description

    Provide a brief description of the topology.

    Source Node

    Instructions to add a topology

    Method 1: Manually

    Method 2: CSV File

    To Export the configuration, click on the 'Export' icon at the page’s top right corner.

    Select from the respective drop-down box.

    Solution

    Provides recommended steps to resolve the issue.Example: Update the application to the latest version, verify access permissions, clear the cache, and restart the application.

    Views / Likes / Comments

    Displays user interaction metrics, such as views, likes, and comments, for the article.

    Feedback Section

    Allows users to provide feedback on whether the article was helpful using Yes or No options.

    Comment Section

    Enables users to add comments or additional inputs related to the article.

    Tags

    Displays relevant tags associated with the issue for quick identification and search (e.g., report generation, error message, application issue).

    Problem Detail

    Provides a clear description of the user's reported issue. Example: Unable to generate reports when clicking on 'Generate Report', resulting in an error message.

    Root Cause

    Attaching KB Articles in Email to Ticket Response

    AI-Generated Knowledge Base Article

    • KB matching is restricted to the organization scope.

    • Attachments in emails (PDF, DOCX, etc.) are also processed for context.

    • Personally identifiable information (PII) is sanitized during processing.

    • The feature requires the Marketplace service to be configured.

    Feature Configuration

    Displays the identified or suggested cause of the issue. If the cause is not determined, it may appear as Unknown.

    emails

    Software change notification

    Used to notify users about software installation, updates, removal, or license-related changes.

    Ticket Escalation

    Escalated ticket notification

    Sends escalation alerts when tickets exceed the configured SLA or escalation criteria.

    Ticket Escalation Notify

    Ticket escalation update notification

    Sends additional notifications about escalated tickets to configured users or groups.

    Ticket Reassignment

    Ticket reassignment notification

    Used to notify technicians or users when a ticket is reassigned to another assignee or group.

    SLA Escalation

    SLA breach notification

    Sends alerts when ticket SLA conditions are approaching breach or have been breached.

    Allocation

    Asset allocation notification

    Used to send allocation details to end users when an asset is assigned. Includes asset details, requester details, allocation time, privacy policy, and optional comment field configuration.

    Deallocation

    Asset deallocation notification

    Used to notify users when an allocated asset is deallocated or returned. Supports privacy policy and optional acknowledgment comments.

    Hardware Changes

    Hardware change notification

    Sends notifications about hardware modifications or asset updates.

    Privacy Policy

    Comment Field

    • Click the Edit icon under the Action column to modify a template.

    • Additional rows and fields can be added using the Add Row option available in the configuration panel.

    • Changes made to templates are reflected in the corresponding notification emails sent to end users.

    Software Changes

    Title*

    Captures the task name

    Enter a short, meaningful title for the task. This helps identify the task in the list view. Example: Prepare a weekly incident report

    Status*

    Sets the current task state

    Defines the task's lifecycle stage at creation. Available options: To Do, In Progress, Done (based on workflow configuration).

    Priority

    Defines urgency level

    Indicates how critical the task is. Priority is visually highlighted in the task list. Available options: Low, Medium, High, Critical

    • Tasks support recurrence configuration, where new tasks are automatically created based on the selected repeat schedule. Each generated task is created as an independent (non-recurring) task.

    • Tasks can be extended using form templates, allowing additional custom fields to be included. Once a template is selected and the task is created, it cannot be changed.

    Trigger - Define a name and select if it is an alert or correlation.

  • Condition - Define filters and conditions.

  • Action - Select action between notifying through email/SMS or creating an incident

  • Triggers can be created for alarms, severity, asset IDs, names, etc. Ensure the trigger status is enabled to trigger the alerts/actions.

    • Go to Infraon Configuration -> Notifications -> Trigger Configuration

    • Click 'Add Trigger.'

    There are three tabs on the 'Add Trigger' page.

    Trigger | Conditions | Action

    Label

    Action

    Description/Example

    Name*

    Add a name for the trigger.

    For example, Severity trigger, Asset-based, etc.

    Trigger Type*

    Select trigger type - Alert or correlation.

    Click 'Next.'

    Trigger | Conditions| Action

    Label

    Action

    Description/Example

    Business Hour Profile*

    Select the business hour profile applicable for the trigger.

    Triggers can be configured to be generated during business hours (by selecting a business hour profile). The business hour profile must be pre-defined for this.

    Filters

    Select filters and conditions for the trigger. The' Add Condition' option can add multiple filters or conditions. Use 'And/Or' to suit requirements.

    Click 'Next'.

    Trigger | Condition | Action

    Label

    Action

    Description/Example

    Notify*

    Notify action can be used to send Email/SMS notifications or create an incident.

    Add information as requested.

    Email

    Macros | Details

    Simplify email composition for technicians by automatically inserting relevant details such as asset IP address, hostname, device type, and NCCM-specific events like job failures and configuration changes.

    This automation saves time, reduces manual errors, and ensures accurate and comprehensive notifications. Using these macros, technicians can quickly generate clear, detailed emails, improving communication and efficiently managing network configurations and changes.

    The following Macros can be availed:

    • Asset

      • IP Address

      • Hostname

      • Alias

      • Device Type

      • OS Name

      • Asset ID

      • Branch Name

      • Branch Code

    • Basic Info

      • Severity

      • Event Message

      • Timestamp

    • NCCM

      • Job Failure Reason

      • Startup Changes

      • Running Changes

    • Resource

      • Resource Type

      • Resource Name

      • Resource Tag

    Click 'Submit' to save the configuration. The respective action icon allows you to edit and delete triggers.

    To configure a Trigger

    Instructions to 'Configure a Trigger'

    When adding filters under the Conditions tab, if an alarm message is selected, the corresponding log management value fields can be incorporated. This allows users to refine the filtering criteria by associating relevant log data with alarm messages, enhancing the precision and effectiveness of log analysis.

    Infraon Admin can view and manage all tasks.

  • Other users can view:

    • Tasks created by them

    • Tasks assigned to them

    • Tasks assigned to their teams (based on workspace and team mapping)

  • The module supports task creation, inline updates, detailed editing, filtering, searching, repetitive tasks, attachments, notifications, and audit tracking.

    The Task page provides a consolidated view of tasks across modules, along with tools for searching, filtering, and managing them efficiently.

    Task View | Basic Details

    Label
    Action
    Description / Example

    Search

    Enter text to search

    Searches tasks by keywords such as Task ID, Name, or Description. Example: Searching workflow lists all tasks whose descriptions contain the word.

    Filter

    Change

    What You See on the Screen

    Attendance

    Add Change

    The "Change" module allows users to add change requests. A user is a technician who requests a change. A change could also arise from a ticket, a request, or a problem from the requester.

    Pre-requisites:

    To add a change, the following must be pre-configured

    • Requester - the user requesting the change

    • Priority - priority of the change

    • Change Manager - A Change Manager is usually a domain expert overlooking the change request.

    • Change Implementer - A Change Implementer is the user responsible for implementing the change.

    • Followers - users to be notified of the "change" status updates. Use the "Follow" button to follow directly.

    • Tags - groupings used for the classification of changes.

    • Go to the "Change" page.

    • Click on the "New Change" button.

    If requesters have been added already, select the requester's name in the search option. If no requesters have been added or to add a new requester, use the "Add a New Requester" button. Follow the "Requester" module for details. You can select or add a requester from the next page too.

    To add a change, follow the steps from the below table:

    *Emergency Change is not part of this release. It will be implemented in a future release.

    Once all details are added, the user must click "Submit as New" - to submit the change.

    • Go to "Add change"

    • Click on the select template.

    The default templates and the ability to create custom templates for planning and specific changes. Ensure seamless data integration and automation tasks for increased efficiency.

    Automated Hardware Change Notifications! Enable in feature plan, select an asset, and edit sub-category. Configure templates for custom mail notifications, including logo, keys, and menu order adjustments.

    Knowledge Base

    A Knowledge Base (KB) is a repository of information about products, services, related topics, etc., intended for self-service. KB makes it easy for users to search for solutions instead of contacting the help desk or experts for repeated/common problems. It is recommended to include articles/guides about all products and services within the organization to enable contactless, round-the-clock self-service.

    Infraon's Knowledge Base module enables users to author their articles, curate articles/guides from internal or external sources, and use, share, and manage knowledge across organizations and end-users.

    Why Knowledge Base?

    Studies conducted by Forrester and Ciboodle state that:

    • 70% of customers prefer to use a company's website to get answers to their questions rather than use phone or email.

    • An efficient knowledge base can enable customers to manage 85% of their relationship with an enterprise without interacting with humans, allowing organizations to save.

    • Organizations saw a 50% increase in Customer Satisfaction ratings through social Customer Support (Public Knowledge Base).

    An adequate Knowledge Base empowers the end user to quickly find the necessary answers and information without having to go through the hassle of waiting to get hold of an agent on call or waiting for their incident to get assigned to a Techie.

    Having said that, to get all the advantages of a Knowledge Base, it is essential to present such complicated and detailed information in a user-friendly format, which Infraon's Knowledge Base offers. Infraon's KB is designed to add quick problem-solving tips, troubleshooting guides, answers to frequently asked questions, sharing best practices through Articles, known errors, and so on in a user-friendly manner.

    A study by Coleman Parkes for Amdocs states that 91%of customers would be glad to use the available online database only if it is tailored to their needs. As easy as it may seem to build a knowledge base, it is a constant 'Work in Progress.' Follow the below steps to build an effective KB.

    CI Rule Configuration

    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.

    Asset

    The CMDB part of Infraon 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.,

    Dashboard

    Dashboards are visual representations of critical data within Infraon. They provide concise yet detailed insights into monitoring and performance metrics. Users can customize dashboards by adding relevant metrics and reports tailored to their specific needs. Dashboards can also be exported as PDFs for reporting and analysis.

    Before customizing dashboards, it is essential to understand the concept of Widgets, as these form the building blocks of every dashboard.

    Click the arrow key in the left navigation panel to expand and access multiple pre-configured dashboards. You can also hover over dashboards to reveal action icons.

    Action Icons | Dashboards

    SLA Exclusion

    SLA Exclusion is a feature that allows specific tickets to be excluded from SLA calculations through an approval-based process. Once a ticket is approved for exclusion, it is not considered in SLA metrics, breach calculations, or reports.

    The SLA Exclusion module enables users to initiate, track, and manage exclusion requests for tickets that should not be evaluated under SLA policies.

    Users can raise an by selecting one or more tickets and submitting a reason along with an approval team. The request is then reviewed by the designated team, and based on approval or rejection, the system updates the SLA applicability for the selected tickets.

    All exclusion processes are maintained in a centralized grid under SLA Exclusion, where users can monitor request status, view details, and track actions.

    The SLA Exclusion module is used to:

    Asset Types

    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.

    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.

    User Management

    User Management is part of Infraon Configuration and is accessible by administrators and authorized users. It involves managing users and defining their role and access level across modules of Infraon.

    Infraon's User Management module consists of six additional modules.

    They are:

    Users: Invite new users or edit/delete existing users.

    Roles & Privileges: Create new roles or edit/delete existing roles and define privileges for roles.

    Requesters: Create special accounts for end-users to raise Incident or Change requests.

    Teams: Create teams of users with similar skills to assign tasks to easily enable collaboration and mutual support.

    Department: Create departments, assign team members, and align them with managers.

    Password Policy:

    Hyper-Threading
  • Memory Size

  • Create a password policy to enhance security and meet compliance standards.

    My Leave: View and apply for leave of absence from work.

    Leaves: View Holiday List and leave categories as per organizational policy.

    Let's see each of these in detail. 

    Attachments added during task creation are stored with the task and can be accessed, downloaded, or removed during task updates.
  • Email notifications are triggered based on workflow configuration. When enabled, notifications are sent to the assignee, including task details and attachments.

  • Assignee

    Assigns task ownership

    Selects the user responsible for completing the task. Notifications are triggered based on workflow configuration. Example: Alex

    Due Date

    Sets task deadline

    Specifies the expected completion date. Used to track task breaches and trigger overdue notifications. Example: 2026-02-10

    Repeat

    Configures task recurrence

    Defines whether the task should repeat automatically. Available options: No Repeat, Daily, Weekly, Weekday, Monthly, Quarterly, Half-Yearly When configured, the system automatically creates new tasks based on the selected schedule. Each generated task is created as an independent (non-recurring) task.

    About Task*

    Adds detailed task description

    Provides full context and instructions using a rich text editor. Supports formatting, links, lists, and images. Example: Verify SLA breach alerts and update the report.

    Additional Information

    Extends task using templates

    Allows selection of a form template to include additional custom fields in the task. Once selected and the task is created, the template cannot be changed. If the template is updated later, the changes are reflected in the task.

    Select Template

    Loads custom form fields

    Displays available form templates created under Template → Form Template. Selecting a template dynamically adds its fields to the task form.

    Attachment

    Adds supporting files

    Allows uploading one or more files related to the task. Attachments are stored with the task and can be accessed later.

    Add (Attachment)

    Uploads files

    Opens file picker to upload attachments. Supports download and delete actions during task edit.

    Submit

    Creates the task

    Saves the task with all configured details. The task appears in the Task list, and notifications are triggered based on workflow settings.

    Cancel

    Discards task creation

    Closes the Add Task panel without saving any entered information.

    Alarm ID
  • State

  • City

  • District

  • Country

  • Parameter Value

  • Bandwidth configured

  • Link ID

  • Link Name

  • Link Mode

  • ISP Name

  • Link Bundle Name

  • Link Bundle Capacity

  • Alert triggers are based on a threshold, whereas correlations are based on multiple events correlated by Infraon.

    If you select 'Alarm Message', for 'CPU Utilization' and 'Severity' 'In' 'Critical', Infraon triggers the selected action when both these conditions are met.

    Criteria

    If selected, an email notification is sent to the configured email address.

    Add the recipient's email address (use a comma or semicolon as a separator to add multiple addresses and a subject line.

    SMS

    If selected, an SMS notification is sent to the selected user.

    Add the SMS content (Text), and select the user to be notified.

    Create a ticket

    On selecting this, Infraon creates a ticket, as configured (filters and conditions)

    Automatically creates a ticket using the defined filters and macros.

    Create Upload Job

    Enable this to auto-create an upload job after discovery

    This action automatically creates and initiates a configuration Upload Job once the trigger is activated (e.g., after a new device is discovered through ZTP).

    When enabled: The configuration is pushed to the device using pre-defined templates and runtime parameters without manual intervention.

    If not enabled: The system only discovers the device, and the technician must do the configuration push manually later.

    Create Discovery

    Enable this to auto-start the discovery of the device.

    This action triggers device discovery, which involves logging into the device (via CLI/SNMP) to gather basic inventory and validate access.

    When enabled: NCCM collects vendor, model, OS version, interface info, and other details necessary for subsequent tasks like config download or template matching.

    If not enabled: The system won’t recognize or validate the new device, and any auto-upload job or config operation might fail due to missing asset data.

    Note: Typically, the first step in automated onboarding workflows, like ZTP, is after a syslog pattern match.

    Configuration Download

    Toggle this option to download the current running configuration during discovery.

    This enables Infraon NCCM to download the live configuration from the device right after it’s discovered.

    When enabled: Ensures the system captures the current baseline state before pushing any changes. Helps compare configurations (pre/post) and supports rollback or audit.

    If not enabled: Configuration is not backed up. If the Upload Job fails or applies the wrong settings, rollback is impossible unless a prior backup exists.

    Click to apply filters

    Opens the Filter Condition panel to narrow tasks based on selected fields and conditions. Choose a task attribute to filter on. Options Include: Task ID, Name, Description, Status, Priority, Type, Assignee, and Due Date.

    Select Date Range

    Select a predefined time range

    Filters tasks based on creation or update time. Examples: Current Hour, Last 60 mins, Last Hour, Last 3 Hours.

    Add Task

    Click to create a task

    Opens the Task creation sidebar to add a new task with required details such as description, status, due date, assignee, and more.

    Task ID

    Click to view details

    Opens the Task Details sidebar for the selected task. Example: #TSK22104.

    Task Name / Description

    View or edit

    Displays the task description. Can be edited from the task details sidebar.

    Assignee

    Select or update

    Assigns the task to a user. The assignee receives notifications on task creation and updates.

    Priority

    View priority

    Displays task priority levels (e.g., Critical, Medium), helping identify urgency.

    Status

    Inline edit

    Allows quick status updates directly from the list. Example: Change from To Do → In Progress.

    Actions

    Edit

    Click

    Opens the Task Edit sidebar, allowing users to modify task details, including description, status, priority, due date, assignee, repeat configuration, attachments, and additional information. Changes are saved on submission and reflected in the task list immediately.

    Delete

    Click

    Deletes the selected task after confirmation. Once deleted, the task is permanently removed from the task list and audit logs capture the deletion action.

    Gather

    Optimize

    Monitor

    Re-Organize

    Collect only necessary, helpful, and relevant information. Include both internal and external services offered by the organization.

    Use Infraon's Incident to KB option or create a KB (article/FAQ etc.) directly.

    Keep your content easy to understand and searchable. Ensure that your knowledge base is seamless to navigate through.

    Add relevant tags to each KB article/documentation and keep the instructions simple and user-friendly.

    Monitor and observe entered keywords, understand the usage of your end customer, and use them to enhance User Experience.

    Tune your data and clean up your database regularly. Help customers find the information they are looking for effortlessly.

    Delete/archive old articles and keep your KB clutter-free.

    How to build an effective Knowledge Base?

    User Rule

    User's first login

    User(s) can self-register on Infraon when they receive an invitation from the administrator(s). Click on the link, add details, and Voila! You are all set.

    Please note that your Administrator/Manager has predefined your role-based privileges.

    Please contact your administrator or manager if you cannot view any Infraon modules/pages.

    When you first log in, Infraon offers options to customize your theme.

    Reporters are users raising the change on behalf of the requester.

    Change Manager

    Select a Change Manager from the list.

    A change manager overlooks the change analysis and implementation.

    Change Implementer

    Select the change implementer from the list.

    A change implementer can be a user or a team responsible for implementing the change.

    Impact Service

    Select the Impact Service from the list.

    This can be left blank. As the risk analysis progresses, the technicians can later select the impacted service.

    Service Classification

    Select the classification within the impacted service.

    This is used when a specific service has multiple classifications. For example, if the impacted service is Network, the classifications can be connectivity, router issue, and so on. Leave this field blank if no classifications are defined.

    Followers

    Select a user to add them as followers.

    Users who must be notified of the change request or any changes to the status of the change request can be added as followers. Use the 'Follow' option to self-follow the change request.

    Tags

    Select a tag to tag the change.

    These tags must be predefined in the 'General Settings -> Tag Management module.

    Subject

    Add a subject line for the change.

    The subject line can be a summary of the change. For example: Unable to connect to the network.

    Description

    Provide a brief description of the change.

    Due By

    It is the due date by which a team aims to implement the change.

    Priority

    Select the priority of the change from the list.

    Risk

    Select the risk level from the list.

    Change Type

    Select the type of Change from the list.

    The changes can be of four types:

    Standard Change

    Major Change

    Minor Change

    *Emergency Change

    Reason for Change

    Specify the reason for requesting the change.

    Add attachments

    Use the action icon to add an attachment to the change.

    Attachments can include emails, screenshots, etc.

    Rollout

    Specify the plan to rollout the change.

    Leave this field blank if the rollout plan is not yet decided.

    Rollback

    Specify the plan to rollback the changes.

    Leave this field blank if the rollback plan is not yet decided.

    Label

    Action

    Description/Example

    Requester*

    Add a new requester or search for an existing requester.

    Requesters are usually technicians or users with the required permissions who can add a change.

    Reported by

    Instructions to add a Change

    Note: When the requester's name is added, Infraon displays the list of past interactions the requester has had. Click on the Change ID to view the details.

    Custom Change template creation.

    E-mail alerts on asset hardware changes

    Use the icon to expand this section. Add the reporter's name and email address, if applicable.

    Refer to the Asset Grid Page and Asset Categories/Sub-Categories 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.

    Note: Assets can be added at the category and sub-category levels. Regardless of the asset type, the steps to view, add, edit, and manage assets are the same.

    Steps to Look for a Specific Asset

    Label

    Action

    Description / Example

    Configure Presentation

    Click to configure

    Enable Dashboard Presentation Mode. Select the dashboard and set time intervals (10–300 seconds) for automated rotation. This mode is useful for displaying dynamic assets or performance boards.

    Add

    Click to perform

    Add a new custom dashboard.

    Pin

    Click to perform

    Pin a dashboard to the top for quick access.

    Edit

    Click to perform

    Modify or update the selected dashboard.

    Clone

    Click to perform

    Duplicate the selected dashboard for reuse.

    Delete

    Click to perform

    Remove the selected dashboard permanently.

    Infraon provides three pre-configured dashboards during platform onboarding. These serve as ready-to-use examples to help users understand dashboard functionality and layout.

    Each dashboard contains dynamic widgets that auto-refresh based on the selected refresh interval. Widgets are clickable, allowing users to drill down and view complete details of the underlying data. Additionally, users can download the displayed data in CSV format for further analysis for specific widgets.

    It enables organizations to manage asset lifecycles effectively, track expenses, and plan budgets proactively. The Asset Summary Dashboard delivers a comprehensive overview of IT and fixed assets, including purchase trends, financial summaries, vendor information, and asset distribution by value and location.

    Widget Name

    Description

    Use Case

    Assets by Value

    Displays asset distribution based on their monetary value.

    Helps in financial tracking of IT and non-IT assets.

    New Purchases (Current Quarter)

    Access to view and customize dashboards is controlled by role-based privileges that the administrator must enable. Access can be managed at both the User and User Group levels.

    What You See on the Screen

    Pre-configured Dashboards

    Asset Summary

    Exclude tickets that are not valid for SLA evaluation (e.g., external delays, dependencies, or exceptions).
  • Ensure accurate SLA reporting by removing irrelevant tickets from calculations.

  • Provide a controlled and auditable process through approval workflows.

  • Maintain data integrity across SLA dashboards, reports, and metrics.

  • Enable traceability with audit logs for all exclusion actions.

  • The SLA Exclusion page displays all exclusion requests in a grid view. Users can view details such as reason, status, team, and creation information. Each record can be accessed to view or manage the exclusion process.

    SLA Exclusion | Basic Details

    Label
    Action
    Description / Example

    Display ID

    Click

    Unique identifier of the exclusion process. Click to open the detailed view. Example: EXCL0009

    Reason for Exclusion

    View

    When a record is opened:

    • Displays complete details of the exclusion request along with linked tickets.

    • The approver can review and approve the request if it is in Pending Approval state.

    • Once approved, the status is updated to Exclusion Accepted.

    • If already approved, the page displays the status as Exclusion Accepted without further action.

    How does it work?

    Purpose of the Module

    What you see on the screen

    View/ Edit Exclusion

    Exclusion Request
    GenAI

    Asset Grid Page

    There is no single home page for Assets. Assets are added based on the asset type, each with a grid page. Click on the respective asset type from the left panel to view the list of assets in the selected category. This page is referred to as the 'Asset Grid Page'.

    Assets can be viewed as a card or a grid view. Asset details include the following information.

    • Asset Name

    • IP Address

    • Asset Category

    • Asset ID

    • Asset Status

    • Device Type

    • Make

    There are three ways to search for an asset.

    • Barcode Search - Click the Scan & Search Asset icon and scan the barcode using a barcode scanner. The corresponding asset information is displayed automatically.

    • QR Code: Users can generate, print, and scan QR codes for assets to quickly access asset-related information.

    • Asset Search - Click the 'Scan & Search Asset' icon and type the asset ID to search.

    Users can customize the information displayed when a QR code is scanned by selecting which asset fields to include in the QR data.

    To customize QR code fields:

    • Navigate to the required Asset module page.

    • Click Actions.

    • Select Customize QR Columns.

    • Choose the fields to be displayed in the QR scan result.

    • Click:

      • Submit – Applies the configuration for newly generated QR codes.

      • Submit & Overwrite – Regenerates QR codes for existing assets with the updated configuration.

    The customization supports:

    • Standard asset fields

    • Custom fields such as:

    • Text

    • Number

    Additionally:

    • A maximum of 6 fields can be selected for QR display.

    • Updated asset values are automatically reflected in QR scan results after regeneration.

    • Printed and bulk-generated QR codes maintain the configured field information.

    • Asset ID changes are reflected in QR data when Asset ID customization is enabled.

    Users can scan the generated QR codes using:

    • Mobile device camera scanners

    • Third-party QR scanner applications

    • QR scanning applications available on Google Play Store

    When scanned, the QR code displays the configured asset information based on the selected QR columns.

    Customize columns based on unique preferences. Arrange columns effortlessly with a simple drag-and-drop action, streamlining the experience for optimal efficiency and organization.

    Select one or more assets to view the asset actions below:

    • Owner - Click to add/change asset owner.

    • Requester - Click to update the requester and/or owner.

    • Tag - Click to update the asset tag.

    • Print - Click to print the asset label(s).

    Enhanced Software Management! Now, easily sort asset ID, name, operational status, and overall status in ascending or descending order while adding software.

    Kafka Connection

    The Kafka Connection module allows users to configure and manage connections to external Kafka brokers. These connections are used to publish data from Infraon workflows to Kafka topics.

    This module serves as the foundation for Kafka-based integrations, enabling workflow events to trigger real-time data publishing to external systems.

    • List of configured Kafka connections

    • Columns:

    Category Template

    The Category Template allows IT admins to predefine metadata fields, default behaviours, and automation logic for various asset categories. It acts as a blueprint that ensures asset records are consistent, enriched with required fields, and easily mapped during asset onboarding or discovery.

    It is used to:

    • Apply default settings like location, ownership, and asset ID.

    • Choose which field groups (like Procurement or OS details) should appear when creating assets.

    My Leaves

    Displays leave details of the logged-in user. Users can view multiple categories of leaves available within the organization, apply for leave and check available leave balance as on date.

    Leave categories with information on the number of leaves available vs. the number of leaves taken.

    Use the 'Apply Leave(s)' button to apply for leave(s). Select date or date range, leave type, and specify a reason. Click 'Apply.'

    Leave Type must be pre-defined by the administrator.

    • Go to Infraon Configuration -> User Management -> Leaves

    • Click on the Apply Leave(s) button.

    Shows assets purchased in the current quarter.

    Useful for budgeting and procurement reviews.

    Upcoming Expenses (Next Quarter)

    Projects upcoming financial commitments for assets.

    Helps plan budgets and avoid surprise expenses.

    IT Asset Summary

    Lists IT assets with key details (type, category, ownership).

    Helps IT teams maintain inventory accuracy.

    Fixed Asset Summary

    Displays details of fixed/long-term assets.

    Supports audits and compliance checks.

    Vendor Summary

    Shows vendor details and associated assets.

    Helps manage vendor performance and procurement contracts.

    Current Year Purchase

    Summarizes all purchases made in the current year.

    Provides annual procurement insights.

    Agent Summary

    Shows workload and asset-related activities of agents.

    Useful to monitor asset-related responsibilities of staff.

    Asset Location Drilldown Table

    Displays asset details by physical location.

    Helps track distributed asset ownership.

    Asset Summary

    General overview of assets within the system.

    Provides quick visibility into total inventory.

    Location-wise Asset Summary

    Breaks down assets based on location.

    /Displays a location-wise count of assets on the dashboard, helping users quickly view asset distribution, track inventory, and manage resources efficiently.

    Infraon Automation

    Infraon Automation is part of Infraon Configuration and contains configurations that can automate features, processes, and activities within Infraon.

    This module of Infraon consists of the following:

    Mail Automator: Configure IMAP mail accounts on infraon and refer guides to forward your existing emails to Infraon to convert emails into tickets.

    Workflow: Visualize and create a process flow involving specific activities in the selected module.

    Business Rule : Defines the business rule for the Infraon system for auto assignment of tickets.

    Escalation: Defines the escalations process and automatic assignment mechanism are employed in support ticket resolution.

    Customer feedback templates: Customize templates to collect feedback to improve service quality and customer experience.

    Let's see each of these in detail.

    Filter - Click on the 'Search Filter' field and type the name, asset ID, hostname, IP address, or category/sub-category to search.
    Email
  • Phone fields

  • QR regeneration activities are recorded in audit logs and asset history.

    More - Click to update asset status and location, enable, disable, or delete the asset.

  • The asset(s) must be in an 'enabled' state for editing.

  • Asset Search/Scan

    QR Code Customization

    Assets column selection

    Asset Actions

    Sorting drop-down feature for Asset card view page

    Name – Identifier of the Kafka connection
  • Bootstrap Servers – Kafka broker endpoint(s)

  • Security Protocol – Connection type (e.g., SASL, SSL)

  • Status – Active / Inactive

  • Creation Time – Timestamp of creation

  • Action – Edit / Delete options

  • Add the Kafka Connection button to create a new connection

    1. A Kafka connection is created by providing:

    • Broker details (Bootstrap Servers)

    • Security configuration (SSL, SASL, etc.)

    • Authentication credentials (if required)

    1. The connection can be:

    • Tested to verify connectivity

    • Activated or deactivated

    1. Once active, the connection becomes available in the Workflow module.

    2. In workflows:

    • A Kafka Integration action is added

    • The user selects the Kafka connection

    • Available topics are fetched dynamically

    1. When the workflow is executed:

    • Data is published to the selected Kafka topic(s)

    • External systems consume this data

    1. System tracks:

    • Success or failure of message publishing

    • Logs in workflow execution and recent activities

    • To create a new Kafka connection, click Add Kafka Connection located at the top right corner of the page.

    • This opens the Add Kafka Connection panel, where you can configure broker details, security settings, and authentication required to establish communication with the Kafka cluster.

    Configuration Details | Kafka Connection

    Label
    Action
    Description / Example

    Connection Name *

    Enter value

    Specify a unique and identifiable name for the Kafka connection. Example: Ticket_Event_Stream, Production_Kafka

    Brokers *

    Enter value

    The fields displayed in the configuration form change dynamically based on the selected Security Type. This ensures that only relevant authentication details are required.

    Field Behavior | Security Type

    Security Type
    Additional Fields
    Description

    None

    None

    No authentication or encryption is applied. The connection is established without any security layer. Suitable only for trusted internal environments without enforced security.

    Plaintext

    None

    • Click Test to validate the Kafka connection using the provided configuration details. The system attempts to establish a connection with the Kafka broker and verifies credentials, security settings, and network accessibility.

    • Click Save to store the Kafka connection configuration. Once saved:

      • The connection becomes available in workflow actions (if marked Active)

      • It can be selected in the Kafka Integration workflow card

      • Configuration changes are tracked in audit logs

    What you see on the screen

    How does it work

    • Only active Kafka connections are available for workflow usage

    • Supports multiple security protocols (SSL, SASL, etc.)

    • Enables event-driven data publishing from workflows

    Add Kafka Connection

    On success: A confirmation message is displayed

    On failure: An error message is shown with details for troubleshooting

    • It is recommended to Test the connection before saving

    • Only Active connections are available in the workflow configuration

    • Internal Kafka topics (e.g., consumer_offsets) are automatically excluded

    Simplify asset management through structured, pre-configured templates.

    The template configuration is split into two tabs:

    1. Basic Details

    2. Fields

    This section allows administrators to configure behavior-based options for the asset category.

    Label

    Action

    Description / Example

    Notify End Users on Asset Allocation

    Click the toggle to enable

    Sends a notification to the end user when an asset is allocated. User can Accept/Deny the asset.

    Notify End Users on Asset De-allocation

    This tab allows you to define which metadata sections should appear when assets of this category are created or imported.

    These fields correspond to the ones described under Asset Categories & Sub-Categories and are grouped as follows:

    • Common Properties (e.g., Hostname, IP, Serial Number)

    • Cost Properties (e.g., Book Value, Estimated Cost)

    • Procurement Properties (e.g., Warranty, AMC details)

    • Assignment (e.g., Owner, Requester, Allocation details)

    • OS Properties (e.g., OS Name, Product Key, Version)

    Admins can:

    • Select or deselect which sections to include in the template.

    • View or modify the fields inside each group by clicking Show Fields.

    • Create Custom Fields to accommodate organization-specific needs.

    Basic Details

    Once added, click on Next.

    Fields

    • Once a template is configured, it automatically applies when creating assets under that category.

    • Multiple templates can be created to match the structure of workstations, servers, SaaS tools, or custom asset types.

    • Custom fields are fully supported for CSV imports and asset discovery.

    Label

    Action

    Description/Example

    Leave Date*

    Choose a date or range of dates you want to apply for leave.

    Leave days are auto-calculated based on the selection.

    Leave Type

    Select leave type using the dropdown menu.

    Click 'Submit.' Leave requests are submitted to the reporting manager for approval. Users can edit leave requests as long as they are not approved.

    What you see on screen

    Instructions to 'Apply Leave'

    Displays the justification provided for excluding the tickets from SLA. Example: Excluding SLA

    Status

    View

    Shows the current state of the exclusion request. Example: Pending Approval / Exclusion Accepted

    Team

    View

    Displays the team assigned to approve the exclusion request. Example: SLA Exclusion

    Created By

    View

    Name of the user who created the exclusion request.

    Creation Date

    View

    Date and time when the exclusion request was created. Example: Feb 13, 2026 09:55 AM

    Actions

    Edit / View

    Use the action icon to open the exclusion details page for the selected record.

    SSP Configuration

    The SSP (Self-Service Portal) Configuration module, exclusive to Infraon Management Admins, empowers admins to customize their end-users (SSP) experience.

    Configure SSP

    Use the toggle buttons for each module to determine which options appear as menu items on the SSP portal's top panel.

    This allows admins to tailor end-user functionality to your organization's needs.

    From this central location, admins can control the visibility (by enabling the toggle buttons) of various modules within the SSP (located at the top panel).

    The following section breaks down the details:

    Home

    The Home section allows Infraon Management Admins to customize the appearance and content of the Self-Service Portal (SSP) Home page. Administrators can configure the Home page layout, customize the banner, and control which shortcuts and Quick Access sections are displayed to end users.

    To configure the Home page:

    • Navigate to Infraon Platform > SSP Configuration.

    • Enable the Home toggle.

    • Configure the required settings.

    • Save the changes.

    Select the preferred Home page layout for the Self-Service Portal.

    The available designs are:

    • Old Design

    • New Design

    The selected design determines which Quick Help and Services options are displayed on the Home page.

    Option
    Description

    The Banner Title defines the title displayed at the top of the SSP Home page.

    Field
    Description

    The Banner Subtitle is available only when New Design is selected.

    Field
    Description
    • The Quick Help and Services section allows administrators to choose which shortcuts are displayed on the SSP Home page.

    • Only the selected shortcuts are shown to end users.

    • If all options are removed, the Quick Help and Services section is hidden from the SSP Home page.

    The following shortcuts are available for the Old Design layout.

    Option
    Description

    The following shortcuts are available for the New Design layout.

    Option
    Description

    The Quick Access section allows administrators to configure which expandable sections are displayed on the SSP Home page.

    Users can quickly access frequently used information directly from the Home page.

    The available options are listed below.

    Option
    Description

    After configuration, the selected sections are displayed on the SSP Home page.

    Password Policy

    Passwords are mandatory to verify user identity (authentication) and protect information. Therefore, it is crucial to have more robust password policies across the Organization.

    Infraon can be configured with multiple Password Policies to suit the organization's internal and external compliance. Different password policies can be configured for various roles.

    What you see on the screen

    The Password Policy page can create new policies and edit and delete existing ones.

    Instructions to 'Add a Password Policy'

    • Go to Infraon Configuration -> User Management -> Password Policy

    • Click the 'Add' button.

    There are two tabs on the 'Add Password Policy' page.

    The Policy Details tab contains options to customize passwords, including Password Length, Upper/Lower Case, Numbers, Symbols, and Frequency to Change Password. The applicability tab lets the user choose the policy's privacy level.

    Policy Details | Applicability

    Fields marked with * are mandatory.

    Click 'Next' to configure the password policy's applicability.

    Policy Details | Applicability

    Fields marked with * are mandatory.

    Once all the parameters are added, click 'Submit' to save the password policy. Password policies can be linked to newer roles.

    Administrators and privileged users can edit and delete policies using the respective icons.

    The default password policy cannot be deleted.

    Topology

    Topology View

    Topology refers to how various nodes, devices, and connections on your network are physically or logically arranged in relation to each other. Topology View displays the complete topology of all the connected devices in the network. The connections are configured to change colours automatically based on the faults or thresholds.

    Node:

    Clicking on the node shows the inventory details about the selected node.

    Node Devices:

    • SDH MUX

    • Routers

    • SDH EMS Firewall

    • PDH MUX

    On the right click of the node, it shows the Device View, Active Events, and Services.

    Below are the details which can be viewed:

    • Host Name

    • IP Address

    • Make

    • Model

    The colours on the Node indicate the status of the device, which depends on the severity of the operation.

    Blue -> Grey -> Green -> Yellow -> Orange -> Red -> Dark Red

    (Green for Up, Red for Down, and Grey for Disabled devices).

    Clicking on the edge shows the connection details and the current performance parameters between the connected nodes, depending on the type.

    Below are the details which can be viewed:

    • Description

    • Source IP

    • Source Device

    • Source Port

    Events

    Infraon detects all changes or activities of CIs or configuration items, observes anomalies based on the configured thresholds, and records them as events. If triggers are configured for the same, notifications or incidents are raised accordingly.

    How does it work?

    Infraon is configured with built-in thresholds for all the monitoring nodes and their components. Infraon monitors the assets constantly. It detects threshold breaches and records them as events. If any thresholds, devices, or metrics are linked in a trigger, Infraon either triggers a notification or converts the event to an Incident.

    What you see on the screen

    The events page lists all events - Issue, Date, Node, Resource, and Event ID, sorted by time. Events have default filters like:

    • Critical, Major, and Minor - based on the threshold

    • Acknowledged and Ticketed - based on the action

    • Priority - based on the asset property

    • Root - based on the correlation

    • NCCM – This shows events focused exclusively on the NCCM module, including download jobs and configuration changes. By applying this filter, technicians can focus on network configuration and change management activities, making monitoring and addressing NCCM-related issues easier.

    Each event allows the below actions (Quick action tool):

    Events can be filtered by dates or downloaded using the respective icons.

    Overview

    The Infraon Admin Guide is explicitly designed for administrators responsible for configuring, managing, and maintaining the Infraon 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.

    Add Asset/Add Item

    Assets are referred to as Items in Infraon. Before adding an asset, the category and subcategory must be defined.

    Navigate to the respective Asset page (IT, fixed, consumables, etc.). If no categories/subcategories are pre-defined, these can be added when adding the asset (item).

    There are three ways to add assets:

    1. Single Asset - You can add a single asset from the drop-down menu in the top right corner

    2. Import from CSV - If you have the asset CSV file, you can import it from the drop-down menu in the top right corner.

    Auto Ticket Assigning till Group Level

    The Infraon platform automates ticket assignment not only at the technician level but also at the group level, based on Business Rules.

    • Tickets can be automatically assigned to a designated group based on defined conditions such as:

      • Category

      • Priority

    Download Job

    Download Job refers to a task that involves retrieving configuration files from network devices such as routers, switches, firewalls, and others and storing them centrally within the system.

    to access the detailed Download Job content and manage your network jobs effectively.

    Leave type must be pre-configured by the administrator.

    Reason*

    Add a reason for leave.

    The reason is a mandatory field.

    Where can I view the full product documentation?

    User Guide
    User Guide
    Click here

    Upload Jobs

    Upload jobs involve changing or updating configuration files or firmware from the Infraon NCCM server to network devices. They're commonly used for deploying new devices, updating existing ones, and upgrading device firmware. For instance, users can simultaneously upload entire configuration files or specific snippets to individual or multiple devices.

    Click here to access the detailed Upload Job content and manage your network jobs effectively.

    Click the toggle to enable

    Sends a notification to the end user when the asset is de-allocated.

    Customize Asset ID

    Click the toggle to enable

    Allows customization of asset IDs as per customer-defined formats. Helps ensure traceability and compliance with internal tagging rules. Example: #ESOL-D-0038.

    Note: Common categories must include the "Customized Asset Id" field for this to work.

    Select default asset location

    Select from the dropdown list

    Automatically assigns a default location when an asset of this category is created or discovered.

    Example: Head Office – Bengaluru.

    Select default asset Owner/Technician

    Select user(s) from dropdown

    Assigns a default owner or technician to assets created under this category.

    View Change

    Displays the View Change shortcut.

    Submit Ticket

    Displays the Submit Ticket shortcut.

    Assets

    Displays the Assets shortcut.

    Service Catalogue

    Displays the Service Catalog shortcut.

    View Requests

    Displays the View Requests shortcut.

    Workspace

    Displays the Workspace shortcut.

    Browse Articles

    Displays the Browse Articles shortcut.

    View Change

    Displays the View Change shortcut.

    Hardware & Devices

    Displays the Hardware & Devices shortcut.

    Trending Articles

    Displays the Trending Articles section.

    Service Catalogues

    Displays the Service Catalogues section.

    Old Design

    Displays the classic SSP Home page layout.

    New Design

    Displays the redesigned SSP Home page with additional configuration options, including the Banner Sub-title and updated Quick Help options.

    Banner Title

    Enter the title to display on the SSP Home page banner.

    Banner Sub-title

    Enter the subtitle to display below the Banner Title on the SSP Home page. Available only for the New Design layout.

    Browse Articles

    Displays the Browse Articles shortcut.

    View Tickets

    Displays the View Tickets shortcut.

    View Requests

    View Tickets

    Displays the View Tickets shortcut.

    Submit Ticket

    Displays the Submit Ticket shortcut.

    Assets

    Active Tickets

    Displays the Active Tickets section.

    Active Requests

    Displays the Active Requests section.

    Assets

    Home Design

    Banner Title

    If no custom title is specified, the portal displays the default banner title.

    Banner Sub-title

    Use this field to display additional descriptive text below the Banner Title.

    The Banner Subtitle is displayed only when the New Design layout is selected.

    Quick Help and Services

    Old Design

    New Design

    The available Quick Help options vary depending on the selected Home page design.

    Quick Access

    If all Quick Access options are removed, the SSP Home page displays the default Quick Access sections.

    self-service portal

    Displays the View Requests shortcut.

    Displays the Assets shortcut.

    Displays the Assets section.

    Assign to the external vendor team; This is for requesters only.

    Change Password Every N Day(s)

    Enter the number of days until the password needs to be changed.

    Users are reminded to change their passwords every (n) day by Infraon.

    Last-Used Password Count

    Enter the count of last used passwords that are considered for non-repetition.

    If the number '4' is entered, Infraon will not enable users to use the previous four passwords when changing or resetting their passwords.

    Minimum Password Length

    Enter the minimum number of characters for the password length.

    If the minimum password length is set to '8', Infraon will only accept passwords at least eight characters long.

    Maximum Password Length

    Enter the Maximum number of characters for the password length.

    If the maximum password length is set to '20', Infraon will only accept passwords less than twenty characters long.

    Minimum Upper Case Characters

    Enter the minimum amount of uppercase or capital letter characters required in the password.

    If the minimum upper case character length is set to '2', Infraon will only accept passwords with two uppercase characters (neither one nor more than two).

    Minimum Lower Case Characters

    Enter the minimum amount of lowercase or minor letter characters required in the password.

    If the minimum lower case character length is set to '2', Infraon will only accept passwords with two lowercase characters.

    Minimum Numerals

    Enter the minimum amount of numerals or numeric characters required in the password.

    If the minimum numerals are set to '2', Infraon will only accept passwords with two digits (neither one nor more than two).

    Minimum Special Characters

    Enter the minimum amount of special characters required in the password.

    If the minimum unique character is set to '2', Infraon will only accept passwords with two special characters (neither one nor more than two). Special characters include

    Continuous N Upper Case Characters

    Enter the count of continuous upper case characters allowed in the password sequence.

    If the continuous upper case character is set to 1, Infraon will not allow more than one upper case character in the password sequence.

    For example, Eims would be accepted, whereas EIMS would not.

    Continuous N Lower Case Characters

    Enter the count of continuous upper case characters allowed in the password sequence.

    If the continuous lower case character is set to 3, Infraon will not allow more than three lower case characters in the password sequence.

    For example, Eims would be accepted, whereas eims would not.

    Continuous N Numerals

    Enter the count of continuous numerals or number characters allowed in the password sequence.

    If the continuous numeric character is set to 3, Infraon will not allow more than three numeric characters in the password sequence.

    For example, Eims123 would be accepted, whereas Eims1234 would not.

    Continuous N Special Characters

    Enter the count of special characters allowed in the password sequence.

    If the continuous unique character is set to 2, Infraon will not allow more than two special characters in the password sequence.

    For example, Eims@123! would be accepted, whereas Eim$@1234 would not.

    Label

    Action

    Description/Example

    Policy Name*

    Give a name to the password policy.

    Vendor Team, Requesters Only.

    Description*

    Label

    Action

    Description/Example

    Roles

    Select a role to apply the password policy.

    Vendor Team, Requesters.

    Roles must be pre-defined to be available for selection.

    Note: Password policies must be de-linked from roles to be deleted.

    Add a brief description of the policy.

    Device Type
  • EMS Name

  • Firmware Version

  • Region

  • State

  • City

  • Location

  • Destination Ip
  • Destination Device

  • Destination Port

  • Layer Rate

  • Active Events (Click to redirect to the Active Events page)

  • Services (Click to redirect to the Services page)

  • Profile

    Locate a Profile from the selected drop-down box.

    Vendors

    Locate a Vendor from the selected drop-down box.

    Stop Auto Reload

    Click to Stop (Default is Auto).

    It reloads the topology view at every interval of 60 seconds.

    Export

    Creates a PDF of the current topology view.

    Edit

    To save a new topology profile or a new topology view. Drag nodes to adjust the view.

    Arrows Key

    Icons can be used to navigate through the topology diagram.

    Zoom Key

    Icons can be used to navigate through the topology diagram.

    Label

    Action

    Description/ Example

    Filter

    Filter can be added based on the City and Condition from the drop-down box below.

    Locate Node

    Properties

    Edge:

    What you see on the screen

    Note: The thickness of the interface indicates the offered Bandwidth.

    Locate a Node from the drop-down. Select the No. of hops, using the drop-down menu. The selected number of neighbors will be displayed.

    Used to acknowledge the event. NOC users or technicians can acknowledge and add a comment to let other users know they are working on it. 

    Diagnosis  

    Used to perform active diagnosis.  Diagnosis can be performed using Ping, SNMP Walk, and Trace Route. 

    Ticket 

    Used to create an incident for the event. 

    Clear 

    Used to clear the event. Cleared events can be viewed using the 'Show History' toggle button. 

    Activity Log 

    Used to view the event history. 

    Label 

    Action 

    Description/ Example 

    Analyse 

    Click to view the ‘Impact Services’ event details. 

    Click on the ‘More Details’ button to be redirected to the event page. 

    Includes details to help analyse the event. User can view the asset details and the statistics of what the current event is performing. 

    Acknowledge 

    Location

  • Ensures workload distribution across groups without requiring manual assignment.

    • Within a group, tickets can be routed to a subgroup or specific member based on additional filters like:

      • Expertise

      • Workload capacity

    • Provided for targeted allocation while still using the business rule framework.

    • Administrators can configure rules for both group and subgroup levels.

    • Rules can be modified dynamically without affecting ongoing tickets.

    • All rule-based assignments are logged in the system.

    • Provides transparency with detailed tracking of:

      • Business rule executions

      • Group/subgroup assignment logs

    1. Group-Level Assignment

    2. Sub-Level (Selective) Assignment

    3. Customization and Configuration

    Example: All “High Priority Network Issues” can be directly routed to the “Network Operations Group”.

    4. Audit and Tracking

    Provides audit logs for connection changes

  • Ensures validation and error handling during execution

  • All create, update, and delete actions are recorded in Audit Logs

    Enter the Kafka broker endpoint(s) in “host: port” format. These brokers act as entry points to the Kafka cluster and are used to establish the connection. Multiple brokers can be provided (comma-separated) to ensure high availability and fault tolerance. Example: 192.168.1.10:9092, kafka-prod:9092

    Status

    Toggle on/off

    Enables or disables the Kafka connection. When enabled (Active), the connection becomes available for selection in workflow actions. When disabled (Inactive), it is hidden from workflow configuration but remains saved in the system.

    Security Type *

    Select option

    Defines the communication protocol and authentication mechanism used to connect with the Kafka cluster. This selection dynamically controls which additional fields are required (such as credentials or certificates). Available options include:

    • None

    • Plaintext

    • SASL (Plaintext)

    • SSL

    • SASL (SSL)

    Similar to “None”, but explicitly indicates communication over an unencrypted channel. Data is transmitted as plain text without encryption or authentication.

    SSL

    Certificate

    Enables encrypted communication between Infraon and Kafka using SSL/TLS. A valid certificate key must be provided to establish a secure connection. No username/password authentication is required.

    SASL (Plaintext)

    Username, Password

    Enables SASL-based authentication without encryption. Credentials are required to authenticate with the Kafka broker, but communication is not encrypted.

    SASL (SSL)

    Username, Password, Certificate

    Provides both authentication and encryption. Requires valid credentials (username/password) along with an SSL certificate. This is the most secure option and recommended for production environments.

    Add Assets through Discovery - This only applies to IT assets. Any asset with an IP can be discovered using agent-based discovery. Refer to the 'Discovery' section for details.

    • Go to Asset -> Asset Type.

    • Click the 'Add' button -> Single Asset.

    There are two tabs on the 'Add Asset' page. Refer to the table for information.

    Define Asset | Details

    Label

    Action

    Description/Example

    Asset Name*

    Add your asset name.

    Asset names can be server, host, computer, device, etc.

    Category

    * Upload images if you have product images.

    Click 'Next' to add 'Asset Properties.'

    Please refer to the previously mentioned asset properties, which are located in the 'Add asset Categories' section.

    Upon clicking on the added assets, icons appear at the top, including the owner, requester, tag, print, and additional options.

    Two sections will be displayed on this page when clicking on the asset.

    • Asset name: This section displays the asset name, IP address, and status. The status can be modified to Trial run, in use, Maintenance, Parts repairs, Accident/failure, Audit, or Lost. To add the requester's location and allocation details, click "more options."

    • Sections: On the left side of the page, there are seven sections represented by tabs; clicking on these tabs will display specific data on the right side of the page. These sections include:

      • Details: If an asset picture has been uploaded, the details section will display it. It displays essential details such as hostname, device type, asset status, Asset ID, barcode, IP address, QR code, make, and OS name.

        • Performance section: System uptime, CPU utilization, memory, and Disk is displayed.

        • Attachment: Attachments can be added by clicking the 'add' button and uploading a CSV file.

        • Details: Assets such as Alias, Asset Name, IP Version, and Model are displayed.

        • Owner: Owner details such as name, e-mail, and phone number are displayed.

    • Asset Lifecycle: The asset life cycle refers to the stages that an asset goes through, from its acquisition to retirement, encompassing its management, maintenance, and utilization throughout its entire existence.

    • Hardware: Any hardware components collectively enable the device to function and perform specific tasks.

    • Events: Infraon detects all changes or activities of CIs or configuration items, observes anomalies based on the configured thresholds, and records them as events. If triggers are configured for the same, notifications or incidents are raised accordingly.

    Enable the events menu on the asset summary page to display Windows events, and CI will enable the asset options.

    The event Page Module is now enabled on the Asset page. It allows access to login/logout history and detailed event data. It also allows you to analyze key information like domain name, login type, machine name, and system details, including IP addresses. To enable it, visit the Event Page settings, choose 'Show History' for universal events, or select specific asset events from the asset page for targeted insights.

    Following are the sections within the 'Asset properties' tab:

    • Sections

    • Show Only Mandatory button.

    • Back

    • Submit

    Label

    Description/Example

    Sections

    Under sections, you can find various asset properties. If your assets have more than one property, you can select multiple properties and fill in the details in the left section.

    Show Only Mandatory Button

    When you toggle the show only mandatory button, you will get only the hardware properties, and you need to fill in only those details.

    Back Button

    • Go to Asset -> Asset Type

    • Click the 'Add' button -> Import from CSV

    In the 'Import from CSV,' there are two tabs:

    Upload | Details

    Label

    Action

    Description/Example

    Category*

    Select asset category using the drop-down menu.

    Server, Fans, etc. Download the sample CSV file and add details accordingly.

    Import Asset List from CSV*

    You can either drag and drop the file or browse to upload the CSV file.

    Click 'Next' to continue with column matching.

    Column Matching | Details

    Once the column matching is completed, click 'Import' to import your asset CSV file for asset management.

    Asset information is imported from the CSV to the respective category on Infraon. Asset information can be viewed, edited, or deleted using the respective action icon.

    Note: Refer to the Asset Categories/Sub-Categories section for more information.

    Instructions to 'Add Single Asset'

    Note: The Next button will work only when you have filled out all the information correctly, viz., the correct asset name, category, owner/technician, requesters, user tags, and location.

    Asset Properties | Details

    Instructions to 'Import from CSV'

    Note: The 'Next' button is enabled only when you have uploaded a relevant CSV file.

    Template

    The Template module enables administrators to create predefined templates for modules such as Change. These templates help standardize recurring issues by pre-configuring key fields like subject, impacted services, service classification, priority, etc.

    Templates can be linked to specific teams, support levels, or assigned technicians.

    What you see on the screen

    It displays all templates in a card/ grid layout, each showing the template name, description, and tags like module type (e.g., Ticket, Request), status, and priority.

    On the left panel, you can filter templates by category—Ticket, Change, Request, Release, or Risk. Search and filter options can refine results using simple conditions based on fields like title, risk, or priority.

    For the section below, please create documentation on how to create templates.

    Action Icons

    Each template module includes action icons that allow you to perform specific operations. In Card View, click the three-dot menu on a template to display and access these actions.

    Action Icons | Basic Details

    The Template module allows administrators to create predefined configurations for different ITSM and operational modules.

    The following template categories are available in the Template module:

    Template Categories | Basic Details

    Template Category
    Description

    Request Template Types | Basic Details

    The Request template category supports multiple request types to standardize workflows across different service requests.

    Request Type
    Description
    • To create a new template, click the + Add Template button at the top-right corner of the screen.

    • Each template allows you to predefine values such as title, description, priority, impact, service classification, assignee, tags, and more.

    Add Template | Basic Details

    Once the Title and Description are added, click Add to define the questions that make up the Risk Template.

    Add Questions | Basic Details

    Once added, click on Save to continue.

    Once the questions are added, you can Submit to save the template.

    The Task tab is available as the third and final step when adding a new Template. This section enables users to predefine the tasks associated with a particular change request.

    Click on + New Task to add a task involved in the service. A task configuration panel will appear with the following fields:

    • Title: Enter a name that clearly defines the task.

    • Description: Add detailed instructions or information regarding the task.

    • Type: Choose the type of task from the dropdown (e.g., Default, Checklist).

    • Status: Set the initial status of the task (e.g., To Do, In Progress, Done).

    Once filled, click on Submit to save the configurations.

    It allows you to define task relationships within a request/ release workflow. By configuring parent-child dependencies, you can control the order in which tasks are executed and ensure that no child task progresses until its parent task is completed. It offers:

    • Standalone tasks – A task without dependencies that can be executed immediately.

    • Parent-Child relationship – A child task is only triggered when its parent task is marked as Closed.

    • Multi-level dependencies – Supports nested hierarchies (e.g., Task A → Task B → Task C).

    • Sequential execution

    Configuring Dependent Tasks

    When creating or editing a template:

    1. Navigate to General Settings > Template > Request/ Release.

    2. Add or edit a task

    3. In the Dependent Tasks section:

      1. Select an existing task to act as the parent.

    Once configured, the dependency hierarchy is applied automatically whenever the request/ release workflow is triggered.

    The Close Task option is used to mark a task as completed. To ensure proper documentation, a mandatory Closure Note must be entered before closing the task. This note is then stored in the system and made visible in key sections for reference.

    The closure note requirement applies not only to Tasks but also to other modules, including:

    • Changes

    A text area appears when closing a task, requiring the assignee to enter closure details. The task cannot be closed without providing this note.

    Once saved, the closure note is automatically displayed in:

    • Recent Activities section

    • Communication page of the related record

    Form Template allows you to create reusable forms by adding custom fields based on your business requirements. These templates can be used while adding a helping users capture additional information in a structured format.

    Use Form Templates when different task types require specific input fields such as Email, Number, Date, Dropdown, Checkbox, Text Area, or other custom data fields.

    • Navigate to Template.

    • Click Add.

    • Select Form Template.

    • Enter the Template Name.

    The template will be created and available for use while adding a Task.

    Add Template | Form Template

    Label
    Action
    Description / Example

    Add Custom Field | Form Template

    Clicking Add Custom Field opens the field creation panel, where you can define the field type and configuration.

    Label
    Action
    Description / Example

    The Custom Configuration section allows administrators to configure custom forms for templates by selecting predefined fields, arranging required fields, and adding custom fields based on business requirements.

    Once the custom configuration is created, it can be assigned to a template. When users create or work on a request using that template, the configured fields are displayed in the request form, allowing them to capture the required information, validate inputs against configured rules, and ensure all mandatory details are completed before submitting the request.

    To configure a custom form for the template:

    • Navigate to the Custom Configuration tab while creating or editing a template.

    • Select the Enable Custom Form toggle.

    • Drag and drop fields from the Available Fields section to the Selected Fields section based on the requirement.

    • Use the Add Custom Field

    The Add Custom Field option allows administrators to create additional fields that are not available in the predefined field list.

    To add a custom field:

    • Navigate to the Custom Configuration tab.

    • Select Add Custom Field.

    • Configure the required field details.

    • Select Submit to add the custom field to the template form.

    Add Custom Field | Field Details

    Label
    Action
    Description/ Example

    Once added, click Submit to save the custom field configuration and add the field to the custom form template.

    After selecting and arranging the required fields in the Selected Fields section, users can validate and customize the custom form layout using the available configuration options.

    The following actions are available in the Custom Configuration section:

    Label
    Action
    Description/ Example

    Once the form preview and configuration are complete, select Save to apply the custom configuration to the template.

    Asset Lifecycle

    Endpoint Assets

    The Endpoint Assets Lifecycle represents the systematic stages that endpoint devices, such as laptops, desktops, and mobile devices, go through within an organization.

    Infraon platform ensures that each stage is managed efficiently, from request to retirement, to maintain operational consistency and accountability.

    Below is an overview of each stage, its significance, and key actions within Infraon platform.

    Lifecycle Stages

    1. Request

    The lifecycle begins when a user or department requests a new asset. This stage involves capturing detailed information about the required asset, such as type, quantity, and purpose.

    • Purpose: To initiate the procurement or allocation process.

    • Action in Infraon platform: Create a request ticket and record the details of the asset requirements.

    Once the request is approved, the required asset is procured or leased. This stage ensures the requested assets are obtained and ready for quality checks.

    • Mandatory QA Check: Every asset undergoes a quality assurance (QA) process to verify its compliance with standards.

      • Failed QA: Assets are marked for return to the vendor.

      • Passed QA: Assets are marked as ready for the next stage.

    Assets that pass the QA process are added to inventory. They are categorized based on type, location, and availability for better tracking and management.

    • Purpose: To ensure assets are available and ready for deployment.

    • Action in Infraon platform: Record and track the asset’s status in the IT asset module.

    The asset is configured and prepared for use. This includes installing required software, updating licenses, and ensuring compliance with security protocols.

    • Purpose: To make the asset operational and ready for allocation.

    The prepared asset is assigned to a specific user or department.

    • Actions in Infraon platform:

      • Update the asset’s status to "Allocated."

      • Assign ownership details in the system.

    The assigned user evaluates the asset and decides whether to accept it.

    • If Accepted: The lifecycle continues to the Operation stage.

    • If Rejected: The asset is returned to In-stock for reassessment or reallocation.

    The assigned user actively uses the asset. During this stage, audits are conducted periodically to verify the asset’s compliance, functionality, and condition.

    • Purpose: To monitor the asset's performance during its active use.

    • Actions in Infraon platform:

      • Conduct regular audits and record results.

      • Move non-compliant or faulty assets back to In-stock for resolution.

    The asset is sent for maintenance if an issue arises during the operation stage. This includes resolving technical issues, replacing parts, or updating software.

    • Purpose: To restore the asset to a functional state.

    • Actions in Infraon platform:

      • Create a maintenance ticket.

      • Log actions taken during the repair process.

    After maintenance, the asset returns to operational status with repairs completed and parts replaced.

    • Purpose: Ensures the asset is functional and ready for continued use until new issues arise or it reaches EOL.

    When an asset reaches its end of life (EOL) or becomes irreparable, it is decommissioned. This involves securely wiping data and marking the asset for disposal.

    • Purpose: To ensure safe and compliant asset removal from active inventory.

    The final stage of the lifecycle involves officially retiring the asset. It is removed from the active inventory, and disposal records are archived for reference.

    • Purpose: To close the lifecycle and maintain audit records.

    The Network Devices Lifecycle tracks the stages that network devices, such as routers, switches, firewalls, and other networking hardware, go through within an organization.

    Below is an overview of each stage, its significance, and key actions within Infraon platform.

    The lifecycle begins when a user or department requests a new network device. This stage captures detailed information about the required asset, such as type, quantity, and purpose.

    • Purpose: To initiate the procurement or allocation process for the required network device.

    • Action in Infraon platform: Create a request ticket and record asset details.

    Once the request is approved, the required network device is procured or leased. This stage ensures that the requested devices are obtained and ready for quality checks.

    • Mandatory QA Check: Every device undergoes a quality assurance (QA) process to verify its compliance with standards.

      • Failed QA: Devices are marked for return to the vendor.

      • Passed QA: Devices are marked as ready for the next stage.

    Devices that pass the QA process are added to inventory and categorized based on type, location, and availability. This enables better tracking and management of devices.

    • Purpose: To ensure network devices are available and ready for deployment.

    • Action in Infraon platform: Record and track device status in the IT Asset module.

    The asset is configured and prepared for integration into the network. This includes setting up hardware, performing initial network configurations, and ensuring the device is operational.

    • Purpose: To make the network device operational and ready for integration into the network.

    The network device is integrated into the organization's network infrastructure. This includes connecting the device to other network components, applying configurations, and testing connectivity.

    • Purpose: To ensure the device is fully integrated and functional within the network.

    • Action in Infraon platform: Track integration progress and update device status.

    The network device enters active use, supporting the network's operation. During this stage, regular audits are conducted to verify compliance, functionality, and security.

    • Purpose: To monitor the device’s performance and ensure it continues to meet network requirements.

    • Actions in Infraon platform:

      • Conduct regular audits and record results.

      • Move non-compliant or faulty devices back to In-stock for resolution.

    If an issue arises during operation, the device is sent for maintenance. This includes resolving technical issues, replacing components, or updating firmware/software.

    • Purpose: To restore the device to a functional state and ensure network stability.

    • Actions in Infraon platform:

      • Create a maintenance ticket.

      • Log actions taken during the maintenance process.

    After maintenance, the device is reinstalled and reconfigured as necessary. Any replacement parts are replaced, and the device is returned to active use.

    • Purpose: To ensure the device is fully functional and restored to its operational state.

    • Action in Infraon platform: Track reinstallation actions and update device status to "In-use."

    When the network device reaches its end of life (EOL) or is no longer functioning as intended, it is decommissioned. This stage involves securely wiping data and removing the device from the network.

    • Purpose: To ensure safe and compliant device removal from the network.

    • Action in Infraon platform: Mark the device as decommissioned and initiate disposal procedures.

    The final stage of the lifecycle involves officially retiring the device. It has been removed from the active inventory, and disposal records have been archived for future reference.

    • Purpose: To close the lifecycle and maintain proper audit records.

    • Action in Infraon platform: Remove the device from the active inventory and store all related documentation for compliance and reporting.

    AIOps Events

    What Do You See on the Screen

    You’ll find a range of search and filter options in the Events tab at the top of the screen. These filters help you narrow down events based on their origin.

    To focus specifically on events triggered by AIOps configurations, use the following filters:

    Label

    Description / Example

    Anomaly Event

    Displays events generated from prediction-based anomaly detection using adaptive thresholds.

    It identifies and raises alerts when anomalies are detected in monitored resources. It is tightly integrated with the prediction model and relies on adaptive thresholds generated using machine learning.

    • Detects deviation from expected behavior using AI-generated thresholds.

    • Converts anomalies into event alerts, which can generate tickets if a trigger is configured.

    • Enables real-time issue identification without relying on static threshold configurations.

    Anomalies are detected by comparing live polled values with model-generated thresholds derived from the past 30 days of data. The process follows this logic:

    1. Model Learning The prediction model uses 30 days of historical data to understand the typical behavior of a metric (e.g., CPU, bandwidth usage). It computes:

      • Upper threshold (e.g., expected high usage)

      • Lower threshold (e.g., expected low usage)

      • Mid value (expected average)

    • If the actual value exceeds the upper threshold or drops below the lower threshold, it is flagged as an anomaly.

    • An event is raised, and based on the configuration, a ticket is auto-generated.

    Example: A bank branch typically consumes 3–6 Mbps on weekdays. Suddenly, 2 Gbps of data is transferred on a Sunday. The system recognizes this spike as an anomaly and flags it.

    It is a mechanism designed to reduce alert fatigue by suppressing known, expected, or repetitive events within specific time windows. These events are often harmless and predictable and do not require user action. It is used to:

    • To prevent unnecessary noise in the event system.

    • Avoid triggering notifications such as tickets, emails, SMS, or JSON alerts for known recurring behavior (e.g., nightly shutdowns in retail or banking environments).

    • Improves event signal-to-noise ratio, making real issues more visible.

    • Suppression is time-based and can be manually configured.

    • Suppressed events are not discarded — they are logged but do not generate notifications or tickets.

    • Common use case: devices shut down every evening at 8 PM. The system learns or is told not to raise events during this window.

    Navigate to the Advanced Resource Configuration (ARC) module and enable the Seasonal Event Suppression toggle under prediction settings. You may need to adjust business hour profiles and ensure the correct metrics are selected.

    • In the Events module, suppressed events are still visible but marked (e.g., “Suppressed” tag).

    • They will not trigger tickets or alert notifications unless manually configured otherwise.

    • Suppressed event counts can be viewed in the dashboard widgets and reports.

    Event Association is correlating multiple related events across components or systems and identifying them as part of a common cause or impact zone. It is used to:

    • To detect root causes when multiple alerts are triggered together.

    • To group events meaningfully rather than treating them as isolated issues.

    • Helps in large, distributed environments where dependent systems impact each other (e.g., a UPS failure causing router, switch, and IP camera outages).

    • The learned associations can also be

    Infraon AIOps analyzes the last 90 days of event history to identify patterns and recurring relationships between events. It learns which events frequently occur together and detects potential correlations across components.

    The system generates association rules based on two key parameters:

    • Confidence (%) – Indicates the likelihood that one event is related to another.

    • Support Value – Represents how often a pattern has occurred in the observed data.

    To configure Event Association, navigate to the Advanced Resource Configuration (ARC) module and follow the steps below:

    • Enable the Event Association Mining toggle under the selected asset.

    • Provide the following configuration inputs:

      • Statistic: Select the specific metric (e.g., CPU utilization, bandwidth) on which event association should be applied.

      • Confidence (%): Defines the strength of the relationship between two events. For example, a value of 90% means there's a high likelihood that one event is related to another.

    • In the UI, a parent-child event relationship is displayed.

    • The association details (what triggered what, how confident the system is, etc.) can be traced in the event’s detail view.

    • You can also view these associations in relevant dashboards, where grouped event patterns are visually represented.

    What you see on the screen

    Basic Details | Home Page

    Label

    Action/ Description

    Save

    Click to save the current map view in the network diagram.

    Rescan

    The following information is shown when the mouse pointer hovers over a Geomap location:

    The Geomap pins show different colors based on the status of the nodes. The meaning of these colors are:

    The maps can be viewed in the following types:

    View

    • OSM

    • Google Roadmap

    • Google Terrain

    • Google Altered Roadmap

    and can be Sort By:

    • City

    • District

    • State

    • Country

    Department

    Departments are created within Infraon to group users logically to suit the organization's requirements. Assigning departments to help align teams to workflows, assigning tickets and tasks, and prioritizing work.

    In short, departments are added for efficient work assignment and team management.

    Users can be part of multiple departments at the same time.

    Click on the 'Add Department' button in the top right corner. Provide a department name, select a department head and a prime user, and save.

    *Department Head - Can be managers or business owners who are decision-makers or otherwise known as high-level approvers.

    *Prime User - can be team leads or a senior member of the team who is in charge of the allocation of work. They are the primary responsibility owners and have basic approval privileges too.

    Add asset category.

    Select an asset category that suits your requirement. Refer to the asset categories section for more details.

    Asset ID

    Customize the asset ID

    Customize the asset ID for the assets as required by changing the prefix, number, type, and custom format of the asset ID from the Infraon Configuration. You can opt for alphanumeric, random or auto-increment and a custom format. This allows overwriting of existing assets IDs that update all previously assigned IDs to the new format.

    Asset Workflow (Beta)

    Edit and customize the stages and statues of the IT Assets.

    Flexible to edit and customize the stages and statuses of IT assets and change the flow based on the requirements. Easily modify the default workflow, add new statuses, and control transitions. Experience improved asset management and status tracking similar to ticket workflows.

    Asset Allocation Mail

    Approve or reject the mail by identifying the owner of the email.

    Acceptance and rejection are identified through the email sent to the asset's owner. Allowance of resending the email by eliminating the previous restriction.

    Calculation

    Depreciation calculation

    Calculate the depreciation based on the two methods provided for the assets. These methods gradually reduce the asset's value to provide more accurate and comprehensive reports. Enhances the accuracy and efficiency of asset management, providing a more comprehensive view of asset performance.

    Maintenance

    Maintenance Configuration

    Configure the assets for maintenance, schedule maintenance periods and easily track progress and history.

    Self-service portal

    Asset details in self-service portal

    With the new portal, you can easily view the complete details of the assets, which allows for a self-service portal and a more convenient and user-friendly experience.

    Owner/Technician

    Select the owner or technician using the drop-down menu.

    Requesters

    Select the requester using the drop-down menu.

    User Tag

    Select user tags from the drop-down.

    Assets may be grouped using these using tags.

    Location

    Add the asset location.

    The location where you are working or performing business activities.

    If you feel you have entered the incorrect information, you can click the back button and fill in the correct information.

    Submit

    After filling in all the asset property details, click on the submit button to import the single asset.

    Ensure to add asset details to the default file before uploading.

    Threshold Comparison The model outputs these threshold bands for every hour in the prediction window (typically the next three weeks). The system continuously compares incoming poll data with these thresholds.

  • Anomaly Trigger

  • used to dynamically build a logical topology
    , allowing users to visualize event flows and dependencies, even when no static topology is configured.
  • Support Value: Specifies how often the same event pattern must occur before it is considered significant. For example, a value of 5 means the system must observe the pattern at least five times.

  • Once configured, Infraon uses this data to detect recurring relationships and generate association rules that link related events across your environment.

  • Event Suppression

    Displays events that are tagged for suppression based on time-based or seasonal logic. These events are still raised, but can be excluded from ticketing if suppression is configured in triggers.

    Event Association

    Shows events grouped by correlation rules learned through event association mining.

    Anomaly Events

    How Anomalies Are Detected

    Seasonal Event

    How Suppression is Detected

    Configuration

    A valid license is required to activate this feature.

    Event Association

    How Associations Are Detected

    Configuration

    These associations will be reflected in the Events module with the label “Associated”, showing grouped events and potential root causes.

    Total Devices

    Total number of locations in the state with the assets.

    Maintenance

    Number of assets that are in the maintenance condition.

    Up Devices

    Number of assets that are up and in running condition.

    Down Devices

    Number of assets that are not reachable.

    Disabled Devices

    Number of assets that are in "Disabled" status.

    Unknown 

    Number of assets whose status is not known.

    Red

    If all the nodes are down.

    Google Satellite
  • Google Terrain Only

  • Google Hybrid

  • Bing Road

  • Bing Aerial

  • Bing Aerial with Labels

  • Bing Road Dark

  • Offline Map

  • Click to rescan the map view.

    Click to see the map in full-screen for a wider view.

    Name

    Description

    State

    Name of the state(territory). Example: Karnataka, Tamil Nadu

    District

    Name of District. Example: Jalalsar, etc.

    Total Sites

    Color

    Description

    Green

    All the nodes are up and running.

    Orange

    One or more nodes are in "Disabled" status.

    Gray

    Total number of sites in the state with the assets.

    If all the nodes are in "Disabled" status.

    Delete

    Click to remove

    Permanently delete the selected template from the system.

    Release

    Used to configure Release templates with predefined release details, task dependencies, restriction rules, workflows, and execution plans.

    Risk

    Used to create predefined risk assessment configurations with risk-related details, classifications, impact, mitigation plans, and ownership information.

    Health

    Used to configure predefined health monitoring templates for tracking operational or service health-related activities and alerts.

    Form Template

    Used to create reusable form structures with configurable fields that can be used across request workflows and operational processes.

    Request for Information

    Used to create templates for information-related requests where users require clarification, details, or operational information from support teams.

    Security

    Used to create templates for security-related requests such as access permissions, security approvals, compliance activities, or security validations.

    Onboarding

    Used to standardize employee onboarding processes, including account creation, asset allocation, access provisioning, and task assignments.

    Offboarding

    Used to standardize employee exit processes, including access revocation, asset recovery, task closure, and compliance activities.

    Service Order

    Used to create templates for predefined service delivery or service fulfillment activities requested by users or departments.

    Add (button)

    Click Add to insert risk questions.

    Opens the Add Questions pop-up, where assessment criteria can be defined.

    Defines the importance of the question in risk calculation. Higher = more impact.

    Example: 5 (critical question).

    Option Name

    Enter option choices.

    Possible answers to the question.

    Example: Yes, No, Partially.

    Option Value

    Select a criticality level for each option (dropdown).

    Defines risk level for the chosen option. Options: Critical, High, Medium, Low.

    Add (button)

    Add more questions.

    Use this to build multiple questions in the same template.

    Priority: Define the task's urgency (e.g., Low, Medium, Critical).

  • Due In Date: Specify how many days after the change initiation this task is due.

  • Actual Start Date & End Date: (Optional) Fill these if the task already has expected start/end timelines.

  • Team: Select the team responsible for executing the task.

  • Assignee: Choose the individual who will carry out the task.

  • – Ensures child tasks are created only after their dependencies are met.
  • Validation – Prevents triggering of child tasks when dependent tasks are still pending.

  • Leave blank if the task is standalone.

  • Save the template.

  • Click Add Custom Field to create required fields.
  • Drag the created fields from Available Fields to Selected Fields.

  • Arrange the fields as required.

  • Click Submit.

  • Available Fields

    Drag and drop

    Displays all created custom fields available to use in the template.

    Selected Fields

    Drag and drop

    Move required fields here to include them in the template form.

    Edit Icon

    Click to modify

    Edit the selected custom field properties.

    Delete Icon

    Click to remove

    Removes the field from Selected Fields and moves it back to Available Fields.

    Placeholder

    Enter text

    Add helper text inside the field. Example: Enter your email

    Mandatory

    Enable / Disable toggle

    Mark the field as required when filling out the form.

    Validation Rules

    Configure

    Define input validation, such as Regex or allowed values.

    Error Text

    Enter text

    Message shown when invalid data is entered. Example: Please enter a valid email

    option to create additional fields if required.
  • Configure the required field details and validations.

  • Select Next to proceed to the next configuration step.

  • Placeholder

    Enter placeholder text

    Displays sample text inside the field before user input. Example: Enter Employee ID.

    Mandatory

    Enable the toggle

    Marks the field as mandatory. Users must provide a value before submitting the form.

    Validation Rules

    Configure validation details

    Allows administrators to define input validation using Regex patterns to control the accepted format for field values.

    Regex

    Enter validation pattern

    Defines the validation pattern for user input.

    Error Text

    Enter validation message

    Displays a custom validation message when the entered value does not match the configured validation rule.

    Label

    Action

    Description / Example

    Edit

    Click to open the template in edit mode

    Modify existing details or update configurations as needed.

    Clone

    Click to duplicate

    Ticket

    Used to create predefined Incident or Ticket configurations with default values such as subject, priority, assignment details, impact, urgency, and related services.

    Change

    Used to create standardized Change configurations, including change details, planning information, task configuration, risk details, and approval settings.

    Request

    Provision Request

    Used to create templates for provisioning-related activities such as user access, software allocation, device setup, or infrastructure provisioning.

    Purchase

    Used to create templates for procurement and purchase-related requests, including hardware, software, licenses, or service acquisitions.

    Request

    Label

    Action

    Description / Example

    Template Title*

    Enter a title for the template.

    Name of the risk template. Example: Network Upgrade Risk Template

    Template Description

    Enter a description of the template.

    Label

    Action

    Description / Example

    Question*

    Enter the assessment question.

    The risk-related query. Example: Does the change impact production systems?

    Weight (Range: 1–5)*

    Template Name*

    Enter text

    Specify a unique name for the template. Example: Employee Onboarding Form

    Add Custom Field

    Click to add

    Field Type*

    Select from the drop-down

    Choose the type of field to create. Example: Email, Text, Number, Date, Dropdown

    Label*

    Enter text

    Field Type

    Select from the drop-down

    Defines the type of custom field to be created. Available options include Text, Email, Phone Number, Checkbox, etc.

    Label

    Enter the field label

    Preview Form

    Select Preview Form

    Opens a preview window displaying the configured custom form with all selected fields arranged in the configured layout. Users can verify field labels, placeholders, mandatory field indicators, dropdown values, and overall form structure before saving the template configuration.

    Configure Form

    Select Configure Form

    Template Categories

    Add Template

    To understand how to fill in each field, refer to the respective module's documentation for detailed instructions on adding the required information.

    Add Risk Template

    When a change template is linked with a risk template, any change created using that change template will automatically have the associated risk template applied.

    Add Task

    Dependent Task

    Close Task

    If a closed task is edited, the closure note field is shown along with the previously entered note for reference.

    Add Form Template

    Click Submit to save the custom field and add it to Available Fields.

    Custom Configuration

    Add Custom Field

    Using Custom Forms in Request Submission

    Custom forms configured in the Custom Configuration section can be used when creating a Request in the Self-Service Portal. Configured fields are displayed as structured form sections where users can manually add records or import data using CSV files.

    Task,

    Create an identical copy of the template, which can be modified without affecting the original.

    Used to create predefined service request configurations for different request types such as provisioning, onboarding, purchase, and security requests.

    Used to configure general service request templates for standard operational or business service requests.

    Brief explanation of the purpose of the template. Example: Used for assessing risks in major network upgrades.

    Assign a weight to the question.

    Opens the custom field configuration panel to create a new field.

    Enter the field name shown in the form. Example: Employee Email

    Specifies the display name of the custom field in the form.Example: Employee ID, Work Location, or Contact Number.

    Opens the Configure Form window to define the form name and organize the selected fields into the required layout structure. Users can rearrange fields, group related sections, and customize the overall form presentation based on operational or business requirements before saving the configuration.

    Go to Infraon Configuration -> User Management -> Department

  • Click on the 'Add Department' button.

  • Label

    Action

    Description/Example

    Department Name*

    Give a name to your Department's password policy.

    Incident Management, Finance, HR, etc.

    Department Head

    Once all the parameters are added, click 'Submit' to save the department.

    Repeat the process to add multiple departments.  Departments can be edited or deleted using the respective icons.

    Add Department

    Instructions to 'Add a Department'

    2. Acquisition

    Note: Assets cannot move directly from Acquisition to In-stock without passing the QA check.

    3. In-stock

    4. Installation

    5. Allocation

    6. User Acceptance

    7. Operation

    8. Maintenance

    9. In-Used

    10. Decommission

    11. Retire

    Network Assets

    Lifecycle Stages

    1. Request

    2. Acquisition

    Note: Devices cannot move directly from Acquisition to In-stock without passing the QA check.

    3. In-stock

    4. Implementation

    5. Integration

    6. Operation / In-Use

    7. Maintenance

    8. Re-Install

    9. Decommission

    10. Retire

    IT Asset (Network) Lifecycle. ITAM Lifecycle. Network asset lifecycle (workflow)
    IT Asset Lifecycle. ITAM Lifecycle. Endpoint asset lifecycle (workflow)

    How does it work?

    Assets must be added to Infraon to enable management. There are multiple ways to add assets.

    • Assets can be added directly from the Infraon asset module. Within the asset module, there are options to manually add an asset or add bulk assets using a .csv file.

    • Agent-based discovery initiated from the Infraon configuration module.

    Assets can be viewed in Grid and card views. Clicking on the corresponding action icons in the assets allows you to scan and search for assets, export them, and perform maintenance actions.

    When this setting is enabled, the system allows admins to define a custom asset ID structure for each asset category. The format can be tailored using prefixes, numeric values, and custom fields to meet organizational standards.

    This format is applied automatically during asset creation, bulk upload, or discovery, ensuring each asset is uniquely and consistently identified.

    Example Formats

    • #IT-LPT-0001

    • #ASSET00023

    • #ESOL-D-0038

    You can configure this from the Category Template > tab.

    Customize Asset ID Format | Field Reference

    Multi-selection of assets is facilitated by clicking the checkboxes adjacent to each desired asset.

    Users can now:

    • Assign a new owner

    • Assign a requester

    • Assign a tag

    • Print

    Shift Configuration

    This allows administrators to create and manage shift schedules for teams within the organization. It helps define shift timings, working days, business hours, effective periods, team allocation, and shift-based ticket assignment workflows.

    Shift configurations are used to organize operational coverage, distribute workload across teams, and automate ticket assignment based on configured shift schedules and availability.

    What you see on the screen

    The Shift Configuration page displays configured teams and their assigned shift schedules. Users can view shift timings, team details, and manage shifts using the timeline view.

    The left panel displays available teams, while the main section displays configured shifts with options to add, edit, or delete shift configurations.

    Shift Configuration | Basic Details

    Label
    Action
    Description / Example

    The configured shifts are used for operational scheduling and automatic ticket assignment based on configured shift timings.

    Add Shift | Field Descriptions

    Label
    Action
    Description / Example

    Once the required details are configured, click on Submit to save the shift details and create the shift schedule.

    Tag Management

    Tags are simplified identification keywords used to group items or users within Infraon. Tags can be applied to users, assets, Incidents or requests, articles, etc.

    Tag Types

    Tagging enables quick grouping of items/users.  At this point in time, tags are added for:

    • Assets - Tag assets by brand, vendor, location technician, etc.

    • Users - Tag users by the team, skills, location, service catered, etc.

    • Expertise - Tag teams (team creation) with   Hardware, Python, Django, or product expertise like washing machines, TV, etc.

    • Services - Tag services by team, location, category, classification, etc.

    • Incident - Tag incidents by the team, technician, site, catalogue, criticality, device, etc.

    • Requests - Tag incidents by the team, technician, site, catalogue, criticality, device, etc.

    In a business where the end-users call from multiple locations for support on laptops and desktops, asset tags such as Laptop, Desktop, NY, AU, and IND can be used to assign these incidents to technicians tagged as Laptop, Desktop, NY, AU, and IND.

    • Go to Infraon Configuration -> General Setting ->Tag Management

    • Click the '"Add Tag button'

    Once both the parameters are added, click 'Submit' to save the tag.

    Repeat the process to add multiple tags.  Tags can be edited or deleted using the respective icons.

    Here are the 7 methods you can assign the asset tag.

    Method 1: Single Asset

    • Go to Infraon Asset Card page -> Select the asset-> ( ⋮ ) More -> Edit

    • Enter the required details, add the tag in Asset Tag, and click Next.

    • Check the details in Asset Properties and click Submit.

    Method 2: Bulk- Card/ Grid View

    • Go to the Infraon Asset Card page -> Select multiple Assets.

    • Click on Tag at the center of the top panel. Click on “Yes, Edit it.”

    • Name your Tag and click Submit.

    Method 3: Bulk Edit

    • Go to the Infraon Asset Card page -> Actions -> Bulk Edit.

    • Select the Category.

    • Download the CSV file (Excel sheet) and enter the tag name on the sheet.

    • Upload the same edited CSV file.

    Method 4: Tags can be assigned directly while adding an asset.

    • Go to the Infraon Asset Card page -> Add Item -> Single Asset

    • Add the required details to add the asset.

    • Select the Tag in the Asset Tag section.

    • Click Next -> Asset Properties -> Submit.

    Method 5: Manually from CSV file (excel sheet)

    • Go to the Infraon Asset Card page -> Add Items -> Import from CSV

    • Select the required Category and download the CSV file.

    • Enter the Tag name in the sheet, use a semicolon (;) to add multiple tags at a time Eg: SHQ; BHQ

    • Upload the same edited CSV file.

    Method 6: Asset details page

    • Go to the Infraon Asset Card page -> Select the Asset Name and redirect to the Details page.

    • Locate the Tags button in the center of the page, near the left panel.

    • Click to proceed to Add the required tags.

    Method 7: Import from CSV

    • Go to Infraon configuration page -> IT Operations -> Discovery -> Automatic Discovery.

    • Click the "Import from CSV" button at the bottom center of the page.

    • Download the CSV file (Excel sheet) and enter the tag name on the sheet.

    • Upload the same edited CSV file.

    Method 1: Bulk

    • Go to the Infraon Asset Card page -> Select the Asset Name and redirect to the Resource page.

    • Check the boxes next to the resources you need to tag.

    • Click on the Add Tag option, add the required tag, and click Submit.

    Method 2:

    • Go to Infraon configuration page -> IT Operations -> Advance Resource Configuration.

    • Click Configure.

    • Navigate to the top right corner and click Actions -> Tag.

    • Add the required Tag.

    Method 3: Advance configuration (CSV file)

    • Go to Infraon configuration page -> IT Operations -> Advance Resource Configuration.

    • Click Configure.

    • Click the "Export" button in the top right corner.

    • Clicking the button downloads the CSV file immediately (a pop-up may appear).

    Method 1: Single

    • Go to Infraon Asset Card page -> Select the asset-> ( ⋮ ) More -> Edit

    • Enter the required details, add the tag in Owner Tag, and click Next.

    • Check the details in Asset Properties and click Submit.

    Method 2: Bulk Edit

    • Go to the Infraon Asset Card page -> Actions -> Bulk Edit.

    • Select the Category.

    • Download the CSV file (excel sheet) and Enter the Tag name in the sheet.

    • Upload the same edited CSV file.

    Method 3: Bulk- Card/ Grid View

    • Go to the Infraon Asset Card page -> Select multiple Assets.

    • Click on Tag at the center of the top panel. Click on “Yes, Edit it.”

    • Name your Tag and click Submit.

    Method 4: Import from CSV

    • Go to Infraon configuration page -> IT Operations -> Discovery -> Automatic Discovery.

    • Click the "Import from CSV" button at the bottom center of the page.

    • Download the CSV file (Excel sheet) and enter the tag name on the sheet.

    • Upload the same edited CSV file.

    Profile

    An SLA Profile defines the objectives regarding the quality of service and performance. For example, a Gold profile customer may get a quicker response and resolution than a Silver profile customer. An SLA profile consists of SLA Type, Service Level Targets, and the conditions under which these targets are applicable.

    To add an SLA Profile, go to the SLA module -> Profile -> Add SLA Profile -> Ticket. There are three tabs under which the details of a profile are captured.

    In Profile Details, one can specify basic details of the profile like name, type, description, start and end dates, and so on. The description of the fields is given below:

    Select a user using the dropdown menu to make them the department's head.

    Department Heads can be managers or business owners who are decision-makers. They are otherwise known as high-level approvers.

    Prime User

    Select user(s) using the dropdown menu to make them the department's head.

    Prime User(s) can be team leads or a senior member of the team who is in charge of allocating work.

    They are the primary responsibility owners and have basic approval privileges too.

    Description

    Add a brief description of the department.

    Handles tickets, Manages payroll and taxation, For new hire onboarding, etc.

    Click Next -> Import -> Proceed with Valid Records.

    Click Next -> Import -> Proceed with Valid Records.

    Click Next -> Import -> Proceed with Valid Records.

    Enter the Tag name in the sheet.

  • Now navigate to the Infraon configuration page -> IT Operations -> Advance Resource Configuration.

  • On the top right corner, click Bulk Resource Update.

  • Upload the same edited CSV file.

  • Click Next -> Import -> Proceed with Valid Records.

  • Click Next -> Import -> Proceed with Valid Records.

    Click Next -> Import -> Proceed with Valid Records.

    Label

    Action

    Description/Example

    Tag Name*

    Give a name to the tag

    Laptops, Desktops, IT, HR, India, NY, etc.

    Type*

    Select tag type using the drop-down menu.

    How to use a tag effectively?

    Instructions to 'Add a Tag'

    Note: Assigned tags cannot be deleted.

    Instructions to ‘Assign a Tag’

    Asset Tag

    Resource Tag

    Owner/ User Tag

    Refer 'Tag Types' section above for detailed information

    Scan & Search Asset

    Search by barcode: type the asset's code.

    To scan and search for an asset, click on the 'Scan and search asset' option, then use your phone to scan the QR code, which will initiate the asset search process.

    Export

    Click to choose the category.

    To export the data, click the 'Export' button, then choose the desired category, and finally download the CSV file containing the selected data.

    Maintenance

    Click to redirect to the Maintenance page.

    When an asset is designated for maintenance, its status is changed to the "maintenance" stage. After scheduling the maintenance time, the asset is set to run automatically during that scheduled period. Once the maintenance is completed, the asset reverts back to its previous state, resuming normal operations or the state it was in prior to the maintenance activity.

    Bulk Edit

    • Go to the Infraon Asset Card page -> Actions -> Bulk Edit.

    • Select the Category.

    • Download the CSV file (excel sheet) and Enter the Asset details in the sheet.

    • Upload the same edited CSV file.

    To Edit Multiple Assets information or details at once.

    Download Agent

    Click to download the Infraon agent available on Windows, MAC, and Linux.

    Customize Asset ID

    To customize the Asset ID configuration.

    CLI Session

    Click to navigate back to the CLI session module.

    CLI Jobs/sessions in NCCM create direct CLI sessions (SSH or TELNET) between the Device and the User through the NCCM application.

    Download Job

    Click to navigate back to the Download Job module.

    NCCM’s Download Jobs added through Discovery process or manual Device addition will start downloading Device configurations, Operational Data, Device Inventory Details, OS image details based on “Configuration Profile” assigned, Device Credentials, Connection & Download protocol selection and Schedule period.

    Define a static prefix that appears before the numeric or alphanumeric value.

    Example: ASSET, ESOL, IT-LPT

    Add Field (Custom Format)

    Click to add fields

    (Optional) Add dynamic components like location code or department manually.

    Number Type

    Select from the dropdown

    Choose how the numeric part of the ID should be generated. Options:

    · Auto Increment: Sequential numbers (e.g., 0001, 0002)

    · Alpha Numeric: Mix of letters and numbers (e.g., IT01A)

    · Random: Generates a randomized unique value (e.g., X23B)

    No of values

    Select from the dropdown (1–10 digits)

    Define the length of the numeric part. Example: 4 creates IDs like 0001, 0002, etc.

    Starting From

    Enter a numeric value

    Sets the starting number for the ID sequence. Example: 1 generates 0001, 0002...

    Change the Status of the assets.
  • Edit the Location

  • Enable/ Disable

  • Add to NCCM

  • Delete multiple assets at once.

  • Add to Log Management

  • Add Download Jobs/ Edit Download Jobs

  • Diagnose

  • Mask Alarms

  • Unmask Alarms

  • Maintenance

  • Change category

  • Label

    Action

    Description/ Example

    Search

    Search for the required asset.

    Filter

    Filter can be added based on the field (Card name, card type, device IP, part number, and serial number) and condition from the drop-down box below.

    Label

    Action

    Description / Example

    Preview Section

    View-only

    Shows a live preview of how the Asset ID will look once generated.

    Example: #ASSET-0001

    Prefix

    Customize Asset ID

    • Ensure that the "Customized Asset Id" field is selected in the Fields tab of the category template.

    • Once saved, the format is automatically applied to all assets created under the configured category.

    Selecting multiple assets:

    Basic Details

    Actions

    Enter text manually

    View shift information

    Displays configured shift name, assigned team, shift duration, and total team members.

    Shift Duration

    View shift timing

    Displays the configured start and end timing of the shift. Example: 09:30 - 15:30

    Team Count

    View member count

    Displays the total number of users assigned to the shift team.

    Timeline View

    View schedule timeline

    Displays shift schedules in a timeline-based format for easier visibility of operational coverage.

    Actions

    Edit

    Modify shift

    Allows users to edit the selected shift configuration.

    Delete

    Remove shift

    Deletes the selected shift configuration after confirmation.

    Shift Name*

    Enter shift name

    Specifies the name of the shift. This field is mandatory. Example: Morning Shift

    Shift Code

    Enter shift code

    Defines a unique code or identifier for the shift. Example: MORN-01

    Min. Team Size*

    Enter minimum team size

    Specifies the minimum number of users required for the shift. This field is mandatory.

    Team color*

    Select color

    Defines the color used to visually represent the shift in the schedule timeline.

    Effective From*

    Select effective start date

    Specifies the date from which the shift configuration becomes active. This field is mandatory.

    Effective Till*

    Select effective end date

    Specifies the date until which the shift configuration remains active.

    Shift does not have an end date

    Enable/disable checkbox

    Allows the shift to remain active without configuring an end date.

    Add a note

    Add additional note

    Allows users to attach notes or comments related to the shift configuration.

    Teams

    View configured teams

    Displays the list of available teams configured for shift management.

    Team List

    Select team

    Allows users to select a team and view its configured shift schedules.

    Shift Timeline

    View shift schedule

    Displays configured shift timings and schedule duration for the selected team.

    Select Team*

    Select team

    Specifies the team for which the shift should be configured. This field is mandatory.

    Select Business hours*

    Select business hour profile

    Add Shift

    Based on the configured business hours, users can define shift start and end timings for each day of the week.

    The Shift Timing section allows separate schedule configurations for individual weekdays, while the Apply to All option automatically applies the same shift timing across all working days.

    • Mandatory fields are marked with an asterisk (*).

    • Ticket assignment workflows can use configured shift timings for operational allocation and routing.

    • All shift creation, update, and deletion activities are recorded in audit logs.

    Shift Details

    Associates the shift with a configured business hour profile. This field is mandatory.

    Name

    Name of the SLA profile.

    Give a name for the SLA profile. For Example, Gold, VIP, and Platinum.

    SLA Type

    Select the type of the SLA.

    Service - define the quality of service offered.

    Performance - define the availability of the services.

    Status

    Select the status of the profile.

    The status of the profile can be Active or In-Active.

    Compliance Target

    Set the compliance percentage.

    A compliance target is the percent of the performance of the SLA to check if the terms were met over a period of time.

    Start Date

    Start Date of the SLA

    End Date

    End Date of the SLA

    Description

    Describe the SLA profile.

    In this tab, the commitments made by the service provider in terms of availability, response, or resolution times are captured.

    • Business Hours Profile—Business hours are the daily working hours of teams/departments within the organization. Select the business hours profile from the drop-down. Business hours can be configured in Infraon Configuration -> General Settings -> Business Hours -> Add Profile.

    To know more about Business Hours, click here.

    • Target Profile - This section allows you to define metrics for response and resolution times. Go to Target Profile -> Add New Profile.

    Label

    Action

    Description/Example

    Target Profile

    Specify a name for the target profile.

    *Select Metric

    *Non-Business Hours are optional.

    *Metrics are derived from the Metrics tab of the SLA module. Custom metrics can be defined for conditions like Start, Pause, Resume, etc.

    The 'Applied For' tab allows a user to specify the conditions under which the SLA metrics are applicable.

    After entering all the details, click 'Submit' to create the SLA Profile.

    An SLA Profile can be edited or deleted after it is created. Deleting an SLA Profile is irreversible.

    Customize default metrics like response and resolution times, and tailor them to your specific operations. Improved flexibility with predefined business hours and effortlessly applied services to meet unique requirements.

    Label

    Action

    Profile Details

    Description/Example

    Service Level Target

    Applied For

    Default SLA

    Configure SMS Gateway

    The Configure SMS Gateway section is used to configure SMS delivery services for the platform.

    The module contains the following configuration types:

    • Global Configuration

    • Customer Specific Configuration

    Global Configuration defines system-wide SMS gateway settings that apply across the platform. Administrators can configure:

    Asset Categories/Sub-Categories

    See it in action!

    Defining the asset category and sub-category is the first step in adding the asset. Categories can also be called Parent categories. It is recommended that an asset category be added before an asset. The process of adding a category and a sub-category is the same.

    Hovering the mouse over the category:

    Click Next -> Import -> Proceed with Valid Records.

    Select the type of the Metric.

    Examples of metrics:

    • Response - Define the time duration within which the customer can expect a response/acknowledgment based on the 'Priority' of the ticket.

    • Resolution - Define the time duration within which the customer can expect a resolution for the ticket based on its 'Priority.'

    Business Hours

    Define the number of minutes, hours, or days required to respond/resolve a ticket based on its priority.

    Suppose a ticket with a priority of 'Critical' is newly created, and the response metric is set at 10 mins. The service desk has to respond/acknowledge within 10 mins to the customer.

    *Non-Business Hours

    Define the number of minutes, hours, or days required to respond/resolve a ticket based on its priority during non-business hours.

    SMS provider details

  • Authentication parameters

  • Request headers

  • Query parameters

  • SMS delivery methods

  • SMPP settings

  • The configuration process contains two steps:

    • Configuration

    • Test

    Select SMS Gateway in the SMS Config Type field to configure API or HTTP-based SMS delivery services.

    This configuration type is generally used for third-party SMS providers that support REST APIs or URL-based SMS requests.

    Follow the table below for more details.

    Configuration Details | SMS Gateway

    Label
    Action
    Description / Example

    SMS Config Type

    Select SMS Gateway

    Defines the SMS integration method using API-based or HTTP-based SMS gateway providers. This option is commonly used for providers such as Fast2SMS, MSG91, TextLocal, and similar SMS services.

    Title

    Enter Title

    Configure request parameters required by the SMS provider API for authentication, recipient details, message content, routing, and other delivery settings.

    Label
    Action
    Description/ Example

    Key

    Enter Key

    Specify the parameter name required by the SMS provider API. Example: numbers, message, authorization, route, Content-Type

    Value

    Enter Value

    Select SMPP Gateway in the SMS Config Type field to configure SMPP protocol-based SMS communication.

    This configuration type is generally used for enterprise-grade SMS delivery and telecom provider integrations supporting SMPP connectivity.

    Follow the table below for more details.

    Label
    Action
    Description / Example

    SMS Config Type

    Select SMPP Gateway

    Defines the SMS integration method using SMPP protocol communication for enterprise or telecom-based SMS delivery services.

    Title

    Enter Title

    Configure DLT (Distributed Ledger Technology) parameters required for telecom regulatory compliance and SMS delivery validation in supported regions.

    Label
    Action
    Description/ Example

    Key

    Enter Key

    Specify the DLT parameter key required by the provider. Example: PE_ID, Template_ID

    Value

    Enter Value

    • Once added, click on Submit to save the SMS gateway configuration details configured for the selected SMS provider.

    • Click on Test & Save to validate the configured SMS gateway settings by sending a test request and saving the configuration after successful verification.

    After adding the SMS configuration details, users can move to the Test section to validate SMS delivery before saving the configuration.

    The Test section helps administrators verify:

    • Gateway connectivity,

    • Message delivery,

    • Request parameter configuration,

    • And the SMS provider response.

    Follow the table below for more details.

    Label
    Action
    Description / Example

    Phone Number

    Enter Phone Number

    Specify the recipient mobile number to which the test SMS should be sent to validate the configured SMS gateway. Example: 91XXXXXXXX90

    Message

    Enter Message

    Click on Save to save the SMS gateway configuration after successful testing and validation of the configured settings.

    Global Configuration

    SMS Gateway Configuration

    Request Parameters

    SMPP Gateway Configuration

    DLT Parameters

    Enable the Secondary SMS/SMPP Gateway option to configure an additional gateway that can be used as a backup or failover mechanism when the Primary Gateway is unavailable or fails to deliver messages.

    Test Configuration

    Click Test to send a test SMS request and validate the configured gateway settings, request parameters, authentication details, and the SMS provider's response.

    Edit

    Click to make changes to the category.

    Delete

    Click to delete the category.

    Before adding an asset category/sub-category

    The ‘Add Category’ field tab is where you can define or configure asset properties. Asset properties may include basic details like make, model, size, dimensions, etc., and critical information like EOL, EOS, end of support, etc. Some properties are mandatory for all asset categories.

    The properties within Infraon are categorized into sections. Some sections are optional, whereas some are mandatory. The optional sections are available for selection based on the type or category of assets.

    The sections are listed below the title ‘Available Section’. Once selected, they are added to the ‘Selected Section’ part and are available for defining permissions and field-level customizations. Please note that selecting fields makes them mandatory for the selected asset category. Field selection is also possible for mandatory sections.

    In addition, Infraon allows you to create custom fields and select unique identifiers.

    Few asset properties are mandatory across all asset categories. The mandatory properties and the fields are as follows:

    Label

    Fields

    Common Properties

    Status, Criticality, Service Status, Operational Status, Business Function, Description, Installation Date, Usage Type, State Change, Reason, Retire Reason, Vendor, Uninstall Date

    Procurement Properties

    Warranty In Year & Month, Warranty Expiry Date, Expiry Date, Purchase Vendor, AMC Vendor, AMC Cost, AMC Expiry Date, Lease End Date, Disposal Date, Reason, End Of Life, End Of Sale, End Of Support, End Of Extended Support, Last Renewal Cost, Next Support Renewal Cost, Effective Date, Effective Cost, Estimated Cost, Book Value, Tax Credit,

    Cost Properties

    The asset properties below are optional and available for selection.

    Label

    Examples

    Hardware Properties

    Serial Number, Hostname, Alias, Make, Model, UUID, Manufacturer, Domain, IP Address, Series, Tag No, QR Code, Barcode

    OS Properties

    OS Name, OS Version, OS Service Pack, OS Install Date, OS Installed By, Build Number, Product ID, Product Key, Virtual Memory

    CPU Properties

    Additional customizations are enabled within the 'Selected Sections.' You can define role-based view and edit permissions. These can be defined at the property level as well as the field level. You can enable or disable a specific field and make it mandatory using the relevant action icons.

    Unique fields are unique identifiers for assets. Use the unique field drop-down to select as per requirement.

    In addition to the default asset property fields, Infraon allows you to add custom fields. Check the ‘Add Custom Field’ section below for more information.

    Add pound currency in the asset management from UI symbols verification

    Expanded Currency Options! Now offering 163 currencies, with INR as the default. Detailed asset currency view, cost estimates, and currency display in asset life cycle and depreciation graphs.

    Select Assets -> Asset Type (IT Asset or Fixed Asset, etc.) from the left menu panel to view the asset grid page. The category panel is displayed on the left, and the assets are listed in a card view on the right.

    • Click on the + icon in the category panel.

    • The 'Add asset category' window appears.

    • Choose whether you are adding the category or the sub-category using the option button.

    There are two tabs to add a category/sub-category.

    Basic Details | Fields

    Label

    Action

    Description/Example

    Category Name

    Add the asset category name.

    Define the asset category name you want to categorize for asset management. For example, the IT asset defines the category as laptop, desktop, etc.

    Associate Item Types

    Use the dropdown menu to associate asset items to this category.

    Other Details | Fields

    Label

    Action

    Description

    Mark as CI

    Select the toggle button to mark it as CI

    CIs (Configuration Items) enable better tracking, management, and understanding of the asset's relationships and dependencies with other CIs.

    Notify End Users on Asset Allocation (End Users can Accept/Deny assets)

    After this step, click ‘Next’ to define fields for the selected asset category.

    To add a sub-category within the selected category, proceed as below:

    Sub-Category

    Click on the sub-category.

    Select this option to define an asset sub-category. A sub-category can be defined for an existing category too.

    Parent Category

    Select the parent category name using the drop-down menu.

    Define the parent category of your asset sub-category.

    Click 'Next' to define 'Fields' for the sub-category.

    Basic Details | Fields

    The mandatory sections are added by default. There are multiple levels of customization available here.

    Level 1: From the list of mandatory fields, select fields to make them mandatory.

    Level 2: Scroll down to select additional sections to add them to the selected section.

    Level 3: Select fields from the additional sections to make them mandatory.

    Level 4: Define role-based privileges, enable/disable fields or make them mandatory.

    Level 5: Create a custom field to suit your specific needs.

    Level 6: Select fields from the list of unique identifiers to add them.

    Once the customization is complete, click ‘Submit’ to save. The ‘Add Item’ section provides details and instructions on adding an asset.

    Label

    Action

    (+)

    To add a sub-category.

    How does it work?

    Mandatory Asset Properties

    Unique Fields

    Create a Custom Field

    Instructions to add the Asset Category

    System Configuration

    Customize your language and time zone settings on Infraon.

    The module offers a centralized location for administrators to manage various user experiences and formatting settings for different modules within the Infraon platform.

    Here's a breakdown of the key functionalities:

    Language and Time Zone

    Admins can define the default language and time zone for the entire platform, ensuring a consistent user experience.

    Timeout

    Set the duration of user inactivity before automatic session lockout to enhance security and prevent unauthorized access to open sessions.

    Assets

    Label

    This powerful feature allows for customization of how specific data is formatted within various Infraon modules. For example, admins can define prefixes for modules like Tickets, Assets, Requests, etc. These prefixes will be displayed instead of the actual names within the portal, potentially improving organization and clarity for users.

    Additionally, formatting options for these modules can be configured, providing granular control over how information is presented.

    The following section breaks down the details:

    For instance, admins can configure these formatting preferences

    • Ticket

    The Ticket module automatically closes tickets that remain in the Resolved status for a defined period. The system calculates the duration based on configured business hours and closes the ticket once the time is completed. Auto-closure starts from the first business hour after resolution and excludes weekends, holidays, and lunch breaks. All system-initiated closures are logged in the ticket activity history.

    Auto-Closure Settings

    The following fields are available in the Ticket module under System Configuration → Formatting.

    • Asset

      • Prefix

    • Request

      • Prefix

    Once the changes are made to satisfaction, click “Save” to proceed.

    The CLI Jobs allow administrators to define the default behavior and restrictions for command-line interface (CLI) jobs. This configuration ensures that access durations, idle timeout, and session frequency are consistent and secure across the platform.

    Action Icons | Basic Details

    These configurations manage upload jobs, CLI job restrictions, and request approval workflows in the NCCM module.

    It prevents the execution of upload jobs and restricts any device configuration changes through the upload functionality.

    Blocks users from executing CLI jobs, adding an extra layer of control for sensitive operations.

    These three sections work together to integrate NCCM with an external approval system through API calls. You can configure endpoints and expected payloads to initiate approvals, check their status, and update results once they are actioned.

    Action Icons | Basic Details

    This section helps the NCCM system update the job’s approval status dynamically once a request is approved, rejected, or pending in the external system.

    Two-Factor Authentication (2FA) adds an extra layer of security to requester accounts in the Self-Service Portal (SSP) by requiring a time-based one-time passcode (TOTP) from an authenticator app.

    The availability of the 2FA option in the requester’s Account Settings depends on the organization-level configuration set by the administrator.

    Behavior Based on Org Settings

    Org Setting
    Result in SSP
    Example
    • The 2FA toggle is dynamically enabled/disabled based on org-level configuration.

    • Admins maintain centralized control to enforce or relax requester 2FA usage.

    Announcements

    The Announcement module enables administrators to create and manage time-bound messages that are displayed to users within the application. It supports targeted communication through configurable visibility settings, including users, teams, and tags, ensuring that announcements reach the intended audience.

    Announcements are automatically published and expire based on the configured date and time.

    What you see on the screen

    The Announcement page displays a list of all created announcements with their current status.

    Users can view announcements under two tabs:

    • Active: Displays currently ongoing announcements within the publish duration

    • Expired: Displays announcements that have passed their publish end date

    Each announcement record includes details such as:

    • Announcement ID

    • Created By

    • Created On

    • Publish Start Date

    Announcements are created with a defined publish window and optional visibility configuration.

    • Once the Publish Start Date is reached, the announcement becomes visible to users.

    • Announcements are displayed in the Notifications panel → Announcement tab in the top navigation bar.

    • Users can click Read More to view the full announcement content.

    Use this option to create a new announcement and configure its visibility and duration.

    Add Announcement | Field Descriptions

    Label
    Action
    Description / Example

    After entering the required details, click Add Announcement to save the configuration. The announcement will be published automatically based on the defined start and end dates.

    Metric

    A Metric defines how SLA time is calculated for a record. It controls when the SLA timer starts, pauses, resumes, stops, or is cancelled based on configured conditions. Metrics are used within SLA profiles to measure response and resolution timelines across modules.

    Each metric supports configurable Start, Close, Pause, Resume, and Cancel conditions using State and Status values. Multiple conditions can be combined using AND / OR logic. When Status is selected, the metric becomes workflow-aware, allowing conditions to be defined based on statuses specific to a selected workflow.

    Metrics can be created, edited, or deleted for Ticket, Request, and Change modules. Default metrics such as Response and Resolution are available and can be enhanced with additional conditions as required.

    • Navigate to SLA → Metric

    API Registration

    APIs or Application Programming Interfaces are added to enable data exchange between Infraon and computers/programs/applications. API integrations are possible with other third-party applications and web services supporting HTTP protocol.

    Infraon supports REST API. REST stands for Representational State Transfer that adheres to REST architectural constraints. REST serves as a bridge between the client and the server, allowing communication over HTTP. It enables servers to cache responses, resulting in improved application performance.

    The REST-API serves as a single point of entry into the system. Before granting access to the application's resources, it encapsulates the business logic and processes all client requests, including authorization, authentication, data sanitization, and other necessary tasks. Infraon supports the below content types:

    • application/json

    Determines which status is used to calculate the ageing time for auto-closure. Example: Selecting Resolved means the timer starts once the ticket enters the Resolved state.

    Activation Status

    Displays activation state

    Shows whether auto-closure is active for the Ticket module.

    Prefix

    Enter or customize prefix

    The prefix used when generating ticket numbers. Example: TKT results in identifiers like TKT6023.

    Preview

    View example output

    Displays a sample ticket identifier and layout with the applied prefix.

    Resolve ticket will close automatically in (1,2,3….) days

  • Select a filter for aging time calculation (Resolved, Closed)

  • Change

    • Prefix

  • Problems

    • Select a filter for aging time calculation (Resolved, Closed)

  • Releases

    • Prefix

  • Risks

    • Prefix

  • Tasks

    • Prefix

  • Knowledge Base

    • Prefix

  • Sets the starting point for job duration calculation

    Options available: From First Access Time and From Approval Time.

    Default Job Active Duration (Hours, Minutes)

    Enter values (dropdown)

    Sets the default time for which a CLI job will remain active.

    Default: 0 hours 30 minutes.

    Default Job Access Count (0 is unlimited)

    Enter a numeric value

    Defines how many times a user can access the job. Setting 0 allows unlimited access.

    Choose the registered API that handles the approval request or status updates.

    Method

    Select HTTP method

    Supported methods: GET, POST, etc., depending on your API design.

    Endpoint

    Enter the API endpoint.

    The complete endpoint path for the selected method.

    Example: /api/approval/start.

    Content Type

    Select content type

    Usually, application/json defines the format of the request payload.

    Content for CLI Jobs / Upload Jobs

    Enter the payload with macros.

    JSON structure with macro variables (e.g., @@@job_name@@@, @@@approval_status@@@) passed during the job request.

    Expected Response for CLI / Upload Jobs

    Enter response format

    Define the expected response from the API for a successful status update or result pushback.

    Action

    Description / Example

    Enable Ticket Creation for Out-of-Warranty Assets

    Click to turn on/off the toggle button.

    When enabled, the system allows ticket creation for assets that are out of warranty. Example: If disabled, users cannot raise support tickets for laptops whose warranty has expired.

    Enable Ticket Creation for Out of AMC Assets

    Click to turn on/off the toggle button.

    Ensures tickets cannot be raised for assets that are not under an active Annual Maintenance Contract (AMC). Applies to both Self-Service and Technician Portals. Example: If enabled, a user cannot raise a ticket for a printer that is not covered under AMC.

    Enable Ticket Creation for Expired User Contracts

    Click to turn on/off the toggle button.

    Restricts users with expired contracts from raising new tickets. The system validates the contract status automatically. Example: If a user’s support contract expired last month, they will not be able to submit new tickets.

    Label

    Action

    Description / Example

    Resolved tickets auto-close after the 1st SLA Business Hour in

    Select the duration using Business Days and Hours

    Defines when a ticket in the Resolved status should be automatically closed. The countdown begins from the first business hour after resolution. Example: 2 Business Days, 1 Hour → Ticket will close after completing this duration within defined business hours.

    Select filter for aging time calculation

    Label

    Action

    Description/ Example

    Idle Session Timeout (Minutes)

    Enter a value (dropdown)

    Defines how long a CLI session remains active without any interaction.

    Example: 15 minutes.

    Active Duration Begins

    Label

    Action

    Description/ Example

    Disable Upload Jobs

    Toggle ON/OFF

    When enabled, all Upload Jobs are blocked from execution. Used to restrict unapproved config pushes.

    Label

    Action

    Description/ Example

    Disable CLI Jobs

    Toggle ON/OFF

    Prevents execution of CLI-based configuration changes through the system interface.

    Label

    Action

    Description/ Example

    Approval Method

    Select from the dropdown.

    Choose how approval requests are handled.

    Options include:

    · Third Party Integration: Approval is managed via an external system through API.

    · Use Infraon Change Request: Uses Infraon's native Change Management module for CAB-based approval.

    Select API

    Label

    Action

    Description/ Example

    Content for Job

    Define response body

    Typically includes the job name, approval status, and change ID.

    Example:

    {

    "job_name": @@@job_name@@@,

    "approval_status": "@@@approval_status@@@",

    "change_id" : @@@change_id@@@

    }

    Disable Requester 2FA = Enabled

    The 2FA toggle in the requester’s account settings is disabled. Requesters cannot activate two-factor authentication (2FA) on their accounts.

    Admin has disabled requester 2FA for the organization → requesters see the toggle as disabled.

    Disable Requester 2FA = Disabled

    The 2FA toggle in the requester’s account settings is enabled, allowing requesters to set up and use two-factor authentication (2FA).

    Module Formatting

    CLI Jobs

    NCCM Module Configurations

    Disable Upload Jobs

    Disable CLI Jobs

    Create Approval Request / Get Approval Request Status / Update Job Result

    Update Approval Status

    Disable SSP 2FA

    Choose the ticket status from the dropdown.

    Select from the dropdown.

    Select from the dropdown.

    Admin allows requester 2FA → requesters can enable 2FA for their accounts.

    Publish End Date
  • Status (Ongoing/Expired)

  • Actions (Edit/Delete)

  • Publish End Date*

    Select date & time

    Defines when the announcement expires and is no longer visible. Example: May 15, 2026, 12:00 PM

    Associated Change

    Select from the dropdown

    Links the announcement to a specific change record. This makes announcements visible within the module.

    Users

    Select users

    Defines specific users who can view the announcement. If not selected, the announcement is visible to all users.

    Teams

    Select teams

    Limits visibility to selected teams. Useful for targeted communication within specific groups.

    User Tags

    Select tags

    Filters visibility based on user tags. Example: IT Team, Support Team

    Requester Tags

    Select tags

    Defines visibility for requesters based on assigned tags.

    Requesters

    Select users

    Allows selecting specific requesters who can view the announcement.

    Add Announcement

    Click button

    Saves the announcement and publishes it based on the configured schedule.

    Announcement Message*

    Input text (Rich text editor)

    Enter the announcement content to be displayed to users. Supports formatting such as bold, lists, and links. Example: Scheduled server maintenance on May 15 from 2 AM to 4 AM.

    Publish Start Date*

    Select date & time

    How does it work?

    • Announcements can be associated with a Change, allowing them to be viewed within the Change panel.

    • Announcement visibility and lifecycle are fully controlled by date and configuration settings.

    Add Announcement

    • Mandatory fields: Announcement Message, Publish Start Date, Publish End Date

    • If no visibility configuration is defined, the announcement is visible to all users.

    Defines when the announcement becomes visible to users. Example: May 07, 2026 11:00 AM

    and click
    Add Metric
    .
  • You can create SLA metrics for the Ticket, Request, and Change modules.

  • Metric Details | Add Metric

    Label
    Action
    Description / Purpose

    Name*

    Enter a unique metric name

    Identifies the SLA metric within the selected module. This name is used when associating the metric with an SLA profile and must be unique within each module. Example: First Response SLA

    Criticality

    Select from the dropdown

    Start Conditions | Add Metric

    Start Conditions define when the SLA metric calculation begins. The SLA timer starts only when the configured conditions are satisfied.

    Label
    Action
    Description / Purpose

    Start Condition Type

    Select from the dropdown

    Determines the rule used to initiate the SLA metric.

    • Matches: Starts the SLA when defined conditions are met.

    • Creation Time: Starts the SLA immediately when the record is created.

    Field

    Select from the dropdown

    Other Conditions | Add Metric

    Label
    System Behavior
    Description / Example

    Start Conditions

    Initiates SLA time calculation when the defined condition is satisfied.

    This section defines when SLA tracking should begin for a record (Ticket, Request, Change, or Task). The SLA timer starts only when the configured condition evaluates to true. Multiple conditions can be combined using AND / OR logic, including State and Status (workflow-based) conditions.

    Example: Start SLA when State = In ProgressAND Status = Analysis. SLA tracking begins only after both conditions are met.

    Close Conditions

    Stops SLA time calculation and completes the SLA metric.

    Once all required conditions are configured, click Submit to save the metric and apply the defined rules.

    An SLA Response Metric can be configured to start when a Ticket State changes to Open AND the Status is Analysis. The SLA timer pauses when the state moves to On Hold, resumes when it returns to In Progress, and stops when the state changes to Closed.

    Add Metric

    application/x-www-form-urlencoded
  • txt/plain

  • APIs use authorization to secure client requests accessing data. While integrating third-party APIs, these credentials are provided by the respective API provider. Based on the API, you can select one of the below Auth Types:

    • API Key - Uses a key-value pair in the API's request headers or query parameters.

    • Basic Auth - Uses a verified username and password with the request.

    • Custom Auth - Uses token-based authorization that requires CSRF URL, token, key, username, and password with the request.

    • No Auth - Uses when there is no authorization to request data.

    • Requests

    • Sites

    • Technicians

    • Assets

    • Worklog

    It enables external applications or systems to receive real-time updates when specific events occur in Infraon workflows. It facilitates unified automation and communication between Infraon and third-party tools by invoking a registered API when triggered by workflow conditions.

    It allows users to:

    • Register external APIs to be invoked during a workflow transition (such as when a ticket moves from Open → In Progress, etc.)

    • Enable or disable webhook responses for specific workflow actions.

    • Automate actions like sending notifications, updating external systems, or triggering remote scripts without manual intervention.

    • Go to Infraon Configuration -> General Settings -> API Registration

    • Click the 'Add API' button and refer to the table below for more details:

    Label

    Action

    Description / Example

    Name

    Enter a name

    It helps identify the integration's purpose, especially when managing multiple APIs in Infraon. This will display the name for the API integration you're configuring.

    Example: JIRA, ServiceNow, etc.

    Content Type

    • API Key - Auth Key, Auth Value, and Add Key to (Header/Query)

    • Basic Auth - Username and Password

    • Custom Auth - Token details, Key, Request Type (GET, POST), Username, and Password

    • No Auth - No credentials required.

    Once all the parameters are added, click 'Submit' to add the API. APIs can be edited or deleted using the respective icons.

    API Supported Operations

    Webhook Handler for Workflow

    Instructions to 'Add API'

    Auth-Type Fields

    Specify a unique name for the SMS gateway configuration for easy identification and management. Example: SMS Gateway Demo

    URL

    Enter URL

    Specify the SMS provider's API endpoint URL for sending SMS requests from the platform. Example: www.fast2sms.com/dev/bulkV2

    Add Country Code

    Enable/Disable Toggle

    Automatically appends the configured country code to recipient mobile numbers before sending SMS messages.

    Use GET Request

    Enable/Disable Toggle

    Sends the SMS request using the HTTP GET method instead of the default POST method, depending on the provider API requirement.

    Use HTTPS

    Enable/Disable Toggle

    Enables secure HTTPS communication for encrypted SMS API requests and secure data transmission.

    Status Code

    Enter Status Code

    Specify the expected success response code returned by the SMS provider after successful SMS submission. Example: 200

    Send SMS Individually

    Enable/Disable Toggle

    Sends SMS messages separately to each recipient instead of processing all recipients in a single bulk request. Useful for providers requiring individual message delivery.

    Specify the parameter value or dynamic system variable used during SMS processing. Example: gateway_sms_recipients, gateway_sms_message, API tokens, route values, or content types.

    Pass To Header

    Enable/Disable Toggle

    Sends the configured parameter in the API request header. Typically used for authorization tokens, API keys, or content-type configurations.

    Pass to query params

    Enable/Disable Toggle

    Sends the configured parameter as a URL query parameter in the SMS API request.

    Add

    Click Add

    Adds a new request parameter row to configure additional API fields required by the SMS provider.

    Delete

    Click the Delete Icon

    Removes the selected request parameter from the SMS gateway configuration.

    Specify a unique name for the SMPP gateway configuration for identification and management purposes. Example: SMPP Gateway Demo

    SMPP Hostname

    Enter Hostname

    Specify the hostname or server address provided by the SMPP service provider for establishing SMS communication. Example: mail.domain.extn

    SMPP Host Username

    Enter Username

    Specify the username provided by the SMPP gateway provider for authentication and connection establishment.

    SMPP Host Password

    Enter Password

    Specify the password associated with the SMPP account used for secure authentication.

    SMPP System ID

    Enter System ID

    Specify the SMPP System ID provided by the SMS vendor or telecom provider for gateway identification.

    SMPP Host Port

    Enter Port

    Specify the communication port number used for SMPP connectivity between the platform and the SMS provider. Example: 443

    TRX Sessions

    Enter the number of TRX sessions to establish with the SMPP gateway.

    Specifies the number of concurrent SMPP transceiver (TRX) sessions to establish with the SMS gateway. The default value is 1. Configure multiple TRX sessions to distribute SMS traffic across multiple active SMPP connections, improving message throughput, connection stability, and SMS delivery performance in high-volume messaging environments.

    Example: Configure 4 TRX Sessions to establish four concurrent SMPP connections, enabling the SMS gateway to process high-volume SMS traffic more efficiently.

    Specify the corresponding DLT parameter value provided by the SMS gateway or telecom operator.

    Add

    Click Add

    Adds additional DLT parameter fields for configuring multiple regulatory or provider-specific parameters.

    Delete

    Click the Delete Icon

    Removes the configured DLT parameter from the SMPP gateway configuration.

    Specify a sample SMS content to verify message delivery and SMS gateway functionality. Example: Test SMS from Infraon Infinity

    Primary

    Click Primary

    Tests the SMS delivery using the Primary SMS Gateway configuration configured in the module.

    Secondary

    Click Secondary

    Tests the SMS delivery using the Secondary SMS Gateway configuration when secondary gateway settings are enabled.

    Invoice No., Part No., Cost, Purchase Date, Depreciation Type, Salvage Value, Currency

    Location Properties

    Location Hierarchy, Country, State, City, Pin Code, Landmark, Flat House No Building Company, Area Colony Street Sector Village, Zone, Region, Division, Location Code, Latitude, Longitude

    Assignment

    Department, Managed By Tag, Managed By, Used By

    Software Properties

    Publisher, Version, Software Type, Software Category, Platform, Size, Note

    CPU speed, Logical Processors, CPU Stepping, CPU Cores Count

    BIOS Properties

    Manufacturer, BIOS Version, Install Date

    Disk Properties

    Drive Name, Drive Type, Drive Capacity, Drive Filetype, Drive Serial Number

    Monitor Properties

    Monitor Type, Refresh Rate, Monitor Serial Number, Resolution

    Keyboard Properties

    Keyboard Type, Keyboard Serial Number

    Mouse Properties

    Mouse Serial Number, Number of Buttons

    For example, items like routers and firewalls can be categorized under 'Network'.

    Select the toggle button to enable the functionality

    Enabling the toggle button will trigger a notification for the end user to accept/deny the allocation of the asset.

    Send bulk allocation email / Send bulk deallocation email

    Select the toggle button and correspondingly add the trigger notification timer.

    Unified notification system for handling large-scale allocations/ deallocations across various asset categories.

    The allocation/ deallocation email process begins when an asset is assigned to a user for the first time. A single email containing all allocated asset information from that specific period will be sent to the De-allocation or vice versa.

    Notify End Users on Asset De-allocation

    Select the toggle button to enable the functionality

    Enabling the toggle button will trigger a notification for the end user to accept/deny the deallocation of the asset.

    Notify Owner on Warranty and AMC expiry

    Select the toggle button and correspondingly add the trigger notification timer.

    Turn on the toggle and set the alert date. This will automatically notify asset owners when their warranties and AMCs are about to expire.

    Notify owner on discovery of blacklisted Application

    Select the toggle button to enable the functionality

    The owner of the IT asset will be notified via email upon discovery of a blacklisted application.

    Notify Owner on Hardware Changes

    Click to turn on/off the toggle button

    When enabled, the system notifies the asset owner whenever there are hardware changes detected in the asset.

    In addition, administrators can configure notifications to also include a requester along with the owner. Filter allows you to specify which hardware components should trigger notifications (e.g., CPU, memory).

    Note: USB component changes are excluded by default, preventing unnecessary alerts for minor modifications.

    Example: If memory is upgraded in a server, both the owner and the selected requester will receive a notification. However, if only a USB device is added/removed, no notification will be sent.

    Notify Owner on Software Change

    Select the toggle button to enable the functionality and choose users to notify

    When enabled, the system notifies the asset owner (and selected users) via email whenever software is installed or uninstalled on the asset. Notification content is based on the configured Software Changes template.

    Notify on Inactive Inventory Agent

    Select the toggle button to enable the functionality, set the inactivity duration (in days), and choose users to notify

    When enabled, the system sends an email notification to the selected users if the asset’s inventory agent remains inactive for the specified number of days.

    Custom Field

    Custom Fields allow IT admins to create and manage asset-specific metadata fields that go beyond the default system-defined attributes. These fields enable teams to tailor asset records to suit organizational, compliance, or operational needs.

    It is designed to support:

    • Organization-specific field tracking (e.g., Warranty Location, Department Tag, Device Owner Remarks)

    • Flexibility in defining Text, Date, Dropdown, or Numeric fields

    Choose from the dropdown

    This defines the format of data being sent to the API.

    Options: application/JSON, text/plain, multipart/form-data, and application/xml.

    Authentication Type

    Choose from the dropdown

    This defines the method by which the API call is authenticated. The correct type must be selected based on the API provider’s documentation.

    Options: API Key, Basic Auth, Custom Auth, and No Auth.

    Username

    Enter your username

    The username is used to authenticate API calls using authentication methods like Basic Auth. This typically refers to your registered email address or username in the third-party platform.

    Example: When integrating Jira, this would be your Atlassian email ID, username@example.com.

    Password

    Enter your password

    This field is used along with the username to authenticate the API. If you're using Basic Auth, this is often your account password, or an App Password generated from the external platform’s security settings—especially in platforms like Jira or GitHub, where regular passwords are restricted.

    Is Base64 Encode

    Toggle ON/OFF

    When enabled, Infraon will automatically convert the username and password into a Base64-encoded string for APIs requiring that format (standard with Basic Auth).

    Secret Key

    Enter the token/key.

    The secret key refers to an API token or access key required for secure authentication. It replaces or supplements the password in many modern APIs. You can generate this token from the API/Developer settings section of platforms like Jira, Freshdesk, or Salesforce.

    Example:

    cJXbGJI2y1oIh3IsnTI5jR6VCJ9....

    Client ID

    Enter the client ID.

    The Client ID is a unique identifier assigned when registering your application in an OAuth2-compliant platform (e.g., Azure, Google, Atlassian).

    Example: 11853234773……...

    Base URL

    Enter API base URL

    This is the root URL of the third-party API to which Infraon will send requests. It forms the foundation of all endpoint calls.

    For Jira, it might look like: https://yourdomain.atlassian.net/rest/api.

    Enable Webhook Response

    Toggle ON/OFF

    This option allows Infraon to receive real-time call-back responses from external platforms via webhooks. It ensures Infraon can process workflow actions or status updates triggered externally when enabled.

    For instance, if Infraon creates a ticket in Jira and Jira later changes the ticket status, enabling webhook response ensures that Infraon receives and updates the ticket status automatically.

    Description

    Optional input

    You can provide an internal description to explain the purpose of this integration. This is not used for functional purposes but is helpful for clarity and documentation.

    Example: Integration for auto-creating tickets in Jira.

    Header Parameter

    Enter key-value pairs

    Some APIs require additional headers for authentication or custom handling. Here you can define header keys (e.g., Authorization) and assign static values or macros.

    Add to Query Parameter

    Toggle ON if needed

    When enabled, the header parameter is attached to the URL as a query string instead of being sent in the header.

    Reusability across different asset categories

  • Uniform data collection and visibility across modules like IT Assets, Fixed Assets, and CMDB

  • Custom Fields ensure that asset data models are scalable and relevant to different business environments.

    Below is a detailed breakdown of the elements shown on the Custom Field listing screen:

    Label

    Action

    Description / Example

    Search

    Type at least three characters to perform a search

    Performs a free-text keyword search on custom field labels.

    Example: Asset ID, Owner Group

    Filter

    Custom fields allow you to extend the default asset metadata by creating organization-specific attributes. These fields can be added to both Assets and Resources, with field type options and properties varying depending on the selection.

    Begin by selecting the type of entity the custom field will be associated with:

    • Asset

    • Resource

    Label

    Action

    Description / Example

    Property

    Select from the dropdown

    Choose the property group the custom field belongs to. Options: Common, Procurement, OS, CPU, BIOS, Disk, Monitor, Keyboard, Mouse, Cost, Assignment, etc.

    Field Type

    Select from the dropdown

    Based on the selected Field Type, different configurations appear on the screen. See below for type-specific settings.

    Label

    Action

    Description / Example

    Field Type

    Select from dropdown

    Available options: Text, Phone Number, Email, and Number.

    Label

    Enter custom field label

    Each field type triggers a specific form layout. Below is a detailed breakdown.

    Based on the selected Field Type, additional configuration fields appear. Each type serves a unique purpose. The details below explain the labels and their usage in a clear format for end users.

    Email / Phone Number / Text | Configuration

    Field

    Purpose

    Placeholder

    This is the default hint text displayed in the field before the user inputs any value. It auto-fills based on the field type (e.g., “Enter your email”) but can be edited to provide more specific guidance.

    Validation Rules

    This allows you to add descriptive text that instructs users on what type of input is expected. For example: “Must be a valid company email address.”

    Regex

    Number | Configuration

    Field

    Purpose

    Min

    Sets the minimum allowable value for the number field. This prevents users from entering values below the defined threshold.

    Max

    Sets the maximum allowable value. Useful for setting limits like asset quantity, license count, etc.

    Validation Rule

    Drop-down | Configuration

    Field

    Purpose

    Label

    Visible name for each dropdown option. Should be human-readable (e.g., “HR Department”).

    Value

    Backend reference for that label (e.g., HR01), used for automation, filters, and rules.

    Action

    Text Area | Configuration

    • Designed for long-form input (e.g., notes, remarks).

    • Uses the same configuration layout as Email/Text fields.

    • Best used for optional descriptions or unstructured inputs.

    Checkbox / Radio | Basic Details

    Field

    Purpose

    Label

    The name shown to users for the option. Use clear wording like “Yes”, “No”, “Internal Use Only”, etc.

    Value

    This is the stored backend value for the label (e.g., “Y” for Yes, “N” for No). Used in reports and rule automation.

    Date / Date & Time | Configuration

    • These types do not have field-specific validations like Min/Max or Regex.

    • A placeholder auto-fills with a default hint (e.g., "Select a date").

    • All common options (like category mapping, toggles for mandatory/unique) are applicable.

    Custom fields can be linked to categories or sub-categories to determine their visibility and usage.

    Option

    Purpose

    Common Custom Field

    When enabled, this makes the field available across multiple selected categories. Best for generic fields like “Department” or “Asset Tag.”

    Category/Sub-Category

    Select the target group where the field should be active. Fields in a Category propagate to all sub-categories. Fields added only to a Sub-Category are restricted there.

    Mandatory

    What Do You See on the Screen?

    • All created custom fields will appear as selectable options in the Category Template > Fields tab.

    • Deleted fields cannot be recovered.

    • Fields are global and can be reused across multiple modules or templates.

    Add a Custom Field

    Duplicate field labels or property-field combinations are not allowed. Each custom field must be unique.

    Steps to Add a Custom Field

    If Asset is Selected

    If Resource is Selected

    Field Type-Based Configuration

    Add Related Categories

    • Avoid using duplicate labels or field names across categories to maintain clarity and avoid conflicts.

    • Fields are global once created but are only active in the categories they are mapped to.

    Defines the metric's priority level. This helps categorize SLAs based on business impact and urgency. Example: High

    Description

    Enter description

    Provides context for what the metric measures. Useful for administrators to understand the intent of the SLA metric. Example: Tracks response time for high-priority tickets

    Specifies the attribute that is evaluated to trigger the SLA start.

    • State: Tracks lifecycle stages such as Open, In Progress, and Resolved.

    • Status: Tracks workflow-specific stages within a module.

    Operator

    Select from the dropdown

    Defines how the selected field is evaluated against chosen values.

    • in: SLA starts when the field matches selected values.

    • not in: SLA starts when the field does not match selected values.

    Value

    Select from the dropdown

    Specifies the value(s) that must satisfy the condition to start the SLA. State example: In Progress Status example: Analysis

    Workflow

    Select workflow

    Displayed only when Status is selected. Determines which workflow’s statuses are applicable for the condition. Example: Ticket Workflow

    Status Value

    Select status

    Lists statuses associated with the selected workflow. SLA starts when the record transitions to the selected status. Example: Respond

    Logical Operator

    Select AND / OR

    Used to combine multiple start conditions.

    • AND: All conditions must be met to start SLA.

    • OR: Any one condition can start the SLA.

    Add Condition

    Click select

    Allows adding additional conditions to build complex SLA start logic using multiple fields and operators.

    This section defines when SLA tracking should be considered successful. Once the close condition is met, the SLA timer stops, and the SLA outcome is finalized. Close conditions support the same multi-condition logic as Start Conditions. Example: Close SLA when State = Resolved OR Status = Closed. Once satisfied, SLA is marked as completed and recorded in SLA reports.

    Metric calculation will restart on enabling this toggle

    Restarts SLA calculation if the close condition is re-triggered after completion.

    When this toggle is enabled, the system allows SLA calculation to restart automatically if the record transitions back to a state that re-triggers the close condition logic. This is useful for workflows where records can move back and forth between states.

    Example: A ticket is closed (SLA stops), then reopened. With this toggle enabled, SLA calculation restarts instead of remaining in a completed state.

    Pause Conditions

    Temporarily suspends SLA time calculation without resetting elapsed time.

    Pause Conditions define scenarios in which SLA time should not be counted, even when the SLA is active. While paused, the SLA timer is frozen. This is typically used for waiting or dependency-based states.

    Example: Pause SLA when State = On Hold or Status = Waiting for Customer. SLA time stops accumulating until a resume condition is met.

    Resume Conditions

    Resumes SLA time calculation from the paused duration.

    Resume Conditions specify when a paused SLA should continue tracking time. The SLA resumes from where it was paused, without resetting the previously elapsed duration.

    Example: Resume SLA when State = In Progress after being on hold. SLA continues counting from the paused time.

    Cancel Conditions

    Permanently terminates SLA calculation and excludes it from compliance.

    Cancel Conditions define scenarios where the SLA is no longer applicable. Once cancelled, the SLA stops permanently and is not considered for SLA breach or compliance metrics. This action cannot be reversed automatically. Example: Cancel SLA when State = Cancelled, Duplicate, or Invalid Request. SLA is removed from evaluation and reporting.

    Change

    My Profile

    When you click the Profile icon (top-right corner of the platform), a dropdown menu appears. This menu provides quick access to personal settings, status control, log history, shortcuts, and session actions.

    Profile Menu | Basic Details

    Label
    Description
    Example / Notes

    This page lets users manage their personal profile settings, including basic details, password, preferences, signature, attendance options, approvals, and security settings like 2FA. All changes apply only to the logged-in user.

    Users can update basic profile details, including full name, gender, contact number, time zone, and email address. This section also supports changing the profile picture and enabling Two-Factor Authentication (2FA) for secure login.

    General | Account Settings

    Label
    Action
    Description / Example

    Users can update their login password by entering their current password and setting a new one. This is used to maintain account security and should be updated periodically or when credentials are compromised.

    Change Password | Account Settings

    Label
    Action
    Description / Example

    Adjust personal viewing and language settings. Users can define how many records appear per page and select their preferred interface language. These preferences apply only to the logged-in user and do not affect global system settings.

    Use this section to create and manage email signatures that automatically append to communications sent from the platform. Multiple signatures can be added and stored for different use cases (e.g., support, escalation, internal).

    Add Signature | Account Settings

    Label
    Action
    Description / Example

    This section stores the user's professional details and organizational mapping. It helps in defining the user’s role, department, experience, skills, business entity, and notification contact details within the platform.

    Field Details| Account Details

    Label
    Action
    Description / Example
    • After entering details, click Submit to save changes.

    • Updated details will reflect across dashboards, workflows, and reporting modules.

    This section displays your attendance logs for selected date ranges. Users can view clock-in/clock-out times, total working hours, remarks, and reasons for leave. You can filter records, review daily entries, and verify time logs based on system-recorded data.

    Label
    Action
    Description / Example

    The Pending Approvals section displays requests that require the user’s action—typically approval or rejection of workflow items such as attendance logs, requests, or task submissions.

    This page only shows items assigned to the logged-in user as an approver. If no items require action, the page remains empty.

    This page displays the attendance records of users who report to you. It includes login/logout times, total and effective working hours, remarks (Worked/Absent), and location-based fields such as latitude, longitude, and distance from the base. You can search by username, apply date-range filters, and review daily logs to monitor team activity and ensure compliance.

    Use Cases

    The CMDB (Configuration Management Database) module in Infraon platform is designed to maintain a structured repository of all configuration items (CIs) within an IT environment. These CIs can include assets such as laptops, servers, routers, and applications, along with their relationships and dependencies.

    A Business Rule in Infraon defines an automation logic that performs actions when certain conditions are met. In the CMDB module, business rules can be applied to assets for activities such as:

    • Auto-updating tags and properties

    • Assigning ownership

    Select a field → choose a condition → enter value

    Filter options include:

    • Fields: Label, Type

    • Conditions: equal to, not equal to, contains, not contain, in, not in

    Example: Filter where Type = Text

    Label

    View only

    Displays the name of the custom field.

    Example: Customize Asset ID, Branch Code

    Property

    View only

    Category this field belongs to (e.g., Custom Property, Procurement Property)

    Field Type

    View only

    Data type assigned to the field.

    Example: Text, Date, Dropdown, Email, etc.

    Type

    View only

    Denotes the module or entity this field applies to.

    Example: Asset, Contract, Software

    All Related Categories

    View only

    Lists the number of asset categories using this custom field.

    Example: 2, 3, etc.

    Action Icons

    Edit

    Click pencil icon

    Opens the custom field in edit mode to change label, field type, or related categories

    Delete

    Click trash icon

    Deletes the custom field. This action is only allowed if the field is not in active use.

    Choose the type of input expected for this field.

    Options: Text, Phone Number, Email, Date, Date & Time, Checkbox, Radio, Text Area, Drop Down, Number.

    Label

    Enter custom field label

    Example: Asset Location Code, Internal User Email, Device Category, etc.

    Example: Resource Owner, Vendor Email

    Enables admins to define pattern-based validation using regular expressions. This ensures that input strictly matches defined criteria (e.g., emails must follow abc@domain.com).

    Error Text

    This is the message shown to the user when the input fails validation. It should clearly explain what went wrong.

    Example: “Please enter a valid email format.”

    Optional message or description that informs the user what the number field is intended for or how to fill it.

    Add multiple entries using "+" and remove using delete icon. Avoid duplicating labels/values.

    Toggle this ON to enforce field entry during asset/resource creation.

    Unique

    Prevents duplicate values. Useful for fields like Serial Number, Asset ID, or Employee ID.

    Disable

    Temporarily hides the field from being used without deleting it.

    Action Icons

    Add

    Confirms and applies the field-to-category association. You can add multiple mappings.

    Delete

    Removes the field from a specific category. Does not delete the field entirely.

    Email

    View Only

    Shows the registered email address used for login and notifications.

    Gender

    Select Option

    Choose the gender preference from Male, Female, or Other.

    Phone Number

    Add / Edit

    Enter your primary mobile number with the country code.Example: +974 4412 3456.

    Timezone

    Select Dropdown

    Set your local timezone for accurate timestamps.Example: (GMT+05:30) Asia/Kolkata [IST].

    Landline

    Add / Edit

    Enter the official landline contact number (optional).

    Contact Extension

    Add / Edit

    Add an internal extension number if applicable (optional).

    Two-Factor Authentication (2FA)

    Enable / Disable

    Enable enhanced security using TOTP via an authenticator app.

    Submit

    Save Changes

    Applies and saves profile updates.

    Submit

    Save changes

    Applies the password update after validation

    Editor (Text area)

    Type / Format

    Add and format signature content. Supports text styling, hyperlinks, and images.Example: Name, role, contact details, company logo.

    Formatting Toolbar

    Bold / Italic / Underline / Alignment / Insert Image

    Apply styling and insert media for professional formatting.

    Save / Close

    Save or Exit

    Save changes or close the editor without saving.

    Defines the functional role assigned within the system hierarchy. Example: Service Engineer

    Department

    Select from the dropdown

    Associates the user with a specific department. Used for routing & reporting. Example: Support / Operations / Engineering

    Experience Months

    Enter value (number)

    Total months of professional experience. Helpful for skill-mapping. Example: 24

    Experience Years

    Enter value (number)

    Total years of professional experience. Example: 3

    Skills

    Select from the dropdown

    Define skillsets for resource assignment & workload mapping. Example: Networking / Troubleshooting / Linux

    Notify Email

    Enter email

    Email address used for task/ticket notifications. Example: john.doe@infraon.com

    Notify Phone No(s)

    Enter phone

    Phone number used for SMS/voice alerts. Example: +91 987XXXX210

    Business Entity

    Enter or select

    Indicates the business unit to which the user belongs. Example: Global Support

    Business Segment

    Enter text

    Categorizes the user under a business division. Example: IT Operations

    Partner Name

    Enter text

    Used when the user belongs to a partner organization. Example: TechSolutions Pvt Ltd

    Subsidiary

    Enter or select

    Maps the user to a subsidiary entity in multi-org setups. Example: Infraon India Pvt Ltd

    System-recorded clock-in time. Example: 03:52 PM

    Out

    View

    System-recorded clock-out time.Example: 06:41 PM

    Effective Hours

    View

    Actual productive time calculated from first clock-in to last clock-out after break deductions. Example: 1 hr, 39 min

    Total Hours

    View

    Gross working hours, including all logged sessions. Example: 2 hr, 48 min

    Remarks

    View

    Work status based on attendance. Example: Worked / Absent

    Latitude / Longitude

    View

    Shows captured geo-coordinates (if location tracking is enabled).

    Login Type

    View

    Indicates login source. Example: Remote / Base / Mobile

    Distance from Base

    View

    Distance from the assigned base location at login time.

    Approval Status

    View

    Shows if attendance adjustments are pending approval. Example: Approved / Pending

    Reason

    View

    Shows remarks for absence or manual edits. Example: No Reason Provided

    Filter (Last 30 Days)

    Select Filter

    Filters attendance records based on date range. Example: Today / This Month / Custom Range

    User Info (Name & Email)

    Displays the logged-in user’s basic profile details.

    Shikar – shikar.srivastav@infraon.io

    Clock In / Clock Out

    Used to log working hours for attendance tracking. Switching to Clock Out ends the current active session.

    Shows the timestamp of the last action.

    View Logs

    Opens attendance/activity logs to review login history and time entries.

    View daily login/logout logs.

    Status

    Shows the current availability status. Users can switch between statuses such as Active, Away, and Busy, depending on configuration.

    Current Status: Active

    Account Settings

    Navigates to the Account Settings page, where users can update profile details, security settings, preferences, and attendance config.

    Click here to know more.

    Keyboard Shortcuts

    Opens a pop-up showing available keyboard shortcuts for quick navigation.

    User: g+u, Requester: g+r, etc.

    Logout

    Logs the user out of the platform.

    Redirects to the login page.

    Privacy Policy / Terms of Service

    Links to compliance and platform usage policies.

    External redirect.

    Profile Picture

    Upload / Change

    Upload or modify your avatar displayed across the platform.

    Full Name

    View / Edit

    Current Password*

    Enter existing password

    Required to verify identity before applying changes

    New Password*

    Enter new password

    New Signature

    Click

    Opens a pop-up window to create a new signature.

    Title

    Enter text

    Designation

    Enter text

    Stores the job title used internally. Example: Frontdesk Engineer

    Organization Role

    Date

    View

    Shows the specific date of attendance entry. Example: 19 Wed, Nov 2025

    In

    Account Settings

    General

    Change Password

    User Preferences

    Signature

    Information

    Attendance

    Pending Approvals

    Sub-ordinates Attendance

    Update the display name associated with your account. Example: Shikar.

    Define a new secure password for login

    Name of the signature template.Example: "Support Team Signature"

    Enter text

    View

    Enabling workflows based on asset data

  • Triggering changes when predefined criteria are satisfied

  • This use case demonstrates how to automatically assign values to discovered assets (such as Asset Tag, Owner, and User Tag) based on their IP Address. This helps:

    • Automatically categorize assets during discovery

    • Assign ownership without manual intervention

    • Maintain consistency in asset metadata

    An organization wants to automatically assign specific properties to all IT assets discovered within a certain IP address range. For example:

    • Any device within the IP range 192.168.50.1 should be tagged as an HP asset.

    • The technician Alex should be assigned as the asset owner.

    • The asset should also be grouped under the DevOps user tag for better filtering and reporting.

    Field

    Value

    Description

    Module

    CMDB

    Selects the CMDB module to apply the rule to asset-level records.

    Type

    Field

    Operator

    Value

    Description

    IP Address

    In Range

    192.168.50.1

    The condition checks if the asset IP matches this value (or falls within a range).

    Field

    Value to Set

    Description

    Asset Tag

    HP

    Automatically tags the asset with “HP” to classify it by vendor or type.

    Owner/Technician

    Alex

    Once the rule is enabled:

    • Infraon continuously monitors assets being discovered or updated in the CMDB.

    • If an asset's IP address matches the defined rule (192.168.50.1), the system automatically updates the configured fields (Asset Tag, Owner/Technician, User Tag).

    • This ensures that the asset is properly categorized and assigned without manual input.

    to view.

    This use case explains how to automatically calculate and update the End of Life (EOL) date for assets using the Model Year field. It is useful when acquisition or purchase dates for existing assets are unavailable.

    The business rule evaluates the asset category and applies a predefined lifecycle period to determine the expected EOL date.

    Example Lifecycle Rules:

    • Laptop → Model Year + 5 Years

    • Desktop → Model Year + 7 Years

    • Monitor → Model Year + 10 Years

    Use this rule to:

    • Standardize lifecycle estimation across assets

    • Automatically maintain End-of-Life values

    • Reduce manual updates for large asset inventories

    • Improve replacement planning and reporting

    • Maintain activity history for EOL updates

    • Navigate to Infraon Configuration → Infraon Automation → Business Rule.

    • Click Add Business Rule.

    In the Rule details section, enter the required information:

    Label
    Action
    Description / Example

    Rule Name

    Enter value

    Specify a name for the rule. Example: End of Life Auto-Update

    Module

    Select from the dropdown

    Under Rule Setup, define when the rule should execute.

    Field
    Action
    Description / Example

    When

    Select field

    Choose the asset category field such as Device Type.

    Condition

    Select operator

    Define which field should be updated automatically.

    Field
    Action
    Description / Example

    Then Value Update To

    Select field

    Choose End of Life.

    Reference Field

    Select field

    Once configured:

    The Software module in Infraon Business Rules enables administrators to automatically trigger notifications when specific software-related events are detected during inventory synchronization. Instead of manually monitoring software changes across managed devices, administrators can configure rules that evaluate software and asset conditions and notify the appropriate users when those conditions are met.

    Business Rules for the Software module support event-driven automation for software lifecycle activities such as software installation, uninstallation, blacklisted software detection, non-whitelisted software detection, and whitelisted software detection. Rules can also be filtered using software properties and asset attributes to ensure notifications are generated only for relevant events.

    This use case demonstrates how to automatically notify the asset owner and designated users whenever a blacklisted software application is detected on a managed Windows device during inventory synchronization. This helps administrators:

    • Detect unauthorized software immediately.

    • Improve software compliance across managed devices.

    • Notify responsible users without manual intervention.

    • Automate software monitoring using Business Rules.

    An organization wants to receive an email notification whenever a blacklisted application is detected on any Windows laptop within the Finance department.

    The administrator creates a Software Business Rule that monitors the Blacklisted Software Detected event. During inventory synchronization, whenever a matching software is discovered on a Windows device belonging to the Finance department, the system automatically sends an email notification to the asset owner and the configured administrator.

    • Navigate to Infraon Configuration → Infraon Automation → Business Rule.

    • Click Add Business Rule.

    In the Rule Details section, configure the following:

    Label
    Action
    Description / Example

    Rule Name

    Enter a value

    Specify a meaningful name for the business rule. Example: Blacklisted Software Notification

    Module

    Select from the dropdown

    Configure the conditions that determine when the notification should be triggered.

    Field
    Operator
    Value
    Description

    Event

    IN

    Blacklisted Software Detected

    Select the software event to monitor. This is the mandatory first condition and cannot be modified.

    Configure the recipients who should receive the notification when the rule conditions are satisfied.

    Field
    Value
    Description

    Then

    Notify To

    Select the notification action.

    Recipients

    Asset Owner, Administrator

    Once the rule is enabled:

    • The Inventory Agent periodically scans managed devices and synchronizes software information with the Infraon server.

    • During inventory synchronization, the Business Rule engine evaluates the detected software events against the configured rule conditions.

    • If the detected software event matches the configured Event, software filters, and asset filters, the rule is triggered.

    • The system automatically sends an email notification to the configured recipients, such as the asset owner, selected users, or user tags.

    • All rule creation, modification, deletion, and notification execution activities are recorded in the audit logs for traceability.

    The CMDB Business Rule module enables you to automatically update asset properties based on configured conditions. With Dynamic Asset Rule Re-Evaluation & Enforcement, the rule engine continuously monitors supported asset updates and re-evaluates applicable business rules whenever dependent asset attributes change.

    This feature introduces Priority and Enforcement Mode settings to control rule execution, conflict resolution, and how automated updates behave after users manually modify asset values.

    This use case demonstrates how to automatically update the Department field for assets based on their IP Address, while controlling how the rule behaves during future asset updates using Enforcement Mode.

    This helps you:

    • Automatically update asset values when matching conditions are met.

    • Re-evaluate rules when dependent asset attributes change.

    • Prevent conflicting rule execution using rule priority.

    • Control whether automated values should overwrite manual updates.

    An organization wants to automatically assign the Department field for assets whose IP address matches a predefined range.

    For example:

    • Assets with the IP Address 1.0.0.0 should automatically be assigned to the IT Team department.

    • The rule should execute whenever the asset is created or updated through discovery synchronization, API updates, manual edits, or bulk import.

    • The administrator wants the rule to update the department only if the field is currently empty by configuring the Apply If Empty enforcement mode.

    1

    Add a business rule

    Navigate to Infraon Configuration → Infraon Automation → Business Rule, and then click Add Business Rule.

    2

    Configure Rule Details

    Label
    Action
    Description / Example
    3

    Configure the condition that triggers the rule.

    Label
    Action
    Description / Example
    4

    Configure the field that should be updated when the condition is satisfied.

    Label
    Action
    Description / Example

    Once the rule is enabled:

    • The rule engine evaluates matching assets during asset creation, manual updates, discovery synchronization, API updates, and bulk imports.

    • When an asset's IP Address matches the configured value (1.0.0.0), the Department field is automatically updated to DepTestCount0.

    • Future rule execution follows the configured Enforcement Mode:

      • Apply Once executes the rule only during the initial match.

      • Enforce Always reapplies the configured value whenever the rule conditions match.

      • Apply If Empty updates the target field only when it is empty.

    • Preserve Manual Changes prevents automated updates after a user manually modifies the field.

    • If multiple rules match the same asset, the rule with the highest Precedence is applied.

    • All automated updates are recorded in the Audit Log for traceability.

    The Business Rule module in Infraon enables administrators to configure automated email notifications for asset lifecycle events. This feature sends notifications whenever assets are created or deleted, ensuring stakeholders are informed without requiring manual intervention.

    Notifications are generated only for informational purposes and do not require approval or user action. For bulk operations, the system sends a single consolidated email instead of individual emails for each asset, preventing unnecessary email traffic.

    This case demonstrates how to configure a Notification Business Rule that sends email notifications whenever assets are created or deleted.

    This helps you:

    • Notify administrators or stakeholders when assets are added or removed.

    • Receive a single summary email for bulk asset import and deletion operations.

    • Avoid email flooding during large-scale asset operations.

    • Maintain notification history and audit logs for asset lifecycle events.

    An organization wants to notify the IT Asset Management team whenever assets are created or deleted.

    For example:

    • When a single asset is added, an email containing the asset details is sent to the configured recipients.

    • When 5,000 assets are imported, the system sends one consolidated email containing the import summary and a bulk import report.

    • When a single asset is deleted, an email containing the deleted asset details is sent.

    • When 10,000 assets are deleted in bulk, only one summary email is generated after the operation completes.

    • Navigate to Infraon Configuration → Infraon Automation → Business Rule, and then click Add Business Rule.

    • In the Rule Details section, configure the following settings.

    Add Rule | Basic Details

    Label

    Action

    Description / Example

    Rule Name

    Enter value

    Specify a descriptive name for the notification rule. Example: Asset Creation Notification

    Module

    Rule Setup | When

    Configure the event that triggers the notification.

    Label

    Action

    Description / Example

    When

    Select field

    Select Event.

    Operator

    Rule Setup | Then

    Configure the notification action.

    Label

    Action

    Description / Example

    Then

    Select action

    Select Notify To.

    Recipients

    Select users or email addresses

    Use the + icon to add additional conditions and the − icon to remove conditions from the rule.

    Once the rule is enabled:

    • The selected notification event is continuously monitored by the system.

    • When the configured event occurs, the system evaluates the rule and sends an email notification to the configured recipients.

    • For single asset operations, an individual email is generated containing the asset details, user information, and operation timestamp.

    • For bulk asset import operations, the system sends one consolidated email after the import completes. The email includes the total processed records, created count, updated count, failed count, operation details, and a bulk import report.

    • For bulk asset deletion, the system sends one consolidated email after the delete job completes. The email includes the deleted asset count, operation details, and a deleted asset report.

    • The system sends only one notification per bulk operation and does not generate separate emails for every asset.

    • Notification history and audit logs are maintained to record the notification status and asset lifecycle events.

    Business Rule for CMDB

    Objective of This Use Case

    Scenario

    Configuration Steps

    Rule Setup: When Condition

    Then: Value Update To (Actions)

    You can add multiple conditions and actions using the "+" and "−" icons in the rule builder interface.

    How It Works

    • Business Rules in the CMDB apply to all discovered or imported asset records.

    • Multiple conditions can be added using logical AND.

    • Values are updated only when the condition is matched during asset data sync, update, or manual addition.

    Business Rule for Delegation Approval

    Business Rule for Model Year–Based End-of-Life

    If the Model Year is blank or if the End-of-Life value is manually entered, the automatic calculation will not be applied.

    Why Use This Rule?

    Steps to Configure the Business Rule

    Add Rule | Basic Details

    Configure Rule | Add Rule

    Configure Value | Add Rule

    Result

    • Assets with a valid Model Year automatically receive an End-of-Life date.

    • Updated values are visible in the Asset View page.

    • The Model Year field is available in CSV Import, Export, and Bulk Edit.

    Business Rule for Software-Based Notification

    Objective of the Use Case

    Scenario

    Configuration Steps

    Rule Setup: When Condition

    You can add multiple software and asset conditions using the + icon. All configured conditions must match before the notification is triggered.

    Then: Notification Action

    Notifications use the default email template, which can include asset metadata through configurable template variables.

    How It Works

    • Software Business Rules are evaluated only during Inventory Agent synchronization.

    • Rules are executed only when they are enabled. Disabled or deleted rules are ignored.

    • Software notification configurations previously available under Asset Category

    Dynamic Asset Rule Re-Evaluation & Enforcement

    Objective of the Use Case

    Scenario

    Configuration Steps

    How It Works

    Asset Creation and Deletion Email Notifications

    Objective of the Use Case

    Scenario

    Configuration Steps

    How It Works

    Customer Registration

    The Customer Registration module enables organizations operating in MSP (Management Service Provider) mode to create and manage customer accounts within the Infraon platform.

    This module is required when a single organization manages multiple customers (tenants) and needs:

    • Logical segregation of customer data

    • Customer-wise asset mapping

    • Customer-specific user access

    • License allocation and tracking per customer

    • Entity-level structuring under a customer

    Customer Registration ensures that assets, users, licenses, reports, dashboards, and monitoring configurations are mapped and isolated based on the selected Customer or Entity.

    When MSP is disabled, this module is not available, and the organization operates in a single-tenant model.

    Customer Registration | Basic Details

    Label
    Action
    Description / Example
    • To create a new customer, click Add Customer on the top panel.

    • In the Add Customer sidebar, provide the required information across the following sections:

      • Customer Details

      • Entity Details

      • Settings

    Customer Details | Add Customer

    Label
    Action
    Description / Example

    After entering the required details, click Next to proceed to the Entity Details section.

    Entity Details | Customer Details

    The Entity Details tab allows you to create and associate one or more entities under a customer. An entity represents a logical or operational subdivision of a customer, such as a branch, department, region, or business unit. Each entity can maintain its own contact and location information while remaining mapped to the parent customer.

    Entities help segregate assets, users, reports, and configurations within a customer scope when MSP is enabled.

    Click Save to create the entity and associate it with the customer. After the entity is added, click Next to proceed to the Settings configuration.

    Settings | Customer Details

    Label
    Action
    Description / Example

    Click Next to proceed to the License configuration.

    License | Add Customer

    The License tab is used to allocate license counts to the customer for users and assets. This section defines how many resources the customer is permitted to use within the organization.

    The configured values determine the operational limits for that customer and are validated against the organization’s available license pool. This tab includes:

    • User License Count

      • User Count

      • Technician User Count

    • Asset License Count

    Each value entered here controls how many corresponding users or assets the customer can manage within the platform.

    After entering all required details, click Submit to create the customer.

    Roles & Privileges

    Access control within Infraon is managed through role-based privileges. A Role defines a user's role within Infraon, and Privileges define the user's level of access across multiple modules of Infraon. Infraon comes with seven default roles with pre-defined privileges.

    On Infraon, multiple default roles are displayed as a list with icons for editing, cloning, and deleting. The 'New Role' button is at the top right corner of the page.

    Details displayed are as follows:

    • Role Name

    • User Count

    Business Rule

    A business rule for an infraon product refers to a specific guideline or constraint that governs the behavior, processes, or operations within the context of that product's infrastructure. These rules are typically defined and enforced to ensure consistency, compliance, and efficient functioning of the infraon product.

    There are two types of business rules:

    • Load Balancer: The ticket allocation system ensures a balanced workload distribution between users. It automatically routes any additional tickets beyond the initial allocation to the following user until the same number of tickets per user is reached.

    For example, if user one has seven tickets and user two has five tickets, the next ticket will be automatically added to user two, since user one already has seven tickets, which is greater than user two's five.

    Select from the dropdown

    Defines the execution priority when multiple matching rules exist. Example: High

    Enforcement Mode

    Select from the dropdown

    Select how the rule behaves after the initial execution. Example: Select Apply If Empty to populate the Department field only if it does not already contain a value.

    Preserve Manual Change

    Toggle On or Off

    Prevents automated updates from overwriting manually modified values when enabled. Example: Enabled

    Description

    Enter text

    Optionally provide a short description for the rule. Example: Automatically assign department based on IP address.

    Is Enable

    Toggle On

    Enables the business rule.

    Operator

    Select operator

    Specify the comparison operator.

    Example: In

    Value

    Enter or select value

    Specify the matching value or range.

    Example: 1.0.0.0

    Value

    Select value

    Select the value to assign to the target field.

    Example: IT Team

    Add additional conditions or actions using the + icon or remove existing ones using the − icon.

  • Changes are recorded in the Activity Log for traceability.

  • are automatically migrated to
    Software Business Rules
    during feature migration.

    Set Value

    Specifies that values will be auto-filled when the condition is met.

    Rule Name

    Auto-Tag HP Assets

    A custom, descriptive name for the rule.

    Description

    [Optional]

    Brief description for internal reference.

    Is Enable

    ON (Toggle Enabled)

    Ensures the rule is active and will run automatically.

    Assigns Abdul as the default technician or owner responsible for this asset.

    User Tag

    DevOps

    Applies the DevOps tag for segmentation or automation.

    Choose CMDB.

    Type

    Select from the dropdown

    Choose Set Value.

    Precedence

    Select value

    Define the execution priority if multiple rules exist.

    Description

    Enter text

    Add a short summary of the rule purpose.

    Is Enable

    Toggle On

    Enables the business rule.

    Example: Contains

    Value

    Enter value

    Example: Laptop

    And

    Add condition

    Add additional filters, such as Make contains Lenovo, if required.

    Choose Model Year.

    Add Years

    Enter value

    Example: 5 for Laptop assets.

    Add Months

    Enter value

    Optional. Leave blank if not required.

    Choose Software to create a software-based notification rule.

    Type

    Select from the dropdown

    Choose Notification as the business rule type.

    Description

    Enter text

    Add a brief description describing the purpose of the rule. Example: Notify asset owner when blacklisted software is detected.

    Is Enable

    Toggle On

    Enables the business rule so it is evaluated during inventory synchronization.

    Device Type

    In

    Laptop

    Limits the rule to laptop devices.

    Department (Optional)

    Equals

    Finance

    Restricts notifications to assets belonging to the Finance department.

    Software Publisher (Optional)

    Equals

    Example Publisher

    Filters notifications based on the software publisher.

    Software Name (Optional)

    Contains

    Example Software

    Triggers the rule only for matching software names.

    Software Version (Optional)

    Equals

    5.2.1

    Restricts notifications to a specific software version, if required.

    Select one or more recipients, including Asset Owner, specific users, or user tags.

    Notification Channel

    Email

    Sends the notification using the default email template.

    Rule Name

    Enter value

    Specify a descriptive name for the business rule. Example: Department Auto Assignment

    Module

    Select from the dropdown

    Select CMDB.

    Type

    Select from the dropdown

    Select Set Value.

    When

    Select field

    Then Value Update To

    Select field

    Select from the dropdown

    Select CMDB.

    Type

    Select from the dropdown

    Select Notification.

    Precedence

    Select from the dropdown

    Specify the execution priority when multiple notification rules exist. Example: High

    Description

    Enter text

    Optionally provide a short description. Example: Sends notification whenever a new asset is created.

    Is Enable

    Toggle On

    Enables the notification rule.

    Select operator

    The operator is In.

    Event

    Select value

    Select one of the supported events:

    • Single Asset Added

    • Bulk Import

    • Single Asset Deleted

    • Bulk Delete

    And

    Add condition (Optional)

    Add additional asset filters if the notification should apply only to specific assets. Example: Make → In → Dell

    Select one or more recipients who should receive the notification. Example: alex@infy.com, chrisbrown@example.com

    Configure the trigger condition

    Configure the value update

    Click here

    Precedence

    Choose the asset attribute to evaluate.

    Example: IP Address

    Select the asset field to update.

    Example: Department

    Add Customer

    Click to add

    Opens the Add Customer sidebar to create a new customer with customer details, entities, roles, dashboards, and license allocation.

    Customer Card

    Click on card

    Displays customer summary including:

    • Customer Name

    • Customer Code

    • Assets Count

    • Users Count

    Edit

    Click edit icon

    Opens the selected customer in edit mode to update customer details, entities, or license allocation.

    Delete

    Click delete icon

    Deletes the selected customer after confirmation.

    Customer License

    Click icon

    Opens the Customer License Sidebar displaying allocated and used license counts per license type.

    License Allocation

    Unique reference code used for mapping and identification. Example: AIR001

    Domain

    Enter domain name

    Specifies the customer’s primary domain. Example: airtel.com

    Business Email

    Enter official email

    Used as the primary communication email for the customer. Example:

    Phone Number

    Select country code and enter number

    Contact number associated with the customer. Example: +1 25********8

    Website

    Enter website URL

    Official website of the customer. Example:

    Subscription ID

    Enter subscription reference

    Identifier for subscription or contract tracking. Example: SUBAIR2026001

    Is Active

    Toggle On/Off

    Enables or disables the customer in the system.

    Location Name

    Enter location name

    Primary operational or registered location name. Example: Airtel Corporate HQ

    Country

    Enter country

    Country where the customer operates. Example: United States

    Region

    Enter region

    Regional classification within the country. Example: North America

    State

    Enter state

    State of the customer location. Example: New York

    District

    Enter district/county

    County within the state (if applicable). Example: New York County

    City

    Enter city

    City of the customer location.

    Pin Code

    Enter postal code

    ZIP code of the location. Example: 10036

    Landmark

    Enter nearby landmark

    Reference point near the customer location. Example: Near Bryant Park

    Flat, House No., Building, Company

    Enter address line 1

    Primary address details. Example: 1095 Avenue of the Americas

    Area Colony, Street, Sector, Village

    Enter address line 2

    Secondary address details. Example: Midtown Manhattan

    Supported Admin Role

    Select role from dropdown

    Select the admin role assigned to the customer for managing configurations and operations.

    Example: Customer Admin

    Supported Reports

    Select reports from dropdown

    Select the reports accessible to the customer admin users. Multiple selections can be configured.

    Example: Policy Audit Report, Network Compliance Report, CLI Job Report

    Supported Dashboards

    Select dashboards from dropdown

    Select dashboards available to the customer admin users.

    Example: NCCM Dashboard, Compliance Overview Dashboard

    IT Asset Count

  • Non-IT Asset Count

  • Mobile Device Count

  • Availability Monitoring Count

  • Performance Monitoring Count

  • Search

    Enter text to search

    Allows you to search customers by Customer Name or Customer Code.

    Filter

    Click to apply filters

    Customer Name *

    Enter customer name

    Defines the customer identifier within the organization. Example: Airtel

    Code *

    Full Logo

    Upload image file (Drag & Drop or Browse)

    Upload the complete company logo displayed on the top-left of the application (expanded menu) and in exported documents. Recommended Size: 320 × 80 pxFormats: png, jpeg, jpg (Max 20 MB)

    Logomark / Icon

    Upload image file (Drag & Drop or Browse)

    What you see on the screen

    Add Customer

    Note: Fields marked with an asterisk (*) are mandatory and must be completed before proceeding.

    Filters customers using:

    • Fields: Customer Name and Customer Code

    • Conditions: in, not in, equal to, not equal to, contains, and not contains.

    Enter unique customer code

    Upload the compact logo icon displayed when the side menu is collapsed.

    Recommended Size: 80 × 80 pxFormats: png, jpeg, jpg (Max 20 MB)

    Role Description

  • Icons to edit/clone/delete

  • Roles are crucial for managing workflows and ensuring secure access to specific modules. Infraon uses dynamic, role-based access control (RBAC) to define user access and responsibilities across the platform.

    Role

    Description

    Infraon Admin

    Has complete access to the Infraon platform. Can manage all configurations, users, assets, and modules. This role is equivalent to the ITIL v4 “Administrator” or Platform Owner. Note: This role cannot be edited or deleted.

    Approver

    Has access only to the Requester Portal and can approve workflows related to tickets, changes, SLAs, and onboarding processes. Reflects the Change Authority or Approver Role in ITIL v4.

    IT Manager

    • Go to Infraon Configuration -> User Management -> Role and Privileges

    • Click on the 'New Role' button in the top right corner.

    Privileges for default roles are saved as templates and can be selected and customized to suit needs. Privileges are customized at the ‘General,’ ‘Ticket,’ ‘NCCM,’ ‘Privacy Settings,’ and ‘Reports’ levels.

    Label

    Action

    Description/Example

    Role Name*

    Add a name for the new role.

    Manager, Support Team, L1 Support, etc.,

    Select Template

    The Privileges module within Infraon Infinity empowers administrators with granular control over user permissions. This ensures users have the necessary access to perform their tasks effectively while safeguarding sensitive data within the platform.

    Here, admins can define specific actions/modules that users can perform within each module using checkboxes. These levels include:

    Label

    Action

    Description/Example

    View

    If selected, the 'View' privilege allows the user only to view the selected module/page.

    For example, if the user is given the 'View' privilege to the 'Business Catalogue' module, the user will be able to view the services listed.

    Add

    Here's a breakdown of the functionalities offered by the Privileges module and its sub-modules:

    Grant access to various Infraon Infinity modules:

    • Agent

    • API Registration

    • Audit

    • Business Hour

    • Bot Configuration

    • Business Rule

    • Business Catalogue

    • Change

    • CI Relation rule

    • Asset

    • Contract Management

    • Correlation Rule

    • CSAT

    • Client Registration

    • Dashboard

    • Department

    • Device Credentials

    • Diagnosis Tools

    • Discovery

    • Events

    • Geomap

    • Holiday

    • IMACD

    • Mail Automator

    • Jobs

    • Knowledge Base

    • Leaves

    • Maintenance

    • Messenger

    • My Profile

    • Network Configuration

    • Network Diagram

    • Organization

    • Address Book

    • Password Policy

    • Problem

    • Release

    • Request

    • Requester

    • Service Catalogue

    • Shift

    • SLA

    • SMS Gateway

    • Software License

    • SSP Configuration

    • Tag

    • Task

    • Team Escalation

    • Teams

    • Template

    • Thresholds

    • Topology

    • Trigger

    • Technician

    • Role

    • Vendor

    • Workflow

    • Workspace

    Log Management:

    Manage user access to functionalities related to Log Management and configurations. This sub-module offers permissions for:

    • Log Multi-Index: Create and manage the multi-indexes that help retrieve data from Elasticsearch.

    • Log Export Configs: Export Configs define how logs are exported, including format, size, and downloaded exported log files.

    • Log Search: Enables rapid searching and analysis of vast amounts of structured and unstructured log data, delivering results in seconds.

    • Log Rule: A critical component in monitoring systems that defines how log data is processed and analyzed in real-time to quickly detect and respond to security threats.

    Define permission levels (Add, View, Edit, Delete, etc.) for different user roles regarding ticket management tasks. This allows for granular control over how users interact with tickets within the system.

    Manage user access to functionalities related to network changes and configurations. This sub-module offers permissions for:

    • Baseline Scheduler: Control access to scheduling tasks for network baseline configuration.

    • Configuration Download Job: Manage permissions for initiating downloads of network configuration data.

    • Configuration Parameters: Define user access to view or modify network configuration parameters.

    • Configuration Profiles: A configuration profile is a template or predefined set of configuration settings that network administrators can create and customize configuration profiles with information like device details and connection protocols for SSH and Telnet.

    • Configuration Search: Configuration Search specifically focuses on download jobs, allowing users to view or export the "startup" or "running" configurations within these jobs to identify any configuration.

    • Configuration template: Configuration templates hold the commands for uploading jobs and making changes to network devices, including provisioning, OS upgrades, creating or deactivating services, and any other change.

    • OS Image: OS images are used primarily for managing and deploying configuration changes across network devices such as routers, switches, and firewalls.

    Administrators can control the visibility of requester information for technicians working on service requests. This helps balance transparency and data privacy within your Infraon Infinity platform.

    • Unmask Requester's Contact: This section provides a toggle button. Enabling this option grants technicians visibility to the requester's contact information, potentially including phone numbers. This can be beneficial for situations where direct contact with the requester might be necessary to resolve an issue.

    • Unmask Requester's Email: Another toggle button allows administrators to control the visibility of the requester's email address for technicians. Granting access to email addresses can facilitate direct communication between technicians and requesters, potentially expediting issue resolution.

    • Unmask Requester's Name: The final toggle button controls the visibility of the requester's name for technicians. Enabling this option ensures technicians can easily identify the person requesting assistance.

    Define permission levels (Add, View, Edit, Delete, etc.) for different user roles regarding reports. This ensures users can access reports relevant to their needs while restricting access to sensitive data as necessary.

    Once all the parameters are added, click 'Submit' to save and add the role. Administrators and privileged users can edit and delete roles using the respective icons.

    Controls permissions related to attendance marking across the Infraon Web App and Infraon Mobile App. When enabled, users can Clock In/Clock Out based on the assigned platform.

    Label

    Action

    Description / Example

    Attendance Infraon Mobile App

    Toggle On/Off

    Allows access to mark attendance from the Infraon Mobile App. Enabling this also shows the Clock In/Clock Out option for mobile usage. Example: A field engineer marks daily attendance on a mobile device.

    Infraon Web App

    Toggle On/Off

    What you see on the screen

    Roles

    You can edit the default roles or create new ones to suit your organizational needs. However, roles must be defined before inviting users.

    • Each user can be assigned one or more roles depending on responsibilities.

    • Role-based privileges impact what users can view, add, edit, or delete within the Infraon platform.

    Instructions to 'Add a new Role.'

    Privileges

    General:

    Ticket:

    NCCM (Network Change & Configuration Management):

    Privacy Settings:

    Report:

    Note: The 'Administrator' role cannot be cloned/edited/deleted.

    Mark Attendance

    Round Robin: Despite any existing ticket imbalances, prospective tickets raised are sequentially assigned to the first user, disregarding the need for a balanced distribution among users.

    For Example, User One has five tickets, and User Two has three tickets; prospective tickets are automatically assigned to User One even though User Two has fewer tickets.

    • Go to Infraon Configuration → Infraon Automation → Business Rule.

    • Click Add.

    • On the Add Business Rule page, configure the rule using the fields described below.

    Label
    Action
    Description / Example

    Rule Name*

    Enter a rule name

    A unique identifier for the business rule. Example: Auto Assign L1 Tickets.

    Module*

    Select a module from the dropdown

    The chosen Module determines the available Rule Types, and selecting a Rule Type updates the Rule Setup section to display only applicable fields and options, ensuring accurate and context-specific configurations.

    Rule Setup | Condition

    Label
    Action
    Description / Example

    When*

    Select operand, operator, and value

    Defines the condition that triggers the rule. Operand specifies the field, Operator defines the comparison logic, and Value is the condition value.

    Add Condition (+)

    Add additional conditions

    Rule Setup | Assignment Rule/ Delayed Assignment Rule

    Label
    Action
    Description / Example

    Then Assign To*

    Select Group, Expertise, Level

    Assigns the record to a specific team based on expertise and support level.

    After*

    Specify time duration

    Set Value | Action

    Label
    Action
    Description / Example

    Then Value Update To*

    Select the field and value

    Updates a selected field with a defined value when conditions are met.

    Add Field (+)

    Add more updates

    Priority Matrix Rule | Action

    The Priority Matrix Rule automatically determines a record's priority based on Urgency–Impact and contextual parameters such as Business, Location, Department, Group, and User.

    This rule is available when the selected Module supports priority calculation (for example: Ticket and Request).

    Label
    Action
    Description / Example

    Urgency – Impact Matrix

    Configure priority mapping

    Defines ticket priority based on combinations of urgency and impact parameters such as business, location, department, group, and user.

    The matrix allows defining priority values for combinations of Urgency and Impact dimensions.

    Urgency Levels

    • High

    • Medium

    • Low

    Impact Dimensions

    • Business

    • Location

    • Department

    • Group

    • User

    Approval Delegation Rules | Action

    Label
    Action
    Description / Example

    Delegate From*

    Select approver

    Specifies the original approver from whom approval is delegated.

    Delegate To*

    Select approver

    After configuring all required fields and labels, click Submit.

    While creating a CMDB business rule, you can choose to apply the rule to assets that already exist in the system.

    Label
    Action
    Description / Example

    Save and Update Existing Assets

    Click to apply the rule to existing assets

    Applies the newly created rule to all existing assets that match the defined conditions. A confirmation dialog appears before proceeding.

    Submit

    Click to save the rule

    What is a business rule?

    Types in business rule

    Instructions to add business rules

    Business Rule configuration dynamically adjusts based on the selected Module and Type.

    The auto-assignment process in L2 support categorizes technicians (U4, U5, U6) by level. When L1 auto-assignment is enabled, the system assigns technicians in sequence (U1, U2, U3, and so on) to resolve customer tickets.

    The auto-assignment mechanism handles hardware issues. When a problem arises in the service, the team provides hardware support. In the event of hardware issues reported by developers, an L1 expert is assigned via load balancing or round-robin, ensuring efficient resolution of customer tickets.

    Apply Rule to Existing Assets

    • If Save and Update Existing Assets is used:

      • The system identifies all existing assets matching the rule conditions.

      • The rule is applied to those assets.

    If only Submit is used:

    • Existing assets remain unchanged.

    • The rule is applied only to future assets.

    Can manage IT asset lifecycles, including adding/editing assets via CSV/Discovery (with approval). It can also view dashboards, monitor reports, alarms, and notifications, and handle discovery profiles. Aligns with the IT Asset Manager and Service Owner roles in ITIL.

    IT Support Operator

    Provides support for IT infrastructure. Has full access to:

    • Discovery Profiles (add/edit)

    • Asset onboarding via CSV/Discovery

    • Dashboards and Reports

    • Alarms and Notifications

    This role reflects the IT Support Role in ITIL.

    NOC Operator

    Monitors and manages network operations. Inherits all privileges of the IT/Tech Support Operator and can additionally manage:

    • Alarms

    • Events

    • Notifications

    The role reflects the Monitoring Specialist or NOC Engineer in ITIL.

    Tech Support Operator

    Handles end-user support by managing:

    • Service Catalog

    • Workflows

    • Assets

    • Own Dashboards and Reports

    • Add/Edit Tickets

    The role aligns with that of a 1st Line Support or Service Desk Technician in ITIL v4.

    Tech Support Manager

    Supervises support teams. Inherits all Tech Support Operator permissions and adds:

    • Access to the request portal

    • Dashboard/Report Management

    • Fixed Asset Management

    • Limited Admin Configuration

    Matches the Team Leader or Support Manager role in ITIL.

    Limited Access Technician

    Restricted access role for contractors or temporary staff. Has limited permissions across the Infraon platform. Helpful in implementing Least Privilege Access practices in ITIL.

    Requester

    End-users who can log in to the Self-Service Portal to:

    • Raise Incidents

    • Submit Service Requests

    • Raise Change Requests

    • Track their request status

    • Access Knowledge Base

    This aligns with the Service Consumer or End User role in ITIL v4.

    Read Only Admin

    The user can view all modules and data across the platform, but cannot create, edit, delete, configure, approve, or perform operational actions. Suitable for monitoring, audits, vendor reviews, and oversight access.

    API User

    Intended for system-to-system integrations and API consumption. Users assigned this role can authenticate using long-term API tokens and access supported APIs based on the permissions granted to the role.

    API Users cannot log in to the Infraon web portal, participate in approval workflows, or be assigned as approvers. All API activities, including token generation, token regeneration, authentication attempts, and API usage, are tracked through audit and metering logs.

    API usage is also subject to license-based consumption tracking, where API calls are monitored against the organization's licensed API call limit. When usage approaches or exceeds the configured threshold, the system can generate notifications and enforce API access restrictions based on the license in effect.

    Select a template to import privileges.

    Selecting existing role templates helps import privileges from an existing role to the new role.

    Description

    Add a brief description of the role.

    Assign to L1 support members of the team.

    Privileges

    Select privileges to enable access to the new role.

    Privileges are split into modules: General, Ticket, NCCM, Privacy Settings, and Reports.

    Permissions can be explicitly selected - view, add, edit, delete, copy, and configure.

    If selected, 'Add' allows the user to view and perform add operations within the selected module/page.

    For example, if the user is given the 'Add' privilege to the 'Business Catalogue' module, the user will be able to view the services listed and add new services. The user will, however, not have edit or delete privileges.

    Edit

    If selected, 'Edit' allows the user to view and perform edit operations within the selected module/page.

    For example, if the user is given the 'Edit' privilege to the 'Business Catalogue' module, the user will be able to view the services listed and edit existing services. The user will, however, not have add or delete privileges.

    Delete

    If selected, 'Delete' allows the user to view and perform add operations within the selected module/page.

    For example, if the user is given the 'Delete' privilege to the 'Business Catalogue' module, the user will be able to view the services listed and delete existing services. The user will, however, not have to add or edit privileges.

    Copy

    If selected, 'Copy' allows the user to view and perform add operations within the selected module/page.

    For example, if the user is given the 'Copy' privilege to the 'Business Catalogue' module, the user will be able to view the services listed and add new services. The user will, however, not have edit or delete privileges.

    Configure

    If selected, 'Configure' allows the user to view and perform add operations within the selected module/page.

    For example, if the user is given the 'Add' privilege to the 'Business Catalogue' module, the user will be able to view the services listed and add new services. The user will, however, not have edit or delete privileges.

    Upload

    If selected, ‘Upload' allows the user to view and perform add operations within the selected module/page

    Download

    If selected, ‘Download’ allows users to download and perform export operations within the selected module/page.

    The Download privilege allows users to export logs from the Log Management module in PDF, CSV, or XLS formats, enabling offline analysis, sharing, and integration with other tools.

    Allows direct access to mark attendance in the Infraon Web Application. Enabling this also shows the Clock In/Clock Out option on the web. Example: A helpdesk operator marks attendance from their office workstation.

    Entity Count

    enterprise@airtel.com
    https://www.airtel.com/

    Asset records are updated accordingly.

    Specifies the module where the rule is applied. Available options:

    • Ticket (rules applied to incidents/tickets)

    • Problem (rules applied to problem records)

    • Request (rules applied to service requests)

    • Approval (rules applied to approval workflows)

    • CMDB (rules applied to configuration items and assets).

    The selected module controls the available rule types and rule setup fields.

    Type*

    Select a rule type from the dropdown

    Defines the action performed by the rule. Options vary by module:

    • Assignment Rule: Automatically assigns records to a group based on conditions.

    • Delayed Assignment Rule: Assigns records after a defined time duration if conditions are met.

    • Set Value: Updates one or more fields with specified values when conditions match.

    • Priority Matrix Rule: Calculates priority based on combinations of urgency and impact. Immediate Delegation Rule: Instantly delegates approvals from one approver to another.

    • Duration-Based Delegation: Delegates approvals after a defined duration with optional reminders.

    Precedence*

    Select priority level

    Determines the order in which rules are evaluated when multiple rules match. Options: High, Medium, Low. Higher precedence rules are executed first.

    Description

    Enter rule description

    Short explanation of the rule’s purpose. Example: Assign network tickets to the L1 team.

    Is Enable

    Enable or disable the rule

    Controls whether the rule is active. Disabled rules are not executed.

    Override Existing Rule

    Enable if required

    Allows this rule to override existing matching rules.

    Allows multiple conditions to be combined for rule evaluation.

    Applicable to delayed assignment rules. Defines when the assignment should occur (Days / Hours / Minutes).

    Allows updating multiple fields in a single rule.

    Specifies the alternate approver.

    Delegate After*

    Define duration

    Time after which delegation occurs.

    Remind Before Delegation*

    Define reminder time

    Sends a reminder before the delegation is triggered.

    Saves the rule without applying it to existing assets. The rule will apply only to assets created or modified after its enactment.

    Users

    Users are organization members with access to Infraon. Administrators can create, invite, import, and manage users, assigning predefined roles and privileges based on their responsibilities.

    The Users module allows administrators to manage user information, roles, access status, work details, and user-to-asset associations.

    The Users module provides multiple ways to create and manage users in Infraon.

    • Add User – Create a user by entering their personal, work, and address details.

    • Add Customer User – Create users associated with a customer or sub-client organization.

    Import Users – Create multiple users by uploading user details through a CSV file.

  • Invite User(s) – Send an invitation to users through their email address. The user can register using the invitation link.

  • Update Users – Update multiple users using a CSV file.

  • Edit or Delete Users – Modify or remove existing users from the user list.

  • Enable or Disable Users – Control whether a user can access Infraon.

  • When a user's Is Active status changes from True to False, the system automatically removes the user from all associated assets.

    This applies when the user is assigned as:

    • Owner

    • Managed By

    • Used By

    • Requester

    The change is recorded in the Asset Activity Log.

    This behavior is supported for:

    • Manual updates

    • Grid updates

    • Bulk CSV updates

    Infraon also applies license limits when it synchronizes users and requesters.

    • New users/requesters cannot be created when the available license capacity is reached.

    • Existing users/requesters can continue to be updated.

    • A warning is displayed when a sync operation exceeds the available license limit.

    • The system prevents inconsistent or partial user creation.

    Go to Infraon Configuration → User Management → Users.

    The Users page lets you search, filter, view, export, and manage users.

    The Users page provides:

    Users | Basic Options

    Label
    Action
    Description/Example

    Search

    Enter a keyword in the search field.

    Searches for users based on the entered information.

    Filter

    Select the required filter criteria.

    The button next to Invite User(s) allows you to switch between:

    • List View

    • Card View

    Both views display user information and available actions.

    The page displays user information such as:

    Users | User List

    Label
    Action
    Description/Example

    Username

    View the username.

    Displays the username of the user.

    Phone

    View the phone number.

    The Users module provides multiple options for creating and managing users in Infraon. Administrators can create users individually, create customer users, import users in bulk, invite users through email, or update existing users using a CSV file.

    The available options are:

    • Add User

    • Add Customer User

    • Import User

    • Invite User(s)

    • Update Users

    The Add User option allows administrators to create a user by entering the required user, work, and address information.

    Click Add User to open the user creation page.

    The page contains three sections:

    • User

    • Work

    • Address

    Add User | User

    Label
    Action
    Description/Example

    Full Name

    Enter the user's full name.

    John Doe

    Username

    After entering the required details, click Next to continue to the Work Details section or click Submit to create a new user.

    Add User | Work

    Label
    Action
    Description/Example

    Designation

    Enter the user's designation.

    Technical Writer

    Organization Role

    Add User | Address

    Label
    Action
    Description/Example

    Base Location

    Select the user's base location.

    Select a location.

    Work Location

    Enter or select the user's work location.

    After entering the required details, submit the form to create the user.

    The Add Customer User option lets administrators create users associated with a specific customer or sub-client organization.

    A customer organization may manage multiple sub-client organizations within Infraon. For example, a service provider managing IT services for multiple clients can use Add Customer User to create a user for a specific customer or sub-client. The administrator can associate the user with the appropriate customer, assign a role, and provide access based on the user's responsibilities and privileges.

    This ensures users can access and manage information relevant to their assigned customer organization.

    The Import User option lets administrators create multiple users by uploading their details via a CSV file.

    1. Go to Infraon Configuration → User Management → Users → Add User.

    2. Select Import User.

    3. Download the sample CSV file using Download sample CSV file here.

    4. Enter the user details in the CSV file.

    5. Drag and drop the completed CSV file into the upload area or click Browse.

    6. Click Next to proceed to validation.

    7. Review the valid and invalid records displayed on the validation page.

    8. Correct any invalid records and re-upload the file, if required.

    Field/Requirement
    Description

    File Format

    CSV

    Maximum File Size

    10 MB

    Row Limit

    The Import CSV option allows you to download a sample CSV file and upload your completed CSV file. It also provides details about the required CSV format and field requirements.

    Label
    Action
    Description/Example

    Download sample CSV file here

    Click to download.

    Downloads the CSV template for importing users.

    Upload

    Upload the completed CSV file.

    After uploading the CSV and clicking Next, Infraon validates the uploaded data and separates the records into Valid and Invalid data. For invalid records, click Download to download the failed data. Click Show Fields to view the specific fields that contain errors.

    The Invite User(s) option lets administrators invite users to access Infraon via email.

    You can add multiple users and different roles in a single invitation process.

    1. Go to Infraon Configuration → User Management → Users → Add User.

    2. Click Invite User(s).

    3. Enter the user's email address.

    4. Select a role from the Role dropdown.

    5. Click Add Invite to add another invitation row, if required.

    6. Click Invite to send the invitations.

    Label
    Action
    Description/Example

    Enter Email address(es)*

    Enter one or more email addresses.

    john.doe@company.com; jane.doe@company.com

    Select Role

    Select a predefined role from the dropdown.

    • Multiple users can be invited in a single instance.

    • Different roles can be assigned to different users.

    • Roles must be predefined before sending invitations.

    • The invitation link expires after 36 hours by default.

    • The invitation expiry period can be changed in settings.

    • After an invitation expires, a new invitation must be sent.

    • If multiple invitations with different roles are sent to the same user, the role associated with the invitation link used for registration first is assigned to the user.

    • Administrators and privileged users can view pending invitations and resend them using the Pending Invitations option/icon.

    The Update Users option allows administrators to update multiple users in bulk using a CSV file.

    It can also be used to deactivate users and automatically remove them from associated assets.

    1. Go to Infraon Configuration → User Management → Users.

    2. Click Update Users.

    3. Select the required Role, if applicable.

    4. Download the sample file using Download Sample.

    5. Update the required user information in the CSV file.

    6. Drag and drop the file into the upload area or click Browse.

    7. Click Next.

    8. Review the validation results.

    Label
    Action
    Description/Example

    Role

    Select a role.

    Select the applicable role.

    Download Sample

    Click to download.

    The CSV must follow the required user-data format.

    • Full Name, Username, Email, Password, and Role are mandatory.

    • The specified Role must exist in Roles & Privileges.

    • Phone Number must include the country code and follow the required format.

    • Is Active must be set to true or false.

    • Gender must be Male, Female, or Others.

    • Multiple Notify Phone Nos must be separated using semicolons.

    • Device Group can be All or a specific device group.

    • Multiple Allowed Client IP Addresses must be separated using semicolons.

    If Is Active is changed from True to False through the update process:

    • The user is deactivated.

    • The user is automatically removed from associated assets.

    • This applies to Owner, Managed By, Used By, and Requester assignments.

    • The changes are recorded in the Asset Activity Log.

    After uploading the CSV, click Next to open the validation page and review the valid and invalid records.

    How It Works

    Automatic Asset Deallocation

    To manually allocate or deallocate a user from an asset, go to the page and update the respective user field.

    License Control

    What You See on the Screen

    View Options

    Instructions to Add User

    Add User

    Add Customer User

    The configuration and fields available under Add Customer User are the same as those available under The option is specifically intended for creating users associated with customer or sub-client organizations.

    Use Case

    Import User

    CSV Requirements

    A new user is created if the specified user does not already exist.

    Validation

    Invite User(s)

    How to Invite Users

    What You See on the Screen

    Invitation Behavior

    Update Users

    How to Update Users

    What You See on the Screen

    CSV Requirements

    User Deactivation During Update

    Filters users based on available fields such as role, status, or other user details.

    Export

    Click Export.

    Exports the user information for further analysis or record-keeping.

    Pending Invitations

    Click to view pending invitations.

    Displays invitations that have been sent but not yet accepted.

    Add User

    Click Add User.

    Creates a new user by entering user, work, and address details.

    Add Customer User

    Click Add Customer User.

    Creates a user associated with a customer or sub-client organization.

    Import User

    Click Import User.

    Creates multiple users by uploading user information through a CSV file.

    Invite User(s)

    Click Invite User(s).

    Sends an email invitation to one or more users to register and access Infraon.

    Update Users

    Click Update Users

    Updates multiple users in bulk by uploading a CSV file.

    Displays the user's phone number.

    Role

    View the assigned role.

    Displays the role assigned to the user.

    Is Active

    Enable or disable the user.

    Indicates whether the user is active or inactive.

    Last Login Time

    View the last login time.

    Displays the user's most recent login time.

    Action

    Edit or delete the user.

    Provides options to edit or delete the user.

    Enter a unique username.

    john.doe

    Email

    Enter the user's email address.

    john.doe@company.com

    Customer Name

    Select a customer from the dropdown list.

    Select the applicable customer.

    Role

    Select a predefined role from the dropdown list.

    Administrator

    Password

    Enter a password for the user.

    Enter a valid password.

    Timezone

    Select the user's timezone.

    Select the applicable timezone.

    Phone Number

    Enter the user's phone number.

    +919988776655

    Landline

    Enter the user's landline number, if applicable.

    Enter the landline number.

    Gender

    Select the user's gender.

    Male / Female / Other

    Enable Temporary User Account Access

    Enable or disable the toggle.

    Allows temporary access to the user account.

    Email Two Factor Authentication (2FA)

    Enable or disable the toggle.

    Enables email-based two-factor authentication.

    Configure Allowed Client IP Address

    Enter the permitted IP addresses.

    Restricts access to specified client IP addresses.

    Is Active

    Enable or disable the toggle.

    Determines whether the user can log in to Infraon.

    Disable Technician Access

    Enable or disable the toggle.

    Prevents the user from accessing technician-specific functionality.

    Enter or select the organizational role.

    Team Member

    Department

    Select the user's department.

    IT

    Reporting Manager

    Select the user's reporting manager.

    Select a manager.

    Employee ID

    Enter the employee ID.

    EMP001

    Experience Years

    Enter years of experience.

    3

    Experience Months

    Enter additional months of experience.

    6

    Skills

    Enter the user's skills.

    Technical Writing, Documentation

    User Tag

    Select applicable tags.

    Select tags.

    Asset Tags

    Select applicable asset tags.

    Select tags.

    Resource Tag

    Select the applicable resource tag.

    Select a tag.

    Notify Email

    Enter an email address for notifications.

    john.doe@email.com

    Notify Phone No(s)

    Enter phone number(s) for notifications.

    +919988776655

    Site Engineer Requester(s)

    Select applicable site engineer requesters.

    Select requester(s).

    Device Group

    Select a device group.

    All

    Business Entity

    Select the applicable business entity.

    Select an entity.

    Business Segment

    Select the applicable business segment.

    Select a segment.

    Partner Name

    Select or enter the partner name.

    Select a partner.

    Subsidiary

    Select the applicable subsidiary.

    Select a subsidiary.

    Bengaluru

    100 rows

    Mandatory Fields

    Full Name, Username, Email, Password, Role

    Role

    Must already exist in Roles & Privileges.

    Phone Number

    Must include the country code and be enclosed in single quotes. Example: '919988776655'

    Is Active

    Must be set to true or false.

    Gender

    Must be Male, Female, or Other.

    Notify Phone Nos

    Multiple numbers must be separated using semicolons. Example: +919988776655;+917766554433

    Device Group

    Can be All or a specific device group.

    Allowed Client IP Addresses

    Multiple IP addresses must be separated using semicolons. Example: 10.0.4.1;10.0.4.2

    Supported format: CSV

    Next

    Click to continue.

    Opens the validation page.

    Select the appropriate role.

    Add Invite

    Click to add another invitation row.

    Allows different users to be assigned different roles.

    Invite

    Click to send the invitations.

    Sends an invitation email to the specified users.

    Downloads the sample CSV file.

    Upload

    Upload the updated CSV file.

    Supported format: CSV

    Browse

    Select the CSV file from your computer.

    Select the file to upload.

    Next

    Click to continue.

    Opens the validation page.

    Asset Details
    Add User.

    Asset Information

    Upon adding an asset to the Infraon portal, users will be presented with a default view showcasing key details about the asset. This information is a quick reference point and can be customized later to fit specific needs.

    Asset Properties | Details

    Label

    Description/ Example

    Asset Name

    Infraon allows administrators or technicians to initiate secure CLI (Command Line Interface) sessions directly from the IT Assets module for supported devices. These sessions can be used for diagnostics, configuration, or troubleshooting.

    The session can be launched using SSH or TELNET protocols, and the access can be controlled through Request-based approval or direct submission, depending on role privileges.

    To initiate a CLI session/ Job, follow the steps below:

    • Locate the desired asset within the IT asset list.

    • Click on the "More Options" menu (usually represented by three dots) and select "CLI Session.”

    • A pop-up window will appear.

    • On the new pop-up tab, enter the IP address, username, port, and access reason, and select the SSH or TELNET protocol.

    From the Asset grid page, filter the category SDH / PDH; on the filtered grid page, click on the Device Name or IP to view additional information. There are multiple sub-views with all the necessary information about the device. These are: 

    Inventory information includes basic details, additional properties, Custom Fields, and Health Summary.

    The following section breaks down the details:

    • Device Details

    • Hostname

    • Device Type

    • Tags (Click on ‘Edit’ to add or remove the tags)

    Audit the user login and logout entries within the asset management module. This allows IT administrators to identify which users have accessed specific IT assets (laptops, desktops) and when. This information can help troubleshoot access issues, monitor asset usage, and maintain security compliance.

    The inventory agent gathers data on login and logout activity for each asset at regular intervals (inventory updates) and presents this data within the user logins and logouts module.

    The asset details page displays a user login and logout cart. This module details the profile name, number of logins, and number of logouts associated with each user profile for the selected asset. Additionally, a date filter allows technicians to refine the displayed data for a specific timeframe.

    The following section breaks down the details:

    • Asset History: Track an asset's entire journey, from initial purchase through use, maintenance, and eventual disposal.

    • Purchase Order Details: View crucial information from the purchase order, including the date, cost, supplier, and specifications.

    • Annual Maintenance Contract (AMC): Monitor active AMCs associated with the asset, displaying coverage period, service provider, and key terms.

    • Warranty Information: Access comprehensive warranty details like start/end dates, covered components, and claims history.

    Displays graphical view of a node with all inventory information including shelf, slot, card and port. Port information includes status of port, port utilization and other details.

    The following section breaks down the details:

    • Service State

    • Serial Number

    • Vendor

    • Name

    Displays the list of inventories and parts of the device, such as rack / shelf / slot / card / port / SFP details. Click on a specific inventory to view its properties. The inventory includes Shelves, Slots, Cards, and ports. On click of each port, it will show port information, for example: Port Status, Optical values of Port, etc.

    The following section breaks down the property details:

    • Name

    • IP Address

    • Host Name

    • Type

    Displays complete hardware information for all asset components. The data includes information collected by the Inventory Agent, as well as any additional details or custom properties added manually.

    All hardware components are organized into tabs (e.g., CPU, Memory, Disk, Interface). Selecting a tab displays only the corresponding component details.

    The hardware details include:

    • Shelf Number

    • Slot Number

    • Slot Name

    • Card Name

    If additional properties or custom fields are configured for hardware components, they are displayed alongside the agent-collected data in the respective tab.

    • Search – Click to search within the selected hardware component.

    • Export – Click to download the hardware inventory in CSV, Excel (XLS), or PDF format.

    Displays battery-related information for the asset, including:

    • Battery Health Percentage (calculated value)

    • Battery Status

    • Battery Chemistry

    • Cycle Count

    Displays the overall system performance score based on hardware evaluation. The score ranges from 1.0 to 9.9, where higher values indicate better performance.

    The overall WEI score is derived from the lowest score among the evaluated components.

    Details Available:

    The following performance metrics are displayed:

    • Processor Score: Performance of the CPU

    • Memory Score: Performance of system memory (RAM)

    • Graphics Score: Desktop graphics performance

    • 3D Graphics (Direct3D) Score: Gaming and 3D rendering performance

    This displays topology connections for the selected NE. Devices are marked in red/green based on their availability. Mouse over an asset to view details. Use action icons to navigate through, zoom in, and zoom out topology connections.

    The following section breaks down the details:

    • Grid View – Click to view in a tabular format.

    • Map View – Click to view in a map view format.

    • Node – Click to see the below details:

    • Host Name

    This option provides technicians with comprehensive access to vital information about network devices. This tab includes a detailed Download Job Summary, offering insights into recent configuration download activities and their outcomes.

    The Configuration Details section displays the device's current and historical configurations, enabling comparison and change tracking.

    The Inventory Details offer a complete overview of the device's hardware and software inventory. This centralized access to configuration, job summaries, and inventory details empowers technicians to manage efficiently and audit network devices, ensuring configurations are up-to-date and compliant with organizational standards.

    The following information can be derived from the page:

    • Device Credential

    • Configuration Profile

    • Connection Protocol

    • Download Status

    • Baseline Running

      • Version

      • Download Time

    • Current Running

    Events are colour coded based on severity. Use the calendar icon to filter active events for a specific period.

    Exports - Choose your export format: Download the topology as a separate CSV or Excel-compatible XLS file.

    Each event allows the below actions by hovering over the mouse (Quick action tool): 

    • Analyse

    • Click to view the ‘Impact Services’ event details. Click the ‘More Details’ button to redirect to the event page.

    • It includes details to help analyse the event. The user can view the asset details and the statistics of how the current event is performing.

    • Acknowledge

    Used to view the performance of the selected Port, Port Type, Statistic, etc., based on the applied filter.

    The following section breaks down the details:

    Filters available for performance reports are:

    • Port

    • Granularity

    • PM Type

    • Statistic

    Add filters to suit requirements and click generate.

    The Activity Log meticulously tracks asset changes, providing a comprehensive history of each asset. It records all modifications made by technicians, including changes to city, country, criticality, connection protocol, device credentials, and download job details.

    Entries are organized by date and time, allowing for easy monitoring and auditing of asset history. This detailed log ensures that all key actions and updates are documented, facilitating better management and oversight of IT assets.

    Enable this toggle if you want to specify a custom username instead of using stored credentials.

    Username*

    Enter username

    Required if "Use Custom Username" is toggled ON. Enter the username to initiate the CLI session. Example: admin, techuser, etc.

    Port*

    Enter the port number.

    Specify the port to use for the session. The default for SSH is 22, and for Telnet, it's 23.

    Access Reason*

    Enter justification

    Provide an apparent reason for accessing the device. This helps with audit logging and approval context.

    Example: Urgent troubleshooting - link down

    Protocol Selection (SSH / TELNET)

    Click to select

    Choose the preferred protocol to establish the CLI session. SSH is recommended for secure access.

    Active Duration (Hours, Minutes)*

    Select duration

    Specify how long the session should remain active after approval. This limits windowed access.

    Example: 0 Hours, 30 Minutes

    Access Count (0 = unlimited)*

    Set limit

    Define how many times the user can access the session. Set to 0 for unlimited access during the session window.

    Active Duration Begins

    Choose start type

    Select whether the session should begin Immediately or From Approved Time.

    Request

    Click to request a session.

    Sends the CLI session request for approval (if pre-approval is required)—routes through the Change Management workflow.

    Submit

    Click to start the session directly.

    Bypasses approval (only visible for users with enough privilege). Starts session instantly.

    Asset ID
  • Device Type

  • IP Address

  • Make

  • Active Version

  • Ci Name

  • Managed EMS IP

  • Managed EMS Name

  • Model

  • Owner Details

  • Name

  • Mail ID

  • Mobile number

  • Edit – Click to make changes.

  • User Details

  • Name

  • Mail ID

  • Edit – Click to make changes.

  • Deallocate – Click to allocate a new user.

  • Resend Email – Click to resend the e-mail.

  • Attachment

  • Choose from the categories (Default, Procurement, Service, Retirement Documents).

  • Add – Click to add new attachments.

  • Asset Configuration

  • Creation Time

  • Last Update Time

  • Login Profile

  • Login Profile ID

  • Filter

    The date filtering function allows technicians to narrow down the displayed data to a desired timeframe.

    Type
  • Location

  • Capacity

  • Layer Rate

  • SFP (Small Form Factor) Type

  • Vendor

  • SFP Status

  • SFP Serial Number

  • SFP Product Code

  • Loopback Mode

  • Transmitted Trace

  • Received Trace

  • PTP (Port of Tanjung Pelepas)

  • SFP Installed Version

  • IP Address

  • MTU (Maximum Transmission Unit)

  • PTP (Port of Tanjung Pelepas)

  • PVID

  • Card Name
  • Component Type

  • Serial Number

  • Part Number

  • Physical Status

  • Port Name
  • Port State

  • Port Number

  • SFP Installed

  • SFP Type

  • Expected Hardware

  • Installed Hardware

  • Serial Number

  • State

  • Design Capacity
  • Estimated Charge Remaining

  • Estimated Run Time

  • Full Charge Capacity

  • Device ID and Battery Name

  • Current Status

  • Disk Score: Performance of the primary disk

  • Last Assessment Time: Date and time when the score was last calculated

  • IP Address

  • Make

  • Model

  • Device Type

  • EMS Name

  • Firmware Version

  • Region

  • State

  • City

  • Location

  • Edge – Click to see the below details:

  • Description

  • Source IP

  • Source Device

  • Source Port

  • Destination Ip

  • Destination Device

  • Destination Port

  • Layer Rate

  • Active Events (Click to redirect to the Active Events page)

  • Services (Click to redirect to the Services page)

  • Export – Click to create a PDF of the current topology view.

  • Zoom Keys - Icons can be used to navigate through the topology diagram.

  • Arrow Keys - Icons can be used to navigate through the topology diagram.

  • Agent
  • Status

  • Download Start Time

  • Download End Time

  • Next Retry Action Time

  • Inventory Download protocol

  • Startup Configuration download protocol

  • Running Configuration download protocol

  • Previous V/S Current Running

  • Baseline V/S Current Running

  • Current Startup

  • Baseline Startup

  • Previous V/S Current Startup

  • Baseline V/S Current Startup

  • This is used to acknowledge the event. NOC users or technicians can acknowledge it and add a comment to let other users know they are working on it. 

  • Diagnosis

  • Used to perform active diagnosis.  Diagnosis can be performed using Ping, SNMP Walk, and Trace Route. 

  • Ticket

  • Used to create an incident for the event.

  • Clear

  • Used to clear the vent. Cleared events can be viewed using the ‘Show History’ toggle button.

  • Activity log

  • Used to view the vent history.

  • Aggregate
  • Duration

  • Identify the asset with a user-friendly name.

    Asset ID

    A unique identifier is assigned to the asset within the system for easy tracking and reference.

    IP Address

    View the network address associated with the asset.

    Status

    Quickly understand the asset's current operational state (e.g., Active, Inactive, or Under Maintenance).

    Manufacturer

    Identify the company that produced the hardware asset.

    OS Version

    View the operating system version installed on the asset.

    System SKU Number

    Displays the unique System Stock Keeping Unit (SKU) number fetched directly from the discovery agent. This field helps in identifying the specific hardware model and configuration provided by the manufacturer. The value is auto-populated by the inventory agent when the asset is discovered and cannot be edited manually. Example: 15AB-1234-XYZ

    Actions

    Edit

    Modify any of the asset's details to ensure accuracy and reflect any changes.

    Delete

    Remove the asset from the inventory if it's no longer needed.

    Add Owner

    Assign a specific user as the asset's owner, facilitating responsibility and ownership tracking.

    CLI Session

    Initiating a CLI session connects to a network device to execute commands for tasks like configuration, diagnostics, and software updates, enabling efficient device management.

    Add Owner

    Click Add Owner to assign a user as the asset owner. Assigns a user as the asset's owner for ownership tracking. If the assigned user is later marked inactive, they are automatically removed from the asset. The change is reflected in the asset fields and recorded in the activity log.

    Add User

    Click Add User to assign a user to the asset. Assigns a user as the asset user (used by). If the assigned user is marked inactive, they are automatically removed from the asset, ensuring assets remain linked only to active users. All changes are tracked in the activity log.

    Label

    Action

    Description / Example

    IP Address*

    Auto-filled

    Displays the IP address of the selected asset. This is non-editable.

    Example: 10.0.4.31

    Use Custom Username

    Label

    Description/ Example

    No of Logins

    Displays the total number of times a user profile has accessed this specific IT asset.

    No of Logouts

    Displays the number of times a user profile has ended a session on the IT asset.

    Profile Name

    Steps to Initiate CLI Connection

    • If your role requires pre-approval, clicking Request will route the session for manager or admin approval.

    • Once approved, the session becomes active during the defined window.

    • If you have direct privileges, clicking Submit will initiate the CLI session instantly without approval.

    • All actions are logged for audit, and access is time-bound and usage-controlled to maintain compliance and security.

    Sections

    Details

    User Logins/Logouts

    What you see on the screen

    Asset Lifecycle

    Panel View

    Inventory Tree

    Hardware Inventory

    Battery Details

    Windows Experience Index (WEI) Score

    My Topology

    Configuration Details

    Download Job Summary

    Configuration Details

    Inventory Details

    Events

    Performance

    Export – These reports can be downloaded in an Excel or PDF format using the respective action icon.

    Activity Log

    Export - Audits can be downloaded in CSV, Excel, or PDF formats using the respective action icon.

    Toggle

    This will typically be the user's network login name or alias.

    Feature Configuration

    The Feature Configuration module enables administrators to manage and control system features and AI capabilities across the Infraon Platform through a centralized interface.

    It allows configuration of feature behavior without requiring backend changes, ensuring consistency across modules and services. Administrators can track, discover, and enable all AI-related capabilities and privileges available within the organization.

    The module provides granular control over how AI-driven functionalities operate, including knowledge base generation, search behavior, automation intelligence, and user experience settings.

    Available sections include:

    • Knowledge Base Configuration: Configure AI-driven knowledge base creation, accuracy, and processing parameters.

    • Ticket AI: Manage AI capabilities related to ticket analysis, suggestions, and automation.

    • Request AI: Configure AI behavior for request classification and processing.

    • Problem AI: Control AI-assisted problem identification and root cause insights.

    • Change AI: Manage AI recommendations and validations for change management workflows.

    • Release AI: Configure AI support for release planning and execution insights.

    • AI Service Classification: Define how AI classifies services based on input data.

    • Bot Assistants: Manage AI-powered virtual assistants and their behavior.

    • SLA Prediction: Configure AI-based SLA prediction and risk analysis settings.

    • Similar Ticket Merge: Control AI logic for identifying and merging similar tickets.

    • Agentic Bot: Configure autonomous AI agents for task execution and assistance.

    Users can automatically detect and sanitize sensitive information before AI-powered features process the data. The configuration helps protect confidential information such as personal identifiers, credentials, financial details, network information, and authentication tokens by masking, replacing, or removing sensitive values before they are sent to the AI model.

    The sanitization engine scans all incoming data as plain text and applies regex-based pattern detection to identify sensitive information across multiple supported categories. Based on the configured settings, detected values are either replaced with placeholders, substituted with synthetic values, or removed completely before being sent to the AI model.

    When Send Faker Data to AI Model is enabled, the system replaces detected sensitive values with realistic synthetic substitutes while maintaining a reversible mapping. This allows the AI model to retain contextual understanding without exposing actual sensitive information.

    Once the AI response is generated, the original values are automatically restored before the response is displayed to the user.

    Configurations

    General Settings | Basic Details

    Label
    Description
    Example

    Sanitization Categories | Basic Details

    Sanitization Categories allow users to control which types of sensitive information should be detected and sanitized before data is processed by AI features. Each category can be enabled or disabled individually based on organizational privacy and compliance requirements.

    Label
    Description
    Example

    The Knowledge Base Configuration section allows administrators to control how AI-generated knowledge base articles are created, processed, and presented across the platform. It provides:

    • Granular settings to manage content quality

    • Search behavior

    • AI response handling

    • System performance

    Administrators can enable or disable the Knowledge Base feature, fine-tune AI thresholds, control KB suggestions in search and email responses, and define limits on content structure. These settings directly impact how knowledge is generated, matched, and delivered to users.

    To know more, refer to the module.

    Label
    Action
    Description/ Example
    Label
    Action
    Description/ Example
    Label
    Action
    Description/ Example
    Label
    Action
    Description/ Example
    Label
    Action
    Description/ Example
    Label
    Action
    Description/ Example
    Label
    Action
    Description/ Example
    Label
    Action
    Description/ Example

    The Ticket AI Configuration section allows administrators to control how AI capabilities assist in ticket handling, response drafting, and communication improvements.

    It enables automation of summaries and enhancement of ticket content to improve clarity and response efficiency.

    For more information, refer to the module.

    Label
    Action
    Description / Example

    The Request AI Configuration section enables AI-driven enhancements for service requests, improving communication clarity and providing summarized insights.

    For more information, refer to the module.

    Label
    Action
    Description / Example

    The Problem AI Configuration section controls AI assistance for problem records, enabling better analysis, documentation, and communication.

    For more information, refer to the module.

    Label
    Action
    Description / Example

    The Change AI Configuration section enables AI support for change records, improving documentation quality and clarity of communication.

    To know more, refer to the module.

    Label
    Action
    Description / Example

    The Release AI Configuration section allows AI assistance in release documentation and communication.

    For more information, refer to the module.

    Label
    Action
    Description / Example

    The AI Service Classification section enables automated ticket and request classification using AI models.

    To know more, refer to the module.

    Label
    Action
    Description / Example

    The Bot Assistants section enables AI-powered bots to provide automated responses and guidance to users.

    For more information, refer to the module.

    Label
    Action
    Description / Example

    The SLA Prediction section enables AI to predict potential SLA breaches and delays.

    For more information, refer to the module.

    Label
    Action
    Description / Example

    The Similar Ticket Merge section helps identify and manage duplicate or similar tickets using AI.

    For more information, refer to the module.

    Label
    Action
    Description / Example

    Login Settings

    Login Settings allows administrators to configure authentication methods, Single Sign-On (SSO), two-factor authentication (2FA), CAPTCHA validity, and login page customization. These settings help organizations manage user access and apply security requirements across the Infraon platform.

    Standard Authentication provides three methods for users to sign in to Infraon: Username & Password Default, Mobile Number & SMS, and Email-Based 2FA. Administrators can configure the required authentication method and its settings based on the organization's security requirements.

    Login Settings | Standard Authentication Methods

    AA:BB:CC:DD:EE:FF → [MAC_ADDRESS]

    IP Address

    Redacts IPv4, IPv4 with CIDR notation, and IPv6 addresses.

    192.168.1.1 → [IP_ADDRESS]

    Email Address

    Redacts standard and obfuscated email addresses.

    user@domain.com → [EMAIL]

    Phone Numbers

    Redacts international and local phone number formats, including E.164, Indian, UK, and North American formats.

    +91 98765 43210 → [PHONE]

    Credit / Debit Card

    Redacts card numbers, CVV/CVC values, and expiry dates for supported card providers.

    4111 1111 1111 1111 → [CARD_NUMBER]

    National / Gov. IDs

    Redacts government-issued identity numbers such as Aadhaar, PAN, Passport, SSN, GSTIN, and Driving License numbers.

    ABCDE1234F → [PAN]

    Date of Birth & Age

    Redacts date of birth information and age references in supported formats.

    DOB: 15/08/1990 → [DOB]

    Secrets & API Keys

    Redacts API keys, tokens, passwords, JWTs, SSH keys, database connection strings, and other secret values.

    sk-abc123XYZ → [API_KEY]

    URL Credentials

    Redacts credentials and sensitive query parameters embedded within URLs.

    https://user:pass@host.com → https://[CREDENTIALS]@[SERVER]

    Banking Identifiers

    Redacts IFSC, IBAN, SWIFT/BIC, UPI IDs, routing numbers, and bank account numbers.

    HDFC0001234 → [IFSC]

    Server & Hostnames

    Redacts fully qualified domain names (FQDNs), Windows machine names, and server hostnames.

    prod-server-01.internal.local → [SERVER]

    Location & Coordinates

    Redacts GPS coordinates, DMS coordinates, Google Plus Codes, and address details.

    12.9716, 77.5946 → [GEO_COORDINATES]

    Vehicle Registration

    Redacts vehicle registration numbers and VIN details.

    MH12AB1234 → [VEHICLE_REG]

    Session & Auth Tokens

    Redacts session identifiers, authentication headers, cookies, CSRF tokens, and OAuth parameters.

    JSESSIONID=ABC123XYZ → [SESSION_ID]

    Data privacy

    AI Context Matching

    Input

    Controls how strictly the AI evaluates contextual similarity (problem description, resolution steps, metadata) during KB generation and retrieval. Higher values improve contextual accuracy but may limit matches.

    Search Results Count

    Input

    Specifies the maximum number of KB articles returned in search results. This helps control UI clutter and ensures users see a manageable list of relevant KBs.

    Email Attachments Limit

    Input

    Sets the maximum number of KB articles that can be attached to ticket response emails. The system prioritizes the most relevant KBs based on similarity score and attaches them up to the defined limit.

    Processing Timeout

    Input

    Specifies the maximum time (in seconds) the system waits for an AI response before timing out. If exceeded, the operation is stopped and handled as a failure or fallback scenario.

    Remove Phone Numbers

    Toggle

    Removes phone numbers from KB articles to ensure privacy and compliance with data protection policies.

    Remove IP Addresses

    Toggle

    Filters out IP addresses from KB content to prevent disclosure of infrastructure-level details.

    Remove Server Names

    Toggle

    Removes server names and host identifiers from KB content to avoid exposing internal system details.

    Use Placeholders

    Toggle

    Replaces sensitive information with placeholders such as [USER], [EMAIL], or [SERVER] rather than removing it completely, preserving context while maintaining privacy.

    Max Solution Length

    Input

    Defines the maximum length of the solution section to ensure structured, readable, and actionable resolution steps.

    Max Keywords Count

    Input

    Specifies the maximum number of keywords that can be associated with a KB article, helping improve searchability without overloading metadata.

    Enable Data Sanitization

    Enables or disables sanitization for all AI requests before the AI model processes the data.

    When enabled, sensitive information is sanitized before being sent to AI services.

    Send Faker Data to AI Model

    Replaces sensitive values with realistic synthetic substitutes instead of placeholders. Original values are automatically restored in AI responses via reversible mapping.

    Enable All Categories

    Enables or disables all sanitization category toggles together.

    Enabling this option automatically enables all category-based sanitization controls.

    MAC Address

    Enable Knowledge Base

    Toggle

    Enables or disables the Knowledge Base feature across the platform. When enabled, the system enables AI-driven KB creation, similarity-based retrieval, and the attachment of KB articles to tickets and emails. When disabled, all KB-related AI operations, such as generation, search, and attachment, are restricted.

    KB Creation Standard

    Input

    Defines the minimum quality or eligibility score required for a ticket to be converted into a KB article. This ensures that only meaningful and well-resolved tickets are considered for KB creation. Lower values increase the volume of KB creation, while higher values enforce stricter quality control.

    Similarity Threshold

    Input

    Enable Smart KB Suggestions

    Toggle

    Enables AI-powered semantic search to suggest relevant KB articles during ticket creation, updates, and search operations. When enabled, users receive contextual recommendations based on issue descriptions and activity.

    Search Relevance

    Input

    Response Consistency

    Input

    Controls the variability of AI-generated content. Lower values produce more deterministic, consistent responses, while higher values allow greater variation and creativity in generated KB content and responses.

    Max Retries

    Input

    Defines the number of retry attempts for failed AI or API requests. This ensures temporary failures (e.g., network issues or provider delays) are retried before marking the operation as failed.

    Max Tokens Per Request

    Input

    Remove Personal Information

    Toggle

    Enables removal of personally identifiable information (PII) from KB content. When disabled, all related privacy filters are disabled as well, allowing the original data to remain in KB articles.

    Remove Email Addresses

    Toggle

    Max Title Length

    Input

    Defines the maximum allowed length for KB titles. This ensures titles remain concise, readable, and suitable for search indexing.

    Max Problem Length

    Input

    Save Settings

    Button

    Saves all configured values and applies them across KB generation, search, and processing workflows. Changes take effect immediately after saving.

    Reset to Default

    Button

    Conversation Summary [AI Generated]

    Toggle

    Automatically generates a concise summary of ticket conversations, including interactions, updates, and resolutions. When enabled, users can quickly understand ticket context without reviewing full conversation threads. When disabled, summaries are not generated, and users must review the complete ticket history manually.

    Text Enhancement

    Toggle

    Conversation Summary [AI Generated]

    Toggle

    Generates a summary of request-related interactions, approvals, and updates. Helps users quickly understand the progress of requests and decisions without having to review all activity logs.

    Text Enhancement

    Toggle

    Conversation Summary [AI Generated]

    Toggle

    Generates a summarized view of problem investigation, discussions, and resolutions. Helps users quickly understand the overall problem lifecycle and key decisions.

    Text Enhancement

    Toggle

    Conversation Summary [AI Generated]

    Toggle

    Summarizes change discussions, approvals, and implementation notes. Provides a quick overview of the change lifecycle and decision points.

    Text Enhancement

    Toggle

    Conversation Summary [AI Generated]

    Toggle

    Generates summaries of release activities, updates, and deployment discussions. Helps users quickly review release progress and outcomes.

    Text Enhancement

    Toggle

    Allow Process Classification

    Toggle

    Automatically classifies incoming emails into tickets or requests using AI. Reduces manual effort in identifying and routing incoming requests.

    Enable Service Classification

    Toggle

    Enable Bot Assistants

    Toggle

    Allows AI bots to provide automated responses, suggestions, and assistance across the platform. Helps resolve common queries more quickly and reduces the manual workload for support teams.

    Enable SLA Prediction

    Toggle

    Uses AI to analyze ticket patterns and predict potential SLA breaches or delays. Enables proactive action to maintain SLA compliance and avoid violations.

    Enable AI Similar Ticket Merge

    Toggle

    Automatically detects and merges duplicate or similar tickets based on content similarity. Improves efficiency by reducing duplicate efforts and consolidating related issues.

    Rule-Based Similar Incident Sidebar

    Toggle

    Data Sanitization Configuration

    How does it work

    AI Knowledge Base

    Configuration

    Enable Knowledge Base

    KB Quality Settings

    User Experience Settings

    AI Behavior Settings

    AI Technical Settings

    Data Privacy Settings

    KB Content Length Limits

    Actions

    Ticket – AI Configuration

    Configuration

    Request – AI Configuration

    Configuration

    Problem – AI Configuration

    Configuration

    Change – AI Configuration

    Configuration

    Release – AI Configuration

    Configuration

    AI Service Classification

    Configuration

    Bot Assistants

    Configuration

    SLA Prediction

    Configuration

    Similar Ticket Merge

    Configuration

    Knowledge Base
    Change
    SLA

    john@company.com → user1@sanitizer.example

    Redacts MAC addresses in colon, dash, and Cisco dot formats.

    Determines how closely a new ticket or query must match an existing KB article for it to be reused or updated. Higher thresholds ensure more accurate matches but may reduce reuse, while lower thresholds allow broader matching.

    Defines the relevance score threshold for displaying KB articles in search results. Higher values ensure only highly relevant KBs are shown, while lower values allow more results with broader matching.

    Limits the number of tokens processed per AI request. This helps control response size, processing cost, and performance, especially when handling large KB content.

    Automatically detects and removes email addresses from KB content to prevent exposure of sensitive user or organizational data.

    Limits the length of the problem description section in KB articles to maintain clarity and avoid excessively long content.

    Resets all configuration fields to predefined system default values. Useful for reverting incorrect configurations or restoring recommended settings.

    Enhances ticket content with AI, improving grammar, clarity, tone, and structure. When enabled, users can rephrase, expand, or refine responses before sending. When disabled, responses remain unchanged and fully manual.

    Improves request descriptions and responses by rephrasing and structuring content for better readability and professionalism. Ensures consistent and clear communication across request workflows.

    Enhances problem descriptions, root-cause details, and resolution notes through AI-based improvements. Ensures clarity and consistency in problem documentation.

    Enhances change request details, implementation plans, and communication using AI-powered text improvements. Helps maintain structured and clear change documentation.

    Improves release notes, descriptions, and communication content using AI enhancements. Ensures professional and clear release communication.

    Enables AI-based service classification based on ticket/request content. When enabled, AI dynamically assigns categories. When disabled, classification must be done manually.

    Displays similar incidents in a sidebar based on predefined rules when viewing a ticket. Helps agents quickly identify related issues and reuse existing solutions.

    Ticket
    Request
    Problem
    Release
    Service Classification
    Bot Assistants
    Ticket

    Username & Password Default

    View the default authentication option.

    Allows users to sign in using their registered email address and password.

    This is the default authentication method in Infraon.

    Mobile Number & SMS

    Enable or disable the authentication option and configure the SMS gateway.

    Allows users to sign in using their registered mobile number and an SMS OTP.

    Configure the primary SMS gateway and, optionally, a secondary gateway to send OTP messages.

    Email-Based 2FA

    Enable the option and configure OTP settings and the email template.

    Allows users to verify their identity using an OTP sent to their registered email address.

    Administrators can configure OTP verification limits, validity, user-level 2FA overrides, and the email template.

    Allows users to sign in to Infraon using their registered email address and password. This is the default authentication method and is enabled by default. Users enter their credentials on the login page to access the application.

    Configure an SMS gateway to send OTPs to users' registered mobile numbers. A primary SMS gateway is required, and a secondary gateway can be configured as an additional option.

    Standard Authentication | Mobile Number & SMS Configuration

    Label

    Action

    Description/Example

    Primary – SMS Config Type

    Select the configuration type.

    Select an SMS Gateway to configure the gateway used to send OTP messages.

    Title *

    Email-based 2FA requires users to verify their identity using an OTP sent to their registered email address. When enabled, the system displays the email OTP verification screen after successful primary authentication.

    To configure Email-Based 2FA, enable the option and open the configuration using the edit option. Configure the OTP settings and email template, then save the changes.

    Standard Authentication | Email-Based 2FA Configuration

    Label

    Action

    Description/Example

    Max OTP Login Attempts *

    Enter a number.

    Specify the maximum number of OTP verification attempts allowed during a login session.

    Example: Entering 5 allows up to five verification attempts.

    OTP Validity (Minutes) *

    Single Sign-On (SSO) allows users to access the Infraon portal using an external identity provider instead of managing separate login credentials. Infraon supports Microsoft SSO, Google SSO, OpenID Connect (OIDC), Security Assertion Markup Language (SAML) SSO, Secure Pass SSO, and SSO Configuration.

    Label

    Action

    Description/Example

    Microsoft SSO

    Enable or disable the option.

    This option leverages the power of Single Sign-On (SSO) for a more convenient and potentially more secure login experience.

    Users can log in to the Infraon Infinity portal using their existing Microsoft credentials, eliminating the need to manage separate passwords for the platform.

    Relying on Microsoft's robust authentication infrastructure improves user experience and potentially enhances security.

    Google SSO

    Microsoft Single Sign-On (SSO) allows users to sign in to Infraon using their Microsoft accounts without entering separate Infraon credentials.

    To configure Microsoft SSO, enable the option and configure the SSO Allowed Domains field to specify which email domains are permitted to sign in. Submit the changes to apply the configuration.

    Google Single Sign-On (SSO) allows users to sign in to Infraon using their Google accounts without entering separate Infraon credentials.

    To configure Google SSO, enable the option and configure the SSO Allowed Domains field to specify which email domains are permitted to sign in. Submit the changes to apply the configuration.

    OpenID Connect (OIDC) is an authentication protocol that allows users to sign in to Infraon using an external identity provider. It verifies the user's identity and enables single sign-on (SSO).

    To configure OIDC, enable the option and click the Edit icon to open the configuration settings. Enter the required identity provider details, such as Client ID, Client Secret, Issuer, Auth Scope, authorization and logout endpoints, and configure role mapping. Save the settings to apply the configuration. You can click the Edit icon again to modify the settings when required.

    Single Sign-On| OIDC Configuration

    Label

    Action

    Description/Example

    Client ID *

    Enter text.

    Enter the client identifier provided by the OIDC identity provider.

    Client Secret *

    SAML SSO configuration includes service provider settings, identity provider settings, identity provider claims, role mapping, and additional user configuration.

    Enable the SAML SSO option to open the configuration sidebar. Complete the mandatory fields and submit the configuration. Once saved, the SAML option remains enabled, and the Edit option is displayed on the SAML card.

    Single Sign-On| SAML SSO Configuration

    Label

    Action

    Description/Example

    Service Provider URL *

    Enter the service provider URL.

    Specifies the base URL used by Infraon for SAML authentication. The related service endpoints are populated using this URL.

    Secure Pass SSO allows users to sign in to Infraon through the configured Secure Pass authentication mechanism without entering their Infraon credentials separately.

    To configure Secure Pass SSO, enable the option and click the Edit icon to open the configuration settings. Update the required details and submit the changes. You can use the Edit icon again to modify the configuration when required.

    Single Sign-On| Secure Pass SSO Configuration

    Label

    Action

    Description/Example

    Client ID *

    Enter text.

    Enter the client identifier provided by Secure Pass.

    Client Secret *

    Select the allowed email domains for Single Sign-On (SSO) to specify which domains can be used by users to sign in to Infraon through Microsoft or Google authentication. This restricts SSO access to users whose email addresses belong to the selected domains.

    The Security & Customization settings allow administrators to control login access, configure CAPTCHA validity, and customize the login page.

    Label

    Action

    Description/Example

    Configure Allowed Client IP Address

    Enter the IP address range or subnet.

    Specify the IP address range or subnet authorized to log in to Infraon.

    CAPTCHA Configuration

    Set the Expiry Duration in hours.

    Configure the IP addresses, IP ranges, or subnets permitted to access Infraon. You can enter the IP details manually or import them using a CSV file. A maximum of 1,000 rows is allowed for CSV uploads. If both the IP list and CSV data are provided, the CSV data takes priority. Click Submit to apply the configuration.

    After submitting, click the Edit icon to modify the allowed client IP addresses or update the configuration when required.

    Security & Customization | Configure Allowed Client IP Address

    Label

    Action

    Description/Example

    IP Address

    Enter the allowed IP address, IP range, or subnet.

    Specifies the client IP addresses permitted to log in.

    Example: 10.0.5.24 or 192.168.1.0/24.

    Import from CSV

    Configure the CAPTCHA validity duration to control how long a successful CAPTCHA verification remains valid. Users are prompted to complete CAPTCHA verification again after the configured duration expires.

    To configure CAPTCHA, enable the option and click the Edit icon to modify the validity duration. Set the required duration within the allowed range and submit the changes to save the configuration. You can use the Edit icon again to update the settings when required.

    Login Page Configuration allows administrators to customize the login page's text, images, colors, links, and supporting resources.

    Enable the Login Page Configuration option and click Edit to modify the available settings. After completing the changes, click Submit to save them.

    Security & Customization | Login Page Configuration

    Label

    Action

    Description / Example

    Username Field Label

    Enter the required label

    Displays “E-Mail ID” instead of “Username/E-mail ID” on the login page.

    Label

    Action

    Standard Authentication

    Description/Example

    Username & Password Default

    Mobile Number & SMS

    Note: After configuring and submitting the settings, click the Edit icon to modify the SMS gateway configuration.

    Email-Based 2FA

    Note: You can use the Edit icon again to modify the configuration when required.

    Single Sign-On (SSO)

    Microsoft SSO

    Google SSO

    OIDC

    SAML SSO

    Secure Pass SSO

    Note: Users must be registered by an administrator before they can sign in through Secure Pass. After authentication, registered technicians are redirected to the main portal, while registered requesters are redirected to the self-service portal. If a user is registered as both a technician and a requester, the technician portal takes priority.

    SSO Configuration

    Security & Customization

    Configure Allowed Client IP Address

    CAPTCHA Configuration

    Login Page Configuration

    Teams

    On the Infraon platform, a team consists of users grouped together. Teams can be categorized based on a reporting manager, technical skills, support level (L1, L2), role, etc. These are the foundations for managing user groups responsible for handling various ITSM operations such as approvals, ticket resolutions, change implementations, and release activities.

    Users are assigned to multiple teams, and teams are assigned to specific modules.

    What you see on the screen

    The Teams page lists all existing teams and offers options to filter, search, add, or manage teams individually or in bulk. From this page, you can view, add, edit, and delete existing pages.

    Teams | Basic Details

    Label

    To add a new team, navigate to the Teams page and click the Add Team button at the top right corner. This opens the Create Team window, where team information and functional attributes can be defined.

    Create Team | Basic Details

    Team types define the role the team plays across various modules and workflows. When creating or editing a team, select the appropriate team type.

    Team Type | Add Teams

    Users can associate the team with a specific location. This helps in aligning team responsibilities based on regional or site-specific operations.

    The section contains two dropdown fields:

    Service Request/ Ticket Location Mapping

    How It Works

    • Admin configures teams with appropriate location categories and values (e.g., Region: South, Location: Bangalore).

    • When a user raises a service request or ticket, their default or selected location is matched against team configurations.

    • The system automatically assigns the request to the team mapped to that location.

    • The team receives the ticket for further action without requiring manual routing.

    Example Use Case

    • A user from “Mumbai – Tower A – 2nd Floor” requests printer support.

    • The system detects their location (requester) and checks against team mappings.

    • That location is mapped to the “Facility Support – West” team.

    • The service request is instantly routed to the correct team, ensuring minimal resolution delays.

    While creating a team, admins must configure the team members who will be part of that group. The Staff Selection section offers two configuration tabs to define how staff are added.

    This configuration helps identify the team’s core skills and areas of specialization (such as ITAM, NMS, NCCM, Log Management, etc). It also allows you to establish a hierarchy of support staff members who will receive notifications and assist in resolving module-specific tasks.

    An approval team is a group of designated staff members responsible for reviewing and approving requests. Team members are added as staff and can be assigned a specific approval sequence to ensure requests follow a structured approval flow.

    The Request Signature option allows organizations to define digital signature requirements for approval teams. Team members who have already configured their signature in can be added to the signature sequence. Signatures are collected in the configured order and can be displayed in documents after approvals are completed.

    Label
    Action
    Description / Example

    Percentage-Based Approval Sequence

    In enterprise environments where actions require team approvals, waiting for unanimous consent can delay critical operations. The Infraon platform makes this process more flexible, configurable, and scalable for team sizes and business needs.

    What is Minimum Approval Percentage?

    The Minimum Approval Percentage setting defines the minimum percentage of team members who must approve a request or action for it to proceed.

    How Does It Work?

    When a request (like a change, ticket, or service approval) is sent to an approval team:

    • The system checks the total number of approvers in the team.

    • Based on the configured percentage (e.g., 60%, 80%), it calculates how many approvals are needed.

    • If that number of users approves, the action is automatically accepted, even if other members have not responded.

    This mechanism enables faster decision-making and reduces bottlenecks in workflows.

    1. Response Required (Toggle Switch)

    • Enabled (ON):

    The system will wait for all team members to respond before proceeding. This is suited for highly sensitive workflows where a unanimous or whole team review is mandatory.

    • Disabled (OFF):

    The system only waits until the minimum percentage of approvals is received. Once that condition is met, the action is approved and executed, even if other members haven’t responded.

    2. Minimum Approval Percentage

    This dropdown field allows you to choose the threshold (e.g., 50%, 60%, 80%, 100%). You can set values based on your organization's comfort level with partial consensus.

    Example Breakdown:

    • Team Size: 5 Approvers

    • Minimum Approval: 60%

    • Required Approvals: 3 (rounded from 60% of 5)

    • If three members approve the action, the system considers it valid, even if the remaining two have not taken any action.

    The UI will display:

    “Minimum 3 from 5 users' approval needed to complete the action” — updated dynamically.

    Background

    Infraon uses Infraon Infinity to manage internal change requests for production systems. Its Change Advisory Board (CAB) includes 10 infrastructure, security, development, and QA team members.

    Challenge

    Usually, only 3–4 core members actively participate in reviews. Waiting for all 10 members to approve often delays release cycles.

    Solution

    Using the Percentage-Based Approval feature, Infraon configures:

    • Minimum Approval Percentage: 70%

    • Response Required: OFF

    Result

    • The system only needs 7 out of 10 members to approve.

    • Even if the remaining three do not respond, the change is processed promptly.

    • This reduces approval cycle times from 3 days to under 1 day.

    • It aligns with their internal governance policy without slowing down DevOps.

    Notes

    • Security-sensitive requests still follow a 100% response policy (Response Required = ON).

    • Infraon uses different thresholds for different teams using team-specific configurations.

    • Set lower percentages for large and cross-functional teams to streamline decisions.

    • Set higher thresholds or turn on "Response Required" for high-risk or compliance-critical workflows.

    This configuration tab is enabled when adding an Operation and Technical Team.

    Operation and Technical Team - Used to configure auto-assignment of tickets.

    What is Auto Assignment?

    An alert is raised when a ticket lands in the service desk queue. Either a technician self-assigns it, or a team leader assigns it to the team. With manual intervention, tickets may be picked based on ease of resolution, making it unfair for other technicians. New tickets may also be in the queue for too long while waiting to be assigned, impacting the SLAs. Auto assignment of tickets removes manual intervention, ensuring fairness and timely assignment. Infraon offers three methods to define auto-assignment.

    Round Robin

    Round Robin is the simplest way of assigning tickets, where tickets are assigned equally to active technicians in a circular order. It is recommended for businesses where tickets are raised to follow up on orders, requests, etc. Using this to auto-assign tickets helps save time on the manual assignment of tickets.

    Use-case - An e-commerce business where tickets are raised to know order status, delays in delivery, or refund status, etc. Since these are information-based tickets and no troubleshooting is required, the time spent on each ticket is minimal. Using the Round Robin method ensures that tickets are assigned equally and orderly.

    Load Balancer

    The load-balanced method assigns tickets based on the technician's load and is recommended for businesses offering a wide range of services, where the resolution time is different for each. Using the Load-Balanced method ensures that the technicians have a balanced workload while working on a ticket. When a new ticket is raised, the technician with the least load is auto-assigned. Tickets are assigned based on the ticket queue's SLA, priority, and criticality. Thresholds must be defined to select this method.

    Use-case - A technical support center for a product that offers 24/7 support where tickets are raised throughout the day. Some tickets may be inquiries, while others might have a long resolution. A round-robin method may not make sense here. The load balancer method checks the technician's current load before assigning new tickets. This way, technicians are not burdened with work.

    Skill Based

    The skill-based method is used when the organization offers multiple categories/levels of support. It is recommended for organizations providing support globally or across a wide range of products/services. Skill-based assignment ensures that the right technician assigns the tickets by matching their skill and level.

    Use-case - A business that offers support or services on multiple products, regions, and time zones, offering multi-lingual support. Here, tickets must be assigned based on the skill of the technician. The technician must be skilled in the language selected by the customer, know about the product chosen, etc. A skill-based allocation is best platformed for this.

    Delegate Configuration

    This tab allows administrators to set up backup approvers or staff in case the primary team members are unavailable. Delegation ensures continuity of operations by routing approvals or tasks to alternate users.

    Once all fields are added, click Submit to finalize the team setup.

    Enter text.

    Enter a name to identify the SMS gateway configuration.

    Add Country Code

    Enable or disable the option.

    Configure whether the country code should be added to the recipient's mobile number, based on the gateway requirements.

    Use GET Request

    Enable or disable the option.

    Configure whether the SMS gateway request uses the GET method.

    Use HTTPS

    Enable or disable the option.

    Enable this option to use HTTPS for the SMS gateway request.

    URL *

    Enter the gateway URL.

    Enter the SMS gateway endpoint URL, such as https://. Use the URL provided by the SMS gateway provider.

    Status Code

    Enter the required status code.

    Specify the HTTP status code used to identify a successful gateway response, according to the provider's configuration.

    Send SMS Individually

    Enable or disable the option.

    Configure whether SMS messages are sent individually to recipients.

    Request Parameters

    Click Add to add a parameter and the delete icon to remove an added parameter. Enter the key and value, and configure the parameter options.

    Add the parameters required by the SMS gateway API.

    • Enter the parameter name in Key and its corresponding value in Value.

    • Enable Pass to Header to include the parameter in the request header, or Pass to Query to include it in the query string, as required by the gateway API.

    Secondary – Enable Secondary SMS Gateway

    Enable or disable the toggle.

    Enable this option to configure a secondary SMS gateway.

    When enabled, the secondary gateway configuration fields are available.

    Submit

    Click Submit after completing the configuration.

    Saves the SMS gateway settings. Review the primary and secondary configurations, if applicable, before submitting.

    Enter a number.

    Specify how long the generated OTP remains valid.

    Example: Entering 3 means the OTP is valid for three minutes.

    Override User-Based 2FA (User Account Settings)

    Enable or disable the option.

    Configure whether the standard Email-Based 2FA settings override the 2FA configuration defined in individual user account settings.

    Subject *

    Enter text.

    Specify the subject line of the email containing the login OTP.

    Email Body *

    Enter or edit the email content.

    Customize the email message sent to users. Include the supported macros {{User}}, {{OTP}}, and {{Expiry Timeout}} to insert the user's name, generated OTP, and OTP expiry timeout, respectively.

    Save

    Click Save after configuring the settings and email template.

    Saves the Email-Based 2FA configuration and template.

    Enable or disable the option.

    This login method prioritizes both convenience and security.

    Users can access the Infraon portal with their existing Google credentials, eliminating the need for separate login details.

    OIDC

    Enable the option and configure the required settings.

    Enables authentication through an OpenID Connect identity provider using the configured client credentials, issuer, endpoints, and role mapping.

    SAML SSO

    Enable the option and configure the service provider and identity provider details.

    Enables authentication through a SAML-compatible identity provider. Administrators can configure endpoints, bindings, identity provider claims, and role mapping.

    Secure Pass SSO

    Select Secure Pass SSO and configure the required settings.

    Enables authentication through Secure Pass digital identity, with access determined by the user's registration and role.

    SSO Configuration (Microsoft, Google)

    Select the SSO Allowed Domains

    Configure single sign-on (SSO) using Microsoft or Google as the identity provider.

    Specify the email domains permitted to sign in through SSO.

    Users with email addresses matching the configured domains are allowed to authenticate.

    Example: company.com allows users with email addresses such as user@company.com to sign in.

    Enter text.

    Enter the client secret associated with the registered application.

    Issuer *

    Enter a URL or issuer value.

    Specify the issuer URL of the OIDC identity provider.

    Auth Scope *

    Enter the required scopes.

    Specify the scopes requested during authentication, based on the identity provider's configuration.

    Auth *

    Enter the authentication endpoint.

    Specify the endpoint used to initiate authentication with the identity provider.

    Logout *

    Enter the logout endpoint.

    Specify the endpoint used to log users out of the identity provider, where supported.

    Enter Role *

    Enter a role value.

    Enter the external role name to be mapped to an Infraon role.

    Select Role *

    Select a role.

    Select the corresponding Infraon role for the specified external role.

    Default Role

    Select a role.

    Select the role assigned by default when no specific role mapping applies, according to the system's configuration.

    Create User If Not Exist

    Enable or disable the option.

    Configure whether a user account is created automatically when the authenticated user does not already exist in Infraon.

    Generate Email If Email Not Found

    Enable or disable the option.

    Configure whether Infraon generates an email address when the identity provider does not supply one.

    Submit

    Click the Submit option

    Click the Submit option to save the OIDC configuration.

    Client ID *

    Enter the client identifier.

    Enter the identifier used to identify the registered application or service provider, as required by the configuration.

    Assertion Consumer Service URL *

    View the generated URL.

    Displays the service provider endpoint that receives the SAML authentication response. The URL contains the service provider URL and the fixed path /ux/saml/ssocallback.

    The path section is read-only.

    Assertion Consumer Service Binding *

    Select a binding.

    Select the binding used to transmit the SAML response to the assertion consumer service.

    Single SignOn Service URL *

    View the generated URL.

    Displays the service provider's SSO endpoint using the service provider URL and the fixed path /ux/saml/ssocallback.

    The path section is read-only.

    Single SignOn Service Binding *

    Select a binding.

    Select the binding used for the single sign-on service.

    Single SignOut Service URL *

    View the generated URL.

    Displays the service provider's single sign-out endpoint using the service provider URL and the fixed path /ux/saml/sls.

    The path section is read-only.

    Single SignOut Service Binding *

    Select a binding.

    Specifies the binding used for the service provider's single sign-out service.

    The default value is urn:oasis:names:tc:SAML:2.0:bindings:HTTP-Redirect.

    Identity Provider URL *

    Enter the identity provider URL.

    Enter the identity provider URL used for SAML authentication.

    The identity provider's service endpoints are populated using the configured URL where applicable.

    Entity ID *

    Enter the entity identifier.

    Enter the entity identifier provided by the identity provider.

    x509cert

    Enter or provide the certificate.

    Configure the identity provider's X.509 certificate used to validate SAML responses or assertions, as supported by the configuration.

    Single SignOn Service URL *

    Enter a URL.

    Specifies the endpoint that processes SAML authentication requests.

    The URL configuration supports the identity provider URL and an additional endpoint path.

    Single SignOn Service Binding *

    Select a binding.

    Select the binding supported by the identity provider's SSO service.

    Single SignOut Service URL *

    Enter a URL.

    Specifies the endpoint used for logout through the identity provider.

    The URL configuration supports the identity provider URL and an additional endpoint path.

    Single SignOut Service Binding *

    Select a binding.

    Select the binding supported by the identity provider's single sign-out service.

    Email Key *

    Enter the claim name.

    Specify the claim containing the user's email address.

    Role Key *

    Enter the claim name.

    Specify the claim containing the user's role information.

    First Name Key *

    Enter the claim name.

    Specify the claim containing the user's first name.

    Last Name Key *

    Enter the claim name.

    Specify the claim containing the user's last name.

    User Name Key

    Enter the claim name.

    Specify the claim containing the user's username, if provided by the identity provider.

    Enter Role *

    Enter a role value.

    Enter the role name received from the identity provider.

    Select Role *

    Select a role.

    Map the external role to the corresponding Infraon role.

    Default Role

    Select a role.

    Select the default Infraon role to assign when no specific role mapping applies, according to the system's configuration.

    Create User If Not Exists

    Enable or disable the option.

    Configure whether Infraon creates a user account when an authenticated user does not already exist.

    Generate Email If Email Not Found

    Enable or disable the option.

    Configure whether Infraon generates an email address if the identity provider does not provide one.

    When enabled, the Email Suffix option will display.

    Email Suffix *

    Enter a suffix.

    Specify the email suffix used when generating an email address for a user whose email is not provided by the identity provider.

    Submit

    Click Submit

    Click the Submit button to save the SAML SSO

    Enter text.

    Enter the client secret associated with the Secure Pass application.

    Environment *

    Select an environment.

    Select the environment in which Secure Pass authentication will operate, such as Staging.

    Assurance Level (ACR) *

    Select an assurance level.

    Select the required authentication assurance level: SOP1 – Low (email/mobile verified), SOP2 – Medium (advanced signature), or SOP3 – High (biometric).

    Scope

    Enter or retain the default value.

    Specifies the scope for Secure Pass profile data. Retain the default scope unless Secure Pass support advises otherwise.

    Callback URL

    View and register the URL.

    Register this URL in the Secure Pass developer portal as the redirect URI for the application.

    Redirect URI Override

    Enter a URL, if required.

    Use this field only for sandbox or testing when the registered redirect URI differs from the Callback URL. Leave it blank in production unless otherwise required.

    Submit

    Click Submit

    Click Submit to save the Secure Pass

    Specify how long CAPTCHA remains valid after a successful login.

    Once the configured duration expires, users must complete CAPTCHA validation again.

    The default expiry duration is 1 hour.

    Login Page Configuration

    Customize the login page settings.

    Customize the login page settings by enabling the login page configuration feature.

    After enabling it, click Edit to modify the login page settings, including field labels, header and footer, content, colors, font size, and links/

    Select Import from CSV, then upload a CSV file using Browse or drag and drop the file.

    Allows multiple client IP addresses or ranges to be imported from a CSV file.

    A maximum of 1,000 rows is allowed.

    Download Sample CSV

    Click Download sample CSV file here.

    Downloads a sample CSV file to help you prepare the import file in the required format.

    Submit

    Upload the CSV file or enter the IP details, then click Submit to apply the configuration.

    Saves the allowed client IP address configuration. When both the IP list and CSV data are provided, the CSV data takes priority.

    Password Field Label

    Configure the password field label

    Defines the label displayed for the password field.

    Sign-in Button Text

    Configure the button text

    Defines the text displayed on the sign-in button.

    Self Service Link Text

    Configure the link text

    Defines the text displayed for the self-service link.

    Header Text

    Enter the header text

    Displays the configured text in the login page header.

    Header Description

    Enter the header description

    Displays supporting information below the header text.

    Header Image

    Upload or configure the header image

    Displays the configured image in the login page header.

    Footer Text

    Enter the footer text

    Displays the configured text in the footer section.

    Footer Description

    Enter the footer description

    Displays supporting information in the footer.

    Footer Image

    Upload or configure the footer image

    Displays the configured image in the login page footer.

    Text Color

    Choose a text color

    Select a color that contrasts with the login page background image to ensure readability.

    Font Size

    Select Small, Medium, or Large

    Sets the font size for the applicable login page text.

    Links

    Configure the required links

    Provides access to relevant pages or resources from the login page.

    Documents

    Upload supporting documents

    Supports PDF, DOC, DOCX, XLS, XLSX, PPT, PPTX, TXT, CSV, JPG, PNG, GIF, BMP, and WEBP files, with a maximum size of 12 MB per file.

    Registration Link Text

    Configure the registration link

    Defines the text displayed for requester registration.

    Restrict to Specific Domains

    Configure domain restrictions

    Restricts requester registration to approved domains when enabled.

    Approved Domains

    Specify permitted domains

    Lists the domains allowed for requester registration.

    Live Clock

    Configure the live clock section

    Provides the live clock feature on the login page, if enabled.

    User Guide

    Configure the user guide resource

    Makes the configured user guide available from the login page.

    Get the Mobile App

    Configure mobile app links

    Provides links to the app on the App Store and Google Play.

    Announcement

    Display eligible announcements

    Displays announcements without a Visibility Config restriction. Each announcement remains visible until its publish end date.

    Submit

    Click

    Click the submit button to save the changes made on the login page.

    Used to send email notifications to multiple members.

    Example: infraon-support@company.com. This should be a distribution group.

    Description*

    Enter description

    Add notes or context about the team. Example: Handles all L1 ticket escalations for the Bangalore region.

    Module*

    Select from the dropdown

    Choose the module to which the team belongs. Example options include: Ticket, Change, Problem, Service Request, Release, Live Chat, etc.

    Team Type*

    Select from the dropdown

    Choose the type of team from the available classifications. See the Team Type Tab below for more details.

    Owners of the Team*

    Select responsible users

    Mandatory. These users manage the team’s structure, approvals, and visibility rules.

    Department

    Select from the dropdown

    Assign the team to a specific business department. Example: IT, Facilities, Procurement.

    Business Hour Profile

    Select applicable time profile

    Maps the team’s operating hours, which impact SLAs and ticket routing. Example: 24x7, Weekdays 9 AM–6 PM.

    Assigned to incident resolution, asset handling, or technical tasks in Ticket, Problem, or Project.

    Servicedesk

    Frontline users who log, categorize, assign, and respond to service tickets.

    Typically used in Ticket or Live Chat modules.

    Review

    Users involved in periodic review processes, compliance checks, or validations.

    Used in Knowledge Base, Change Management, or Problem for formal assessments.

    CAB

    The Change Advisory Board is responsible for reviewing and approving regular changes.

    Used in Change Management for predefined change approval workflows.

    Expert

    Subject matter experts performing advanced-level configurations or troubleshooting.

    Ideal for complex issue resolution in Change, Problem, or Release.

    ECAB

    Emergency CAB for urgent changes requiring immediate approvals.

    Critical for fast-track Emergency Changes in Change Management.

    When adding new expertise, input the tag name (e.g., log management), select the Type as Group, and then click Submit.

    Enable send notifications to additional internal/external users

    Toggle to activate

    When enabled, notifications can be sent to selected support staff even if they are not directly assigned to the task.

    Select Expertise

    Choose an expertise tag from the dropdown.

    Determines the expertise area being configured for the support hierarchy.

    Example: ITAM.

    Description

    Enter a short explanation (optional)

    Provide additional information about the expertise.

    Example: Handles hardware asset tracking.

    Add Users

    Select users for the support hierarchy level.

    Choose users to notify or assign responsibilities within a level.

    (+) Icon

    Add another hierarchy level

    Add multiple levels of escalation or expertise-specific staff.

    Example: Add Level 2 with different users.

    Add

    Click to add another expertise mapping.

    Configure support hierarchy for multiple expertise tags (e.g., ITAM and NCCM).

    Choose the first-level approvers for the team. These users will be prompted for approval first. Example: Abdul, Abhirup, Alex Carry

    Add

    Click to add additional sequence rows.

    This option allows adding second-level (or more) approval steps. The approval request will move to the following sequence only after the prior sequence is completed.

    Sequence 2, 3...

    Select users for each additional sequence

    Define second-level or third-level approvers as needed. Example: Sequence 2 – John Doe, Sequence 3 – Team Lead

    Add

    Click to add additional signature rows

    Adds more signature levels to the configuration. Use this option when multiple users must sign the document in sequence.

    Signature 2, 3...

    Select users for each additional signature

    Choose the next user required to sign after the previous signature is completed. Signatures follow the configured order. Example: Signature 2 – Carter Cooper, Signature 3 – Finance Manager

    Delete

    Click the delete icon

    Removes the selected signature row from the sequence.

    Communicate the approval logic to team members to avoid confusion or delays.

    Enables delegation to a specific staff member. Useful when designated approvers or team members are unavailable.

    Delegate From

    Select a user from the dropdown

    Choose the user whose tasks or approvals will be delegated. Example: Select John Smith (Team Approver)

    Delegate To

    Select an alternate user from the dropdown

    Choose the delegate who will take over the responsibilities. Example: Delegate to Jane Doe (Alternate Approver)

    Add

    Click the add (+) button

    Adds the selected delegation pair to the team configuration. You can define multiple delegation rules.

    Action

    Description / Example

    Bulk CSV Update

    Click to download/upload template

    Enables mass editing or creation of teams. Steps:

    1. Click Bulk CSV Update

    2. Download the CSV template

    3. Fill in the required team data

    4. Upload the modified CSV to apply changes

    Add Team

    Click to open the team creation form.

    It opens the "Add Team" configuration page, where you can manually create a new team by selecting a module, team type, and members.

    Team Name

    View only

    Displays the name of the configured team.

    Example: Default Approval Team.

    Module

    View only

    Indicates the module the team is associated with, for example, ticket, change, and contract management.

    Type

    View only

    Specifies the team's functional role, such as Approval, CAB, Technical, or Servicedesk.

    Description

    View only

    Displays an internal note about the team’s purpose or assignment scope.

    Example: All changes will be visible to this team.

    Edit

    Click to modify the existing team.

    Opens the edit screen to update the module, team members, type, or description.

    Delete

    Click to remove a team

    Deletes the selected team from the inventory.

    Label

    Action

    Description / Example

    Team Name*

    Enter the team name.

    Mandatory field. A unique identifier for the team.

    Example: IT Service Desk – L1, Network Change Review Board.

    Group Email ID

    Team Type

    Purpose

    Usage Example

    Approval

    Users are responsible for reviewing and approving requests, changes, or releases.

    Used in Request, Change, or Release modules as part of approval chains or thresholds.

    Operational and Technical

    Label

    Action

    Description / Example

    Location Category

    Select a location category from the dropdown

    Defines the category under which the location falls.

    Example: Country, Region, State, etc.

    Select Value

    Choose the value based on the selected category

    Label

    Action

    Description / Example

    Staff Selection

    Choose between User Tags or Users

    Determines how team members are assigned. User Tags: Automatically includes users who are tagged with the selected criteria. Users: Allows manual selection from all active users in the system.

    Staff

    Select from the dropdown.

    Label

    Action

    Description / Example

    Expertise

    Select from the dropdown or enter to add a new expertise

    Identify the domain or technical skills for the team.

    Example: ITAM, NCCM, Log Management.

    Add Tag

    Label

    Action

    Description / Example

    Approval Sequence

    Click the toggle button to enable

    Activates the option to define multiple levels of approval. Once enabled, you can add users in the order in which approvals are to be received.

    Sequence 1

    Request Signature

    Click the toggle button to enable

    Activates digital signature configuration for the selected team. Once enabled, signature rows can be added to define who must sign the document.

    Signature 1

    Select from the dropdown

    Label

    Action

    Description / Example

    Delegate To Owner

    Toggle to enable

    This allows the delegation of approval or responsibility to the team owner. When enabled, tasks are redirected to the team owner.

    Delegate To Staff Member

    Instructions to 'Add Team'

    Create Team

    Fields marked with an asterisk (*) are mandatory.

    Team Type

    When a Team Type is selected, the system dynamically displays different configuration options based on that type. The configuration page adapts based on the team’s role, ensuring only the relevant options for that specific type are shown.

    Location

    Multiple values can be selected depending on the team’s configuration. For example, a regional support team can be associated with the South and North regions.

    The system determines the location using one of the following methods:

    • Asset Location – If the request/ticket is raised from a specific asset, its location is used.

    • Requester Location – The default location configured for the user is referenced.

    • Service Request Location – A location selected manually during request creation is considered.

    Staff Selection

    Expertise

    Approval Sequence

    Request Signature

    Advanced Configuration

    Recommendation: Keep this OFF for dynamic or time-sensitive workflows.

    If three members reject the request, the system will trigger the rejection flow since achieving the required 60% approval with only two remaining approvers is impossible.

    Use Case Scenario – Infraon

    Automatic Ticket Assignment

    Delegation is typically configured for team types such as Approval, CAB, and ECAB, where approval chains must be maintained.

    My Profile

    Enter shared group email (optional)

    Users who execute operational tasks, such as troubleshooting or maintenance.

    Displays location options based on the chosen category. Example: India, USA, Bangalore.

    Choose the appropriate user tags or individual users from the list based on the selected method. Example (User Tags): L1 Support, Network, Linux Admin Example (Users): John Smith, Anita Rao

    Enter the tag name and select the type.

    Select from the dropdown

    Choose the first user required to provide a signature. This user will be prompted first during the signing process. Example: Alex Alexander

    Toggle to enable

    Purchase Order

    How does it work

    Multiple pre-configured reports are available on Infraon. These can be customized, and new custom reports can also be added.

    What you see on the screen

    The Report Grid page displays all created reports, including their category, description, scheduling details, and available actions. Users can search, filter, create, schedule, and export reports directly from this page.

    It also provides visibility into scheduled reports and allows quick operations without opening individual reports.

    Report Grid | Basic Details

    Label
    Action
    Description/ Example

    Column Details | Report Grid

    Label
    Action
    Description/ Example

    Admins can enable hiding the requester’s info in reports to comply with data privacy regulations.

    Nested Grouping allows you to analyze Ticket data across multiple hierarchical levels within a single report. It helps in breaking down data step-by-step, enabling deeper visibility into ticket trends, ownership, and resolution patterns.

    This feature is currently available for the Ticket Summary Report and will be extended to other Summary Reports (Request, Problem, Change) in upcoming releases.

    • Navigate to Report → Add Report.

    • Select Ticket Summary Report.

    • Go to the Configuration tab.

    • Enable the Nested Grouping toggle.

    Nested Grouping | Configuration

    Label
    Action
    Description / Example

    Grouping Structures | Example

    Purpose
    Example

    After submitting the report configuration, the system opens the View Report page. This page displays the generated report based on the selected grouping fields, timescale, and configuration settings.

    For Nested Grouping reports, the page shows ticket data in a hierarchical tabular structure, allowing users to review grouped counts and calculated metrics such as MTTR and Percentage. Users can also reopen report settings, export the report output, or edit the existing configuration.

    Summary Report | View Report

    Label
    Action
    Description / Example

    Custom Fields support allows users to use workflow-specific custom fields as Filters and Columns in supported reports. This enhancement helps users generate more refined, context-specific reports by filtering and displaying data based on custom workflow attributes configured in the system.

    Custom fields are dynamically fetched from the associated workflows and made available in the report configuration screen.

    Custom field support is available for the following reports:

    • Incident Prediction Report

    • SLA Report

    • Ticket Assignment History

    • Ticket Count Summary

    Use custom columns when the default report fields do not meet your reporting needs. Common use cases include:

    • Calculate SLA utilization percentage

    • Convert minutes into hours

    • Compare elapsed time against target time

    • Derive resolution duration

    Use the Custom Columns section in SLA Report configuration to create calculated columns.

    To add a custom column:

    • Open Reports.

    • Select or create an SLA Report.

    • In the Configuration page, scroll to Custom Columns.

    • Click Add Column.

    Custom Column | Field Description

    Label
    Action
    Description

    The Formula Builder supports the following components.

    Fields

    You can use available SLA date, time, and duration fields, such as:

    • Creation Time

    • Last Update Time

    • Resolved Date

    • Assigned Time

    Operators

    The following operators are supported:

    • + Addition

    • - Subtraction

    • * Multiplication

    • / Division

    Functions

    The following functions are available:

    • SUM() – Adds all values

    • MIN() – Returns the smallest value

    • MAX() – Returns the largest value

    • AVG() – Returns the average value

    Units

    You can assign output units such as:

    • Seconds

    • Minutes

    • Hours

    • Percentage

    The formula expression is generated automatically based on the values selected in the Formula Builder.

    You can combine:

    • Fields + Operators

    • Fields + Input Values

    • Functions + Fields

    • Parentheses for grouped calculations

    Formula Configurations

    SLA Utilization Percentage

    Field
    Value

    Formula:

    Resolution Hours

    Field
    Value

    Formula:

    Average Hold Time

    Field
    Value

    Formula:

    After adding the Custom Columns, click Next to proceed to the Filter tab, then click Submit to save the report.

    Custom Fields support allows users to use workflow-specific custom fields as Filters and Columns in supported reports. This enhancement helps users generate more refined, context-specific reports by filtering and displaying data based on custom workflow attributes configured in the system.

    Custom fields are dynamically fetched from the associated workflows and made available in the report configuration screen.

    Custom field support is available for the following reports:

    • Incident Prediction Report

    • SLA Report

    • Ticket Assignment History

    • Ticket Count Summary

    Requesters

    Requesters are internal or external users who can raise incidents, service requests, and change requests in Infraon. Technicians, such as Tech Support Users or NOC Operators, can also raise incidents or requests on behalf of requesters.

    Requesters can access the to raise and track requests and access the Knowledge Base.

    The Requesters module allows administrators to create and manage internal and external requesters.

    Requesters can be added or managed using the following options:

    1. Add Requester

    Dropdown

    Used to generate on-demand (one-time) reports without saving or scheduling them. These reports are executed instantly based on selected parameters and are not stored in the report grid unless explicitly saved. Available Report: MRTG Report: Generates real-time graphical reports for network traffic and bandwidth utilization using MRTG data.

    Example: View a device's bandwidth usage over time.

    Statistics Report: Provides aggregated statistical data based on selected metrics (e.g., count, average, min, max). Example: Average CPU usage across devices for the last 7 days. Forecast Report: Predicts future trends based on historical data using predefined thresholds and patterns.

    Example: Forecast storage utilization for the next 30 days.

    Prediction Report: Uses analytical models to estimate future outcomes or behaviors based on existing data.

    Add Report

    Button

    Click to create a new report with configuration, filters, and scheduling options.

    Displays the report category (e.g., Asset Report, Audit Report).

    Description

    View only

    Displays a brief summary of what the report contains or represents. Example: “Asset report for update changes like hardware/software details.”

    Schedule Description

    View only

    Displays scheduling details if configured. Example: “Scheduled for every Sunday at 11:30 (Asia/Kolkata)”. If no schedule is set, this field remains empty or shows “-”.

    Actions

    Edit

    Click

    Opens the report configuration page to modify columns, filters, timescale, sorting, and other settings.

    Clone

    Click

    Creates a duplicate of the selected report with the same configuration. Users can modify and save it as a new report.

    Send Now

    Click

    Generates and sends the report immediately via configured channels (e.g., Email). Does not affect existing schedules.

    Schedule

    Click

    Opens the schedule configuration window to define report frequency (Once, Daily, Weekly, Monthly), time, and delivery method.

    Delete

    Click

    Permanently deletes the selected report from the system. This action cannot be undone.

    Export as CSV

    Click

    Downloads the report as a CSV file for external analysis or sharing.

    Export as PDF

    Click

    Downloads the report in PDF format with a structured layout and optional graphical representation.

    Export as XLSX

    Click

    Downloads the report as an Excel (XLSX) file for advanced data manipulation.

    Bulk Actions

    Delete

    Select + Click

    Select multiple reports using checkboxes and delete them in bulk. Useful for removing unused or duplicate reports.

    Email

    Enabling this toggle will obfuscate the requester’s email ID in reports to comply with data privacy regulations.

    Use the designated toggle switch to restore the requester's email display in the report interface for authorization.

    Select required fields under Nested Group By.

  • Choose the Timescale.

  • Click Preview to validate the structure.

  • Click Submit to save the report.

  • Hierarchy Levels

    Add multiple grouping levels

    Supports multi-level grouping to drill deeper into report data. Each additional level further categorizes the results of the previous level. Useful for layered analysis such as State → Team → Assignee.

    Level Sequence

    Arrange selected fields

    The order of selected fields determines how data is grouped in the report. The first field becomes the parent level, followed by child levels in sequence.

    Timescale

    Select report duration

    Defines the date range used for generating report data. Example: Last 30 Days, Last 180 Days, Last 365 Days, and other available ranges.

    Preview

    Click to generate sample output

    Displays the report results based on the current configuration before saving.

    Service Performance

    Impact Service → Team → Assignee

    Edit

    Click to modify report

    Opens the report configuration page where users can update columns, grouping fields, filters, timescale, visibility settings, or other report options, then save the changes.

    Ticket Escalation Notification
  • Ticket Feedback

  • Ticket Report

  • Ticket SLA Compliance

  • Ticket Summary

  • Report Template

  • Create business-specific KPI columns

  • Display aggregated values such as average or count

  • Enter the custom column name.

  • Click Formula Builder.

  • Build the formula using fields, values, operators, and units.

  • Click Save.

  • Continue report configuration and generate the report.

  • Formula Builder

    Click

    Opens the formula builder window to create calculations.

    Formula Expression

    Auto-generated

    Displays the formula based on selected fields and operators.

    Columns

    Select

    Choose an SLA field to use in the formula.

    Input Value

    Enter value

    Add numeric constants such as 60, 100, or 24.

    Operators

    Select

    Choose an arithmetic operator or a function.

    Units

    Select

    Select output format, such as Minutes or Percentage.

    Save

    Click

    Saves the custom formula.

    Re-Assigned Time
  • SLA Start Date

  • SLA End Date

  • Metric Expected Time

  • Metric Start Time

  • Metric Target

  • Total Elapsed

  • Total Elapsed (min)

  • Business Elapsed

  • Business Elapsed (min)

  • Non-Business Elapsed

  • Non-Business Elapsed (min)

  • Hold Time

  • Hold Time (min)

  • ( Open Parenthesis

    COUNT() – Counts total rows

    Count
  • Currency

  • Input Value

    100

    Unit

    Percentage

    Unit

    Hours

    Unit

    Minutes

    Ticket Escalation Notification
  • Ticket Feedback

  • Ticket Report

  • Ticket SLA Compliance

  • Ticket Summary

  • Report Template

  • Search

    Input field

    Click to search for a report from the available reports. Minimum 3 characters required.

    Filter

    Click to apply filters

    Filter reports based on fields such as Name, Category, Description, and Schedule. Supported conditions: in, not in, equal to, not equal to, contains, and not contains.

    Show Scheduled Reports

    Toggle

    Enable the display of only reports that have an active schedule configured. The disabled state shows all reports.

    Name

    Click to open the report

    Displays the report name. Clicking opens the report configuration page, where users can modify settings or preview the report. Example: Clicking the Asset Allocation Report opens its configuration.

    Category

    Label

    Mask

    Unmask

    Name

    Enabling this toggle will obfuscate the requester’s name in reports to comply with data privacy regulations.

    Use the designated toggle switch to restore the requester's name display in the report interface for authorization.

    Contact

    Enabling this toggle will obfuscate the requester’s contact information in reports to comply with data privacy regulations.

    Nested Grouping

    Enable or disable toggle

    Activates hierarchical grouping for the report. When enabled, the standard Group By option is replaced with Nested Group By, allowing multiple (up to 7 parameters) grouping levels to be configured.

    Nested Group By

    Select one or more fields

    Ticket Priority Analysis

    Priority → Urgency → Severity

    Team Ownership Review

    Team → Assignee → Status

    Resolution Analysis

    Show Settings

    Click to expand report settings

    Displays the applied report configuration panel above the report results. Users can review or modify settings such as Nested Grouping, Nested Group By, and Timescale, then click Generate Report to refresh the output.

    Export View

    Click to download the report output

    Custom Column Name

    Enter value

    Name of the calculated column displayed in the report.Example: SLA Utilization %

    Add Column

    Click

    Custom Column Name

    SLA Utilization %

    Columns

    Hold Time (min), Total Elapsed (min)

    Operators

    Custom Column Name

    Resolution Hours

    Columns

    Resolved Date, Creation Time

    Operators

    Custom Column Name

    Avg Hold Time

    Columns

    Hold Time (min)

    Function

    Data Privacy

    Mask/ Unmask Requester Info

    Nested Grouping

    How does it work?

    View Report

    Custom Column

    Why Use Custom Columns?

    Add Custom Column

    Formula Builder

    Build Formula

    (Hold Time (min) / Total Elapsed (min)) * 100

    Resolved Date – Creation Time

    AVG (Hold Time (min))

    Custom Fields

    Adhoc Report

    View only

    Use the designated toggle switch to restore the requester's contact information in the report interface for authorization.

    Used to define the hierarchy of ticket grouping. Each selected field becomes a level in the report structure. Example: Status → Urgency → Priority.Note: Duplicate field selection is not allowed.

    State → Close Type

    Exports the currently displayed report in available formats, including PDF, XLSX, CSV, and WORD.

    Adds a new custom column row.

    /, *

    -

    AVG()

    Import from CSV
  • Invite Requester(s)

  • Administrators can also activate or deactivate requesters and manage their requester details, work information, access, and asset associations.

    When an administrator marks a requester as inactive, Infraon automatically removes the requester from all associated assets.

    This applies to the following asset fields:

    • Requester

    • Owner

    • Managed By

    • Used By

    A confirmation message is displayed before disabling the requester.

    When you deallocate the requester, the asset allocation status updates from Requester to Deallocated, and the change is recorded in the Asset Activity Log.

    This functionality is supported for:

    • Manual updates

    • Grid updates

    • Bulk updates through CSV

    Go to Infraon Configuration → User Management → Requester.

    The Requesters page can be displayed in List View or Card View. Use the view toggle available next to the Add Requester(s) button.

    The page lets you search, filter, export, invite, add, and manage requesters.

    Requester | Basic Details

    Label
    Action
    Description/Example

    Search

    Enter a keyword in the search field.

    Searches for requesters based on the entered information.

    Filter

    Select the required filter criteria.

    Requester | Requester List

    Label
    Action
    Description/Example

    Username

    View the username.

    Displays the username of the requester.

    Phone

    View the phone number.

    Edit and delete icons are available for each requester when you hover over the corresponding list item or card.

    The Requester module provides multiple options for creating and managing requesters in Infraon. Administrators can create requesters individually, import users in bulk, and invite users through email.

    The available options are:

    • Add Requester

    • Import from CSV

    • Invite Requester(s)

    The Add Requester option allows administrators to create a requester by entering the required requester, work, and address information.

    Go to Infraon Configuration → User Management → Requester and click Add Requester.

    The Add Requester page contains the following sections:

    1. Requester

    2. Work

    3. Address

    Add Requester | Requester

    Label
    Action
    Description/Example

    Change

    Click to add or change the profile photo.

    Upload or update the requester's profile photo.

    Full Name*

    Click Submit to create the requester.

    To add work and address details, click Next.

    Add Requester | Work

    Label
    Action
    Description/Example

    Designation

    Enter the requester's designation.

    Technical Support Engineer

    Department

    Select the department from the dropdown list.

    Click Next to continue.

    The address can be populated based on the requester's Base Location or Work Location.

    Select the appropriate location from the dropdown list. Infraon uses addresses already available in the address book.

    Add Requester | Address

    Label
    Action
    Description/Example

    Base Location

    Select the requester's base location.

    Select the applicable location.

    Work Location

    Select the requester's work location.

    The Import from CSV option allows administrators to add multiple requesters at once.

    1

    Download the sample CSV file

    Click Import from CSV, then click Download sample CSV file here.

    2

    Enter requester details

    Enter the requester details in the downloaded CSV file.

    3

    Upload the CSV file

    Upload the completed CSV file using Browse or drag and drop.

    4

    Click Next and map the required columns.

    5

    Review the validation results.

    6

    Click Import, then click Proceed with Valid Records to continue with the valid records.

    The Import CSV option allows you to download a sample CSV file and upload your completed CSV file. It also provides details about the required CSV format and field requirements.

    Label
    Action
    Description/Example

    Download sample CSV file here

    Click to download the template.

    Downloads the sample CSV file for requester import.

    Upload

    Upload the completed CSV file.

    Field/Requirement
    Description

    File Format

    CSV

    Maximum File Size

    1 MB

    Mandatory Fields

    During CSV import, Infraon provides column-matching options to map CSV columns to the corresponding requester fields.

    Label
    Action
    Description/Example

    Show only Mandatory

    Enable or disable

    When enabled, only mandatory columns are displayed. When disabled, all columns are displayed.

    After mapping the required columns, click Next. Infraon validates the uploaded data and separates the records into Valid and Invalid data. For invalid records, click Download to download the failed data. Click Show Fields to view the specific fields that contain errors.

    The Invite Requester(s) option allows administrators to invite one or more requesters through email.

    1

    Open Add Requester

    Go to Infraon Configuration → User Management → Requester → Add Requester.

    2

    Invite requesters

    Click Invite Requester(s).

    3

    Enter email addresses

    Enter the requester's email address. Multiple email addresses can be entered using a semicolon (;) or comma (,).

    4

    Click Invite to send the invitation.

    Label
    Action
    Description/Example

    Enter Requester's Email ID

    Enter one or more email addresses.

    john.doe@company.com; jane.doe@company.com

    Invite

    Click to send the invitation.

    The Bulk Delete Requesters option allows administrators to remove multiple requesters from the system.

    When deleting requesters who are associated with assets or tickets, Infraon checks their existing associations before deletion.

    • Requesters with mapped assets can be removed according to the applicable deletion rules.

    • Requesters associated with active tickets may require the ticket or requester association to be resolved first.

    • If an owner cannot be deleted because of active tickets or associated users, Infraon displays a prompt to replace the owner before proceeding.

    This ensures that deleting requesters does not leave active tickets or asset associations without the required ownership.

    How It Works

    Automatic Asset Deallocation

    To manually allocate or deallocate a requester, navigate to the Asset Details page and update the respective fields.

    What You See on the Screen

    The requester status must be Active for the requester to log in to Infraon.

    Instructions to Add Requesters

    Add Requester

    Import from CSV

    What You See on the Screen

    CSV Requirements

    Column Matching

    Additional work-from-home address fields can also be mapped, including WFH Location Name, WFH Country, WFH City, WFH State, WFH Postal Code, WFH Landmark, WFH Flat/House No/Building/Company, WFH Area/Colony/Street/Sector/Village, and WFH Additional Information.

    Click Import to send it for validation.

    Validation

    Invite Requester(s)

    What You See on the Screen

    The invitation link expires after 36 hours by default. You can change the expiry period in settings. Send a new invitation if the previous invitation expires.

    Bulk Requester Delete

    Vendor

    A centralized hub for managing information about software vendors associated with the organization's IT environment.

    What you see on the screen

    The main screen displays a comprehensive list of vendors, providing a clear overview of the vendor landscape.

    Details | Basic information

    Label

    Action

    Search

    The Infraon platform offers two distinct vendor roles.

    This table summarizes the specific actions that Vendor Admin and Site User roles can perform for each module in the Infraon platform.

    • To manage vendor information within the Infraon portal, navigate to the Infraon Configuration section. From there, select "Infraon Portal" and then choose the "Vendor" module.

    • Select the Add Vendor option located at the top right corner of the page, and add the below details respectively:

      • Vendor Name

    • Click the + icon in the Vendor option on the top right corner.

    • The vendor creation form includes three tabs: Organization Details, Address, and Representatives.

    Refer to the table below for guidance on filling in each field.

    Organization Details | Add Vendor

    Click Next to proceed to the next tab – Organization Address.

    Add Address| Add Vendor

    to view how to add basic address details.

    Follow the table below to add Contact, GSTIN, and Bank Details.

    Other Details | Add Address

    Once the address is added, users can select Edit and Delete to change the vendor’s address.

    Click Next to proceed to the next tab – Representatives.

    The Representatives tab is the third and final step in the "Add Vendor.” This section allows you to assign individuals representing the vendor organization in the system. These users can access the portal (if login is enabled) and perform actions based on their assigned roles. Adding representatives ensures clear accountability and secure access control for vendors.

    To add a representative, click + Add User and complete the necessary details. The login can be enabled or disabled based on the requirement. Below is a structured table explaining each label in the tab:

    Once done, click on Submit to save the Vendor.

    Add Report (Old)

    Click on Add Report in the top right corner. The 'Add Report' page has three tabs. Refer to the table for more information.

    Category | Configuration | Filter

    Label
    Action
    Description / Example

    Requester

    View the Requester details in the report.

    Label
    Action
    Description / Example
    Label
    Action
    Description / Example
    Label
    Action
    Description / Example
    Label
    Actions
    Description / Example
    Label
    Action
    Decription / Example

    Category | Configuration| Filter

    The configuration boxes vary depending on the selected Report. The configuration tab has three to four sections. Refer to the table for more information.

    After selecting the appropriate boxes on the Configuration tab, click 'Next' to add details on Filter.

    Category | Configuration | Filter

    Filter options vary based on the selected Report. You will see three sections in the Filter tab.

    You can apply a filter to see only the details you selected.

    After applying Filter, click View Report to see your report on the Report dashboard.

    Status (Draft, New, and Publish)

  • Vendor Location

  • Web URL

  • Contact Person

  • Email

  • Phone Number

  • Description

  • Once the changes are made to satisfactory, click “Save” to proceed.

  • Click to search, enabling efficient navigation through the vendor list.

    Filter

    Filter can be added based on the field (Vendor Name, Status, Location, Web URL, Contact Person, Email ID, and Phone Number) and select the respective condition from the drop-down box below.

    Vendor Name

    To quickly identify the vendor.

    Status

    Indicates the vendor's current standing (active, inactive, etc.).

    Location

    View the vendor's physical location.

    Web URL

    Access the vendor's website with a single click.

    Contact Person

    Identify the designated point of contact at the vendor company.

    Email ID & Phone Number

    Facilitate easy communication with the vendor.

    Actions

    Edit

    To make changes to the vendor information.

    Delete

    Click to delete a specific vendor information from the inventory.

    Role Name

    Description

    Site User

    • Add, edit, delete, and view organization locations, holidays, password policies, and leaves.

    • Can edit and view their profile.

    • View users, organizations, dashboard, audit logs, history, knowledgebase, CMDB, software licenses, vendors, contracts, projects, and purchase orders.

    Vendor Admin

    • All privileges of Site User.

    • Add, edit, delete, and view users and vendors.

    Module

    Role

    Add

    Edit

    Delete

    View

    Copy

    Label

    Action

    Description / Example

    Organization Logo

    Upload (Drag and Drop/Click)

    Upload the organization logo in PNG, JPEG, or JPG format. The maximum size allowed is 20 MB, with an aspect ratio of 4:4.

    Label

    Action

    Description / Example

    Contact Person Name

    Enter the full name

    Name of the individual representing the vendor.

    Example: Rahul Sharma

    Email Address

    Label

    Action

    Description / Example

    Name*

    Type

    Enter the full name of the representative.

    Example: Emily Davis

    Email*

    Roles

    Instructions to Add Vendor

    Add Vendor

    Fields marked with an asterisk (*) are mandatory to fill.

    Click on “New Address” to add multiple addresses to the vendor.

    Fields marked with an asterisk (*) are mandatory to fill.

    Click here

    Displays information related to the employee who requested the asset, such as Requester Name, Requester Email, Employee ID, and other available requester details.

    Custom Fields

    Configure the required requester fields.

    Allows administrators to customize the requester information displayed in the report by adding or configuring the required fields.

    Example: Employee ID, Designation, Employee Type, or Requester Location.

    Asset

    View the asset associated with the requester.

    Displays asset-related information such as Asset Name, Hostname, Alias Name, and other configured asset fields.

    Label

    Action

    Description / Example

    Inventory Agent Installation Report

    Displays inventory agent installation and uptime details for managed assets. The report includes fields such as Agent Name, Asset Name, Serial Number, IP Address, Location, Installation Date, Last Contact Time, Agent Version, and Agent Uptime in Minutes. By default, the report displays all assets without applying any grouping. Users can optionally group the report by criteria such as Location to organize the results before previewing or saving the report. The report dynamically reflects updated asset and agent-related information after asset modifications. The report supports Send Now, Schedule Report, Clone, Edit, and Delete actions. Users can export the generated report in PDF, XLSX, and CSV formats.

    Displays inventory agent installation and uptime details for managed assets. The report includes fields such as Agent Name, Asset Name, Serial Number, IP Address, Location, Installation Date, Last Contact Time, Agent Version, and Agent Uptime in Minutes. By default, the report displays all assets without applying any grouping. Users can optionally group the report by criteria such as Location to organize the results before previewing or saving the report. The report dynamically reflects updated asset and agent-related information after asset modifications. The report supports Send Now, Schedule Report, Clone, Edit, and Delete actions. Users can export the generated report in PDF, XLSX, and CSV formats.

    Agent Uptime Report

    View / Configure

    Asset Audit Summary Report

    Users can filter this report using options like Change Type, Custom Filters, and Location conditions.

    Provides visibility into API consumption across API Users. By default, the report displays Date/Month, API User, Total Calls, Endpoint, Method, and Distinct IPs.

    Optional columns, such as Full Name and Email, can be included by selecting them. Data can be filtered using fields such as API User, Endpoint, Method, and Email to analyze API usage patterns.

    The report groups API activity by user, endpoint, and HTTP method, helping administrators monitor API consumption, identify frequently used endpoints, track unique source IP addresses, and review license utilization trends. Supports report preview, scheduling, and export in Excel, CSV, and PDF formats.

    Depreciation Report

    Click the Helpdesk Reports on the left panel and select the Depreciation Report

    Availability Reports

    Select the availability report box to send the report.

    Availability report helps technicians to analyze situations in which problems have occurred. It can be plotted against time in each interval and viewed as a data table, line chart, area chart, bar chart, etc. Example; Login hours, shift hours, availability percentage, etc.

    Event Report

    Click the Event Reports on the left panel and select the Event Report.

    The event report provides statistical information about the specific event for the selected time interval.

    Event Summary Report

    Click the Event Reports on the left panel and select the Event Summary Report.

    Label

    Action

    Description / Example

    API Metering Data Report

    Users can configure this report by selecting required columns, applying custom filters, defining a timescale, choosing a View By option (Day or Month), and specifying the number of records using the Top setting.

    Provides visibility into API consumption across API Users. By default, the report displays Date/Month, API User, Total Calls, Endpoint, Method, and Distinct IPs. Optional columns, such as Full Name and Email, can be included by selecting them. Data can be filtered using fields such as API User, Endpoint, Method, and Email to analyze API usage patterns. The report groups API activity by user, endpoint, and HTTP method, helping administrators monitor API consumption, identify frequently used endpoints, track unique source IP addresses, and review license utilization trends. Supports report preview, scheduling, and export in Excel, CSV, and PDF formats.

    SLA Report

    Authorized vs Unauthorized Trend

    View Authorized vs Unauthorized Trend

    Displays a comparative trend of authorized and unauthorized configuration changes over the selected time-period. The report provides a graphical and tabular representation of change counts over time. Data is generated based on configuration comparison results within the selected filters.

    Note: Graph representation is not included in CSV/Excel exports.

    Software License Summary Report

    Users can configure this report by selecting required columns, applying custom filters, choosing a Timescale Column(Effective From, AMC Start Date, AMC Expiry Date, End Date, Invoice Date), and defining a Timescale.

    Displays software license details based on the selected configuration. The report includes fields such as License Name and Description (available by default), as well as selectable columns such as Free (available licenses) and Allocated (assigned licenses). Users can filter data using custom conditions and time-based criteria. The report supports preview before saving and allows export in Excel, CSV, and PDF formats. It helps track license usage, availability, and lifecycle based on selected time filters.

    Software Detail Report

    Click on the reports on the left panel and select software reports.

    Label

    Description

    Statistics

    You can modify your report by adding satistical details like CPU utilization, Availability, etc.

    Columns

    You can choose assets from the column. This column is optional; you can proceed to the next tab without filling it.

    Show Top

    Label

    Description

    Duration

    Select the particular duration that you want to see on the report. By default, it is selected as the last hour.

    Asset Tag

    Select any asset tag for your report.

    Assignee

    Agent

    Asset

    Availability

    Event

    ITSM

    NCCM

    Software

    Release and Change reports include related record information during report extraction. While configuring the report, selecting the Relation column displays IDs of all linked records, such as Tickets, Changes, Problems, Releases, and Requests.

    • The Relation column lists related record IDs for each Release or Change.

    • If no relation is found, the column remains empty.

    After selecting the specific Report, click Next to add Configuration.

    Note:

    • The Location Name / Installed Location filter supports the IN and IS conditions. Selecting IS allows you to choose an empty value to retrieve assets that lack a location assignment.

    • A custom field filter for Asset Custom Field (Zone, Circle, Time, etc.) is now available in all summary reports. These fields are part of the custom attributes added in IT Assets and help refine report data directly within the tool for quicker analysis. The export option remains available for full report downloads.

    Note: The Service Catalogue field is available as a custom filter in ITSM reports. Users can select one or more service catalogue entries while creating or editing a report.

    When applied, the report data is filtered to display only records associated with the selected service catalogue entries. The filter is supported in both report configuration and preview mode.

    Example: Predict potential device failures based on past alerts.

    Statistics Pattern Report: Identifies recurring patterns and trends in statistical data over time. Example: Detect recurring spikes in network usage during specific hours. Event Pattern Report: Analyzes event logs to identify frequent or repeating event patterns. Example: Identify repeated “Device Down” events for a specific asset.

    Filters requesters based on available fields.

    Add Requester

    Click Add Requester.

    Creates a new requester by entering requester, work, and address details.

    Import from CSV

    Click Import from CSV.

    Adds multiple requesters by uploading a CSV file.

    Displays the requester's phone number.

    Type

    View the requester type.

    Indicates whether the requester is Internal or External.

    Is Active

    Enable or disable the requester.

    Indicates whether the user is active or inactive.

    Action

    Edit or delete the requester and view the license

    Provides options to edit or delete the requester. Click the View Allocated Licenses icon; it will display licenses allocated for the requester

    Enter the requester's full name.

    John Doe

    Email*

    Enter the requester's email address.

    Phone Number

    Enter the requester's mobile number.

    +919988776655

    Landline Number

    Enter the requester's landline number.

    Enter the landline number, if applicable.

    Contact Extension

    Enter the contact extension.

    Enter the extension assigned to the requester, team, or department.

    Customer Name

    Select the customer or entity.

    Select the applicable customer or entity.

    Type

    Select the requester type.

    Internal or External

    Enable Login

    Enable or disable the option.

    Allows the requester to access the self-service portal.

    Approval Access

    Enable or disable the option.

    Provides the requester with the applicable approval access.

    Is Active

    Enable or disable the option.

    Determines whether the requester account is active.

    Enable 2FA

    Enable or disable the toggle.

    Enables email-based two-factor authentication.

    User ID

    Enter the user ID.

    Enter a unique user ID for the requester.

    Password

    Enter the password.

    Used by the requester to log in when login is enabled.

    Time Zone

    Select the requester's timezone.

    Select the applicable timezone.

    Language

    Select the preferred language.

    Select the language used by the requester.

    Enable Reporting

    Enable or disable the option.

    Allows a reporting manager to be assigned to the requester.

    Reporting Manager

    Select the reporting manager.

    Select the applicable manager.

    Technical Department, IT System

    Employee Type

    Select the employee type.

    Internal or External

    Joining Date

    Select or enter the joining date.

    Select the employee's joining date.

    Notify Email ID(s)

    Enter email address(es).

    Used to send notifications to the requester.

    Notify Phone No(s)

    Enter phone number(s).

    Used to send notifications to the requester.

    Tags

    Select tags from the dropdown list.

    DevOps, Front Desk Manager

    Service Hub

    Select the applicable service hub.

    Head Office, Branch Office

    Employee ID

    Enter the employee ID.

    EMP001

    Select the applicable work location.

    Supports CSV files up to 1 MB.

    Next

    Click to continue.

    Validates the uploaded requester information.

    Full Name and Email

    Phone Number

    Must contain the country code and be enclosed in single quotes. Example: '919988776655'

    Is Active

    Must be true or false.

    Phone Number Length

    Must contain numeric data with 10–15 digits.

    Notify Email IDs

    Multiple email IDs must be separated using semicolons.

    Notify Phone Nos

    Multiple phone numbers must be separated using semicolons.

    Tags

    Multiple tags must be separated using semicolons and must contain unique existing tag names.

    Type

    Must be Internal or External. If another value is provided, the system saves it as Internal.

    Is Work From Home

    Must be True or False. The default value is False.

    Full Name*

    Map the CSV column to the requester’s full name.

    Mandatory field. Example: John Doe

    Email*

    Map the CSV column to the requester’s email address.

    Mandatory field. Example:

    Type

    Map the CSV column to the requester type.

    Internal or External

    Enable Login

    Map the CSV column to the login access setting.

    Enables or disables requester login.

    Password

    Map the CSV column to the requester password.

    Password used when login is enabled.

    Phone Number

    Map the CSV column to the requester’s phone number.

    Example: '919988776655'

    Landline

    Map the CSV column to the requester’s landline number.

    Enter the landline number.

    Subscription Plan

    Map the CSV column to the subscription plan.

    Select or specify the applicable plan.

    Subscriber ID

    Map the CSV column to the subscriber ID.

    Enter the subscriber identifier.

    Subscription Details

    Map the CSV column to subscription information.

    Enter the applicable subscription details.

    Contact Extension

    Map the CSV column to the contact extension.

    Example: 1025

    Is Active

    Map the CSV column to the requester status.

    Set to True or False.

    Enable 2FA

    Map the CSV column to the two-factor authentication setting.

    Enables or disables 2FA for the requester.

    Timezone

    Map the CSV column to the requester's timezone.

    Example: Asia/Kolkata

    Language

    Map the CSV column to the requester's preferred language.

    Select the applicable language.

    Enable Reporting

    Map the CSV column to the reporting setting.

    Enables reporting for the requester.

    Reporting Manager

    Map the CSV column to the reporting manager.

    Specify the requester's reporting manager.

    Designation

    Map the CSV column to the requester's designation.

    Example: Technical Support Engineer

    Department

    Map the CSV column to the requester's department.

    Example: IT

    Employee Type

    Map the CSV column to the employee type.

    Internal or External

    Joining Date

    Map the CSV column to the joining date.

    Example: 15-Jan-2026

    Notify Email IDs

    Map the CSV column to notification email addresses.

    Multiple email IDs can be separated by semicolons.

    Notify Phone Nos

    Map the CSV column to notification phone numbers.

    Multiple phone numbers can be separated by semicolons.

    Tags

    Map the CSV column to requester tags.

    Example: DevOps; Front Desk Manager

    Service Hub

    Map the CSV column to the service hub.

    Example: Head Office

    Employee ID

    Map the CSV column to the employee ID.

    Example: EMP001

    Is Work From Home

    Map the CSV column to the work-from-home status.

    Set to True or False.

    Base Location

    Map the CSV column to the requester's base location.

    Select or specify the applicable location.

    Work Location

    Map the CSV column to the requester's work location.

    Select or specify the applicable work location.

    Approval Access

    Map the CSV column to the approval access setting.

    Enables the applicable approval access for the requester.

    Customer ID

    Map the CSV column to the associated customer.

    Enter the customer ID associated with the requester.

    Sends an invitation email to the requester.

    Pending Invitations

    View pending invitations.

    Allows administrators and privileged users to view and resend pending invitations.

    Map columns

    Review validation results

    Import requesters

    Send the invitation

    Displays agents' uptime for assets over a selected time range, allowing users to analyze availability and operational duration. By default, the report shows overall uptime from the agent installation date to the current date. Users can apply predefined filters (e.g., Last 7 Days, Last 30 Days) or select a custom date range to view uptime for specific periods, such as weekly or monthly analysis. Supports filtering using asset tags and custom conditions, column selection, sorting, and preview before saving. Reports can be exported in CSV, XLSX, and PDF formats and scheduled for automated delivery via email or to a folder.

    Generate the Depreciation Report for Assets and select the relevant report from the provided list. Submit the report request and select the financial year start date to generate the report according to the specific needs. The generated report provides accurate and up-to-date information about asset depreciation.

    Asset Summary Report

    The report also supports Nested Grouping, allowing users to group report data using multiple Group By levels.

    Users can select up to four grouping fields, and the exported report maintains the same grouping structure as displayed in the report view.

    Provides a consolidated view of assets with configurable grouping and filtering options. Users can group assets using fields such as OS Name, Device Type, Status, Vendor, and other available asset attributes for reporting and audit purposes. The report supports a Split By option that breaks down asset counts by a selected attribute. When enabled, the report preview displays asset distribution with accurate split counts.

    The selected Split By configuration is retained during save, edit, view, and export operations.

    Asset Detailed Report

    Click on the Helpdesk Reports on the left panel and select the Asset Reports. Click on the Detailed Asset Report

    Comprehensive asset hardware, software, and activity log all in one report with detailed asset report by selected tags and duration and generate information that contains the asset name, IP address, inventory details and more.

    The event summary report gives comprehensive statistical data for all the events for the selected time interval.

    Click on the report to configure and generate SLA-based reports.

    Tracks SLA violations and calculates penalties based on predefined contract rules. The report highlights breached SLAs within the selected time interval and provides a penalty summary categorized by ticket, service, team, customer, location, service category, and requester username. Approved By displays the usernames of approvers associated with the request/ticket, while Approval Comment displays the comments added during the approval process. If approval details are unavailable, the report displays Not Approved or No Comment based on the report data. SLA Exclusion ensures that excluded tickets or durations are not considered in SLA evaluation, breach calculations, or reported metrics.

    Task Report

    Select the Task Report option from the ITSM reports category and proceed to configure columns and filters.

    The Task Report provides visibility into all tasks across the system based on the selected filters. Users can configure columns such as Task Title, Assignee, Status, Priority, Due Date, and more to generate customized reports. Filters such as status, assignee, priority, and module help narrow down the task data. The report supports preview, export (CSV, XLSX, PDF), scheduling, cloning, and editing.

    Location Report

    Click on the organization on the left panel and select the address book. Click on the 'Export' icon.

    Manage and track the location of the assets by exporting the address book details from the organization's address book. With the ability to import and export location details, quickly generate comprehensive location reports for the assets.

    SLA Compliance Report

    Configure and generate a report

    Shows incident performance against selected SLA Profiles and Metrics. Filters data based on SLA Profile, Metric, Timescale, and Group By options (Level, Team, Assignee, Catalogue, Impact Service). Includes Incident Closed Count, SLA Violations, Compliance%, and Non-Compliance%. Supports CSV export. Example: View all incidents under a selected SLA Profile (e.g., High Priority SLA) and Metric to check how many met or breached the SLA, grouped by team or level, along with compliance percentages.

    Installed vs purchased report advance

    Click on the reports on the left panel and select software reports.

    Access the 'Software Installed vs Purchase' report in the software report section. Track software names, purchase details, installation status, and compliance metrics.

    Backup Failed Devices

    View Failed Backup Details

    Displays devices for which the configuration download (backup) has failed during execution. The report provides device-level details, including IP Address, Asset Name, Vendor, OS Version, Configuration Profile, Status, and Customer/Entity (MSP-based visibility).

    Data is generated based on failed configuration download results within the selected filters and time interval.

    Backup Not Configured Devices

    View devices not configured for backup

    Displays device details where configuration download (backup) is not configured. The report helps identify assets that do not have a download job or configuration profile associated for backup.

    Supports custom filters (e.g., Vendor, IP Address, Customer/Entity), MSP-based visibility, scheduling, and export options (CSV, PDF, XLSX).

    Change Job Trend Graph Report

    View Change Job Trend Details

    Displays the trend of CLI and upload job executions on a day-by-day basis in a graphical format. The report tracks the number of CLI jobs and upload jobs executed during the selected timescale.

    Supports filtering by IP Address, Device Group, Asset Tag, and custom filters. Allows timescale selection, scheduling, and export options (CSV, PDF, XLSX). Data visibility is based on user role and MSP configuration.

    CLI Job Report

    View CLI Job Details

    Displays detailed information of executed CLI jobs within the selected time range. Includes Job Name, Creation Time, Requester, Client IP, Device IP, Protocol Type, Device Account, Approval Status, Access Duration, Access Attempts (Tried/Allowed), Change Request ID, Approver, and Session timelines.

    Supports filtering by Asset Tag, Custom Filters, Timescale, Resolution, and Top N limit. Supports export in CSV, XLSX, and PDF formats.

    CLI Jobs Approval Audit Report

    View CLI Job Approval Details

    Displays approval audit details for CLI jobs, including execution status, approver information, job execute time (first access or last access time), and related device details.

    Data is generated based on CLI job approval audit records within the selected filters and timescale.

    Configuration Discrepancies Report

    View Configuration Discrepancy Details

    Displays devices where the last downloaded configuration differs from previous, baseline, or startup/running configurations. The report helps identify configuration deviations across comparison types such as Current vs Previous, Current vs Baseline, and Startup vs Running.

    Provides device-level details, including IP Address, Asset Name, Configuration Profile, and discrepancy status. Supports custom filters, MSP-based visibility, scheduling, sorting, and export options (CSV, PDF, XLSX).

    Configuration Download Result Report

    Click on the reports on the left panel and select the NCCM reports.

    Generate a detailed summary of configuration download activities for network devices. This report includes the status of each download (success or failure), device details, and any encountered errors.

    Device Download Statistics

    Statistics

    View device download statistics

    Displays statistical data for devices where configuration download (backup) has been executed. The report provides device-level download metrics, including IP Address, Creation Time, Total Downloads, Successful Downloads, and Failed Downloads.

    Data is generated based on configuration download execution results within the selected timescale. Supports custom filters (AND/OR conditions), asset column selection, visibility filters, MSP filters, and export options (CSV, PDF, XLSX).

    Device Upload Job Statistics Report

    View Upload Job Statistics

    Displays total, successful, and failed configuration upload jobs per device within the selected time range. Includes device details such as IP Address, Hostname, Vendor, Model, and OS Type. Supports filtering by Organization, Asset Tags, Custom Filters, Timescale, and Top N limit.

    Supports export in CSV, XLSX, and PDF formats with configurable Cover Page, Header, and Footer.

    Device Vulnerability Report

    View device vulnerability details

    Displays agents' uptime for assets over a selected time range, allowing users to analyze availability and operational duration. By default, the report shows overall uptime from the agent installation date to the current date. Users can apply predefined filters (e.g., Last 7 Days, Last 30 Days) or select a custom date range to view uptime for specific periods, such as weekly or monthly analysis. Supports filtering using asset tags and custom conditions, column selection, sorting, and preview before saving.

    Reports can be exported in CSV, XLSX, and PDF formats and scheduled for automated delivery via email or to a folder.

    Device Vulnerability Statistics Report

    View vulnerability statistics by device

    Displays summarized vulnerability statistics for each device (IP address/node). Provides consolidated metrics including Total Vulnerabilities, Unresolved, Resolved, EOL, and EOS, along with device attributes such as IP Address, Hostname, Vendor, Model, OS Type, and Created Time.

    Supports tag-based filtering (asset/resource/ticket), custom filters, column selection, timescale selection, scheduling, sorting, MSP visibility, and export options (CSV, PDF, XLSX).

    Jobs Account Audit Report

    View Jobs Account Audit Details

    Displays audit records for download job account activities within the selected time interval. The report provides job-level and device-level details, including Device IP Address, Device Account, Connection Protocol, Agent, Connect Time, Connect Status, Job Type, Job Name, and execution information.

    Data is generated based on download job execution logs and audit records within the selected timescale.

    Supports Timescale selection, custom filters, column selection, scheduling, and export options (CSV, PDF, XLSX).

    Note: When MSP is enabled, data is filtered based on Customer/Entity mapping and asset visibility. When MSP is disabled, data follows organization-level visibility rules.

    Network Compliance Report

    View Compliance Details

    Provides a consolidated compliance overview for all active (non-deleted) managed devices. Displays IP Address and Hostname along with: Backup Status, Startup vs Running comparison, Current vs Baseline comparison, Policy Association, Policy Compliance Status, and Vulnerability Status.

    Supports filtering by Vendor, OS Type, Device Group, Asset Tags, Custom Filters, Timescale, Resolution, and Top N limit.

    Supports export in CSV, XLSX, and PDF formats with configurable Cover Page, Header, and Footer.

    Network Summary Report

    View Network Summary Details

    Displays device summary information based on Vendor, Configuration Profile, Device Credentials, Series, OS, and OS Version. The report provides overall network distribution in table and chart formats for the selected configuration.

    Supports filtering based on asset tags and custom filters, MSP-based visibility, scheduling, sorting, and export options (CSV, PDF, XLSX).

    Operational Data Report

    View Operational Data Report

    Summarizes operational command execution data for devices. Provides details such as Asset ID, Asset Name, IP Address, Hostname, Vendor, Serial Number, Command, and Result.

    Includes sidebar view for detailed command results. Supports custom filters (Device Group, Customer/Entity, Command), Top limit, scheduling, and export options (CSV, PDF, XLSX).

    Patch Compliance Report

    View Patch Compliance Report

    Summarizes device patch and OS compliance details, including Asset ID, IP Address, Hostname, Vendor, Model, Serial Number, Current OS Version, Latest OS Version, End of Support, End of Life, Vulnerabilities, and Compliance Status.

    Includes vulnerability sidebar with detailed advisory information (Advisory ID, CVSS Score, Resolution Status). Supports timescale filtering, custom filters, scheduling, and export options (CSV, PDF, XLSX).

    Policy Associated Devices Report

    View devices associated with policies

    Displays devices associated with selected policies along with assigned rule information. Shows IP address, hostname, vendor, model, assigned policies, service status, asset state, and operational status.

    Supports asset tags, custom filters, column selection, sorting, top configuration, MSP visibility, scheduling, and export options (CSV, PDF, XLSX).

    The IP Address and Hostname fields are clickable and navigate to the respective IT Asset details page.

    Policy Compliance Device Report

    View policy compliance per device

    Displays policy and rule compliance details per IP address/device. Shows policy name, rule group, rule status, and compliance metrics for each device.

    Supports asset tags, custom filters, sorting, top limit configuration, MSP visibility, scheduling, and export options (CSV, PDF, XLSX).

    PDF export supports configurable cover page, header, footer, logo size/alignment, custom text, generated details, and page numbering.

    Policy Comply Devices Report

    View Policy Comply Devices Report

    Displays devices that comply with assigned configuration policies. Provides detailed device information, including Asset details, Category, Location, State, and associated tags.

    Supports asset tags and custom filters, column configuration, Top limit, resolution, business-hour filtering, scheduling, and export options (CSV, PDF, XLSX).

    Policy Detailed Report

    View detailed policy execution results

    Provides comprehensive policy execution results categorized by policy, rule group, and rule, along with associated asset details. Includes execution time, rule type, configuration file, review task name, and configuration type.

    Supports asset tags, custom filters, column selection, chart/table view options, sorting, top configuration, MSP visibility, scheduling, and export options (CSV, PDF, XLSX).

    PDF export supports cover page, header/footer customization, logo configuration, generated details, duration, and page numbering.

    Policy Not Associated Devices Report

    View Policy Not Associated Devices Report

    Displays devices that are not associated with any configuration policy. Provides asset-level information, including Asset ID, Asset Name, Alias, Category, Location, Status, and related attributes.

    Supports asset tag filtering, custom filters, column selection, Top limit, scheduling, and export options (CSV, PDF, XLSX).

    Policy Summary Report

    View policy execution summary

    Displays a summarized view of policy execution status across devices. The report includes a pie chart visualization (Configured vs Non-Compliant/Compliant status) and a tabular summary of total devices, configured devices, and non-configured devices.

    Supports asset/resource/ticket tags, custom filters, column selection, sorting, resolution, business hour filtering, MSP visibility, scheduling (email/folder/immediate), and export options (CSV, PDF, XLSX).

    PDF export supports cover page, header, footer, logo configuration, custom text, report duration, generated by/on, and page number alignment.

    Policy Violation Devices Report

    View Policy Violation Devices Report

    Displays devices that have violated assigned configuration policies. Provides device-level details, including Asset ID, Asset Name, IP Address, Hostname, Vendor, Model, Status, Service Status, and related policy information.

    Supports asset tag filtering, custom filters, column selection, Top limit, sorting, scheduling, and export options (CSV, PDF, XLSX).

    Unauthorized Change Report

    View Unauthorized Configuration Changes

    Displays configuration differences that indicate unauthorized changes between the running and startup configurations. The report provides device details and configuration comparison results.

    Data is generated based on configuration download and comparison results within the selected timescale. Only valid and accessible assets are included.

    Unauthorized Changes Trend Graph Report

    View Unauthorized Changes Trend

    Displays a graphical representation of unauthorized configuration changes over the selected time range. Shows trend-based data (date/time vs change count) to help identify frequency and patterns of unauthorized changes across devices.

    Supports filtering by Vendor, Device Group, Asset Tags, Custom Filters, and Timescale.

    Supports export in CSV, XLSX, and PDF formats, including graphical representation in PDF export when enabled.

    Vulnerability Detailed Report

    View detailed vulnerability information

    Displays complete vulnerability-level details mapped to each device IP. Includes fields such as IP Address, Vendor, OS Type, Version, Series, Model, Vulnerability ID, Vulnerability Title, CVSS Score, Severity, Published Date, Identified Time, Resolved Status, Resolved By, Resolved Time, URL, Resolve Comments, Summary, End of Life, and End of Support.

    Supports custom filters, tag filtering, timescale selection (Published/Identified/Resolved), column configuration, scheduling, sorting, MSP visibility, and export options (CSV, PDF, XLSX).

    Vulnerability Report

    View vulnerability overview

    Displays consolidated vulnerability details for managed devices under NCCM. Provides vulnerability-level information, including Vulnerability ID (CVE), Severity, CVSS Score, Published Date, Identified Time, Resolved Status, Resolved By, Resolved Time, Resolve Comments, and related device information.

    Supports default filters (Vulnerability ID, Severity, Vulnerability Status), resolution-based filtering, custom filters, scheduling, audit tracking (add/edit/delete/clone), MSP visibility, and export options (CSV, PDF, XLSX).

    Vulnerability Summary Report

    View Vulnerability Summary Details

    Displays vulnerable device details categorized by severity levels, including Critical, High, Medium, and Low. The report provides summary and detailed vulnerability statistics for the selected time interval.

    Includes device-level details such as IP Address, Asset Name, Severity, CVSS Score, and Vulnerability Status.

    Supports custom filters, time scale selection, business-hour selection, Top limit, MSP-based visibility, scheduling, and export options (CSV, PDF, XLSX).

    Recent Changes Report

    View Recent Changes Details

    Displays devices for which configuration download changes are detected during the selected time interval. The report provides device-level details, including IP Address, Asset Name, Vendor, OS Version, Configuration Profile, and comparison results such as Previous vs. Current, Baseline vs. Current, and Startup vs. Running.

    Data is generated based on configuration download results within the selected filters and timescale. Supports custom filters, MSP-based visibility, scheduling, sorting, Top limit, and export options (CSV, PDF, XLSX).

    Configuration Download Result Report

    Click on the reports on the left panel and select the NCCM reports.

    Generate a detailed summary of configuration download activities for network devices. This report includes the status of each download (success or failure), device details, and any encountered errors.

    Upload Job Audit

    View Upload Job Audit Details

    Displays upload job execution results for the selected time interval. The report provides device-level details, including IP Address, Job Name, Task Status, Execution Time, Result Status, and Customer/Entity (MSP-based visibility).

    Data is generated based on upload job execution logs within the selected filters and timescale.

    Upload Job Approval Audit

    View Upload Job Approval Details

    Displays approval workflow details for upload jobs, including approval status, approver name, action time, execution time, and job result. If Next Action Time is unavailable, the last action time is used instead.

    Data is generated based on the upload job approval audit logs within the selected filters and timescale.

    Upload Job Summary Report

    View Upload Job Summary Details

    Displays the upload job summary with task-level and IP-level execution status. The report includes the total, successful, and failed tasks, along with related audit information.

    Data is generated based on upload job execution results within the selected filters and timescale. Deleted assets are excluded from the report view.

    Supports custom filters, scheduling, and export options (CSV, PDF, XLSX).

    Configuration Change Report

    View Configuration Change Report

    Displays detailed configuration change history for devices, including Running and Startup configuration changes. Includes Total Changes summary, Authorized vs Unauthorized changes, IP-based change tracking, configuration type, file version, and download time.

    Supports timescale filtering, custom filters (IP, Make, OS Name, Configuration Type, Customer/Entity), scheduling, and export options (CSV, PDF, XLSX).

    Device CLI Job Statistics Report

    View Device CLI Job Statistics Report

    Provides a statistical summary of CLI job execution status counts, including Total CLI Jobs, Waiting for Approval, Approved, Rejected, Expired, In Progress, and Session Ended.

    Supports time scale selection, custom time range in the view, asset tag filtering, column selection, Top limit, scheduling, and export options (CSV, PDF, XLSX).

    Policy Audit Report

    View Policy Audit Details

    Displays policy-level audit logs generated for configuration and compliance-related activities. The report includes fields such as Timestamp, Client IP, User Name, Audit Category, and Message. Supports add, edit, clone, delete, preview, and export (CSV, XLSX, PDF).

    Supports custom filters, sorting, Top limit, scheduling (Email / Folder / Immediate), and user-based visibility. PDF export supports cover page, header, footer, logo alignment, custom text, page number, report name, duration, Generated By, and Generated On options.

    Policy History Audit Report

    View Policy History Details

    Displays historical policy compliance records for devices, including policy name, rule group, rule, rule type, configuration type, compliance status, and timestamp.

    Supports filtering by Asset Tags and custom filters.

    Supports add, edit, clone, delete, preview, export (CSV, XLSX, PDF), scheduling (Email / Folder / Immediate), sorting, and Top limit. PDF export supports cover page, header, footer, logo configuration, custom text, page number, report metadata (Report Name, Duration, Generated By, Generated On).

    Access detailed reports for respective software in Software Detail Reports. Identify software status as 'Discovered' if found through the agent, or 'Managed' if manually added.

    Software by publisher reports

    Click on the reports on the left panel and select software reports.

    Enable all columns in Software by publishing reports. Gain detailed insights into respective assets, including application name, vendor, help link, and more. Filter by asset tag and custom criteria for comprehensive software tracking.

    You can select the top 5 or 10 to see only the full 5 or 10 reports.

    Resolution

    You can select resolution duration as min, hour, day, or month.

    Note: The resolution option is only available in the Availability Report.

    Select the name of the assignee to whom you want to send the report.

    Note: This option is only available in the Incident Report and Incident Summary Report.

    User

    Vendor Admin

    ✔️

    ✔️

    ✔️

    ✔️

    ❌

    Site User

    ❌

    ❌

    ❌

    ✔️

    ❌

    Organization

    Vendor Admin

    ❌

    ❌

    ❌

    ✔️

    ❌

    Site User

    ❌

    ❌

    ❌

    ✔️

    ❌

    Organization Location

    Vendor Admin

    ✔️

    ✔️

    ✔️

    ✔️

    ❌

    Site User

    ✔️

    ✔️

    ✔️

    ✔️

    ❌

    Dashboard

    Vendor Admin

    ❌

    ❌

    ❌

    ✔️

    ❌

    Site User

    ❌

    ❌

    ❌

    ✔️

    ❌

    My Profile

    Vendor Admin

    ❌

    ✔️

    ❌

    ✔️

    ❌

    Site User

    ❌

    ✔️

    ❌

    ✔️

    ❌

    Audit

    Vendor Admin

    ❌

    ❌

    ❌

    ✔️

    ❌

    Site User

    ❌

    ❌

    ❌

    ✔️

    ❌

    History

    Vendor Admin

    ❌

    ❌

    ❌

    ✔️

    ❌

    Site User

    ❌

    ❌

    ❌

    ✔️

    ❌

    Holiday

    Vendor Admin

    ✔️

    ✔️

    ✔️

    ✔️

    ❌

    Site User

    ✔️

    ✔️

    ✔️

    ✔️

    ❌

    Password Policy

    Vendor Admin

    ✔️

    ✔️

    ✔️

    ✔️

    ❌

    Site User

    ✔️

    ✔️

    ✔️

    ✔️

    ❌

    Leaves

    Vendor Admin

    ✔️

    ✔️

    ✔️

    ✔️

    ❌

    Site User

    ✔️

    ✔️

    ✔️

    ✔️

    ❌

    Knowledge Base

    Vendor Admin

    ❌

    ❌

    ❌

    ✔️

    ❌

    Site User

    ❌

    ❌

    ❌

    ✔️

    ❌

    CMDB

    Vendor Admin

    ❌

    ❌

    ❌

    ✔️

    ❌

    Site User

    ❌

    ❌

    ❌

    ✔️

    ❌

    Software License

    Vendor Admin

    ❌

    ❌

    ❌

    ✔️

    ❌

    Site User

    ❌

    ❌

    ❌

    ✔️

    ❌

    Vendor

    Vendor Admin

    ✔️

    ✔️

    ✔️

    ✔️

    ❌

    Site User

    ❌

    ❌

    ❌

    ✔️

    ❌

    Contract

    Vendor Admin

    ❌

    ❌

    ❌

    ✔️

    ❌

    Site User

    ❌

    ❌

    ❌

    ✔️

    ❌

    Project

    Vendor Admin

    ❌

    ❌

    ❌

    ✔️

    ❌

    Site User

    ❌

    ❌

    ❌

    ✔️

    ❌

    Purchase Order

    Vendor Admin

    ❌

    ❌

    ❌

    ✔️

    ❌

    Site User

    ❌

    ❌

    ❌

    ✔️

    ❌

    Vendor Name*

    Text Input

    Enter the official name of the vendor

    Example: ABC Technologies.

    Contact Person*

    Text Input

    Provide the full name of the primary contact person for this vendor

    Example: John Doe.

    Email*

    Text Input

    Provide a valid email address for vendor communication.

    Example: vendor@example.com.

    Phone Number

    Country Code Dropdown + Input

    Select the country code and enter the vendor’s contact number.

    Example: +91 9876543210.

    Risk

    Dropdown

    Select the vendor risk level: Low, Medium, High, or Critical. This helps categorize vendors based on compliance or operational risk.

    Status

    Dropdown

    Indicates vendor onboarding stage.

    Options: Draft (Creation), New (Open), Publish (Active).

    Draft is the default for newly added vendors.

    Country*

    Dropdown

    Select the vendor’s country of operation.

    Example: India.

    Enable Login

    Toggle

    Enables login access for the vendor representative. Only allow this if the vendor interacts directly within the system.

    Password

    Text Input

    Add an eight-letter password for login.

    User Approval

    Select from the drop-down.

    Options Include: Vendor Admin/ Site User.

    Web URL

    Text Input

    Add the vendor’s official website URL.

    Example: https://www.vendorexample.com.

    Vendor ID Number

    Text Input

    Provide a unique internal/external identifier for the vendor, if applicable.

    Example: VEN1024.

    Date of Incorporation

    Date Picker

    Select the official incorporation date of the vendor organization from the calendar dropdown.

    ID Type

    Dropdown

    Choose a supported ID type: Aadhar, Passport, or PAN.

    This is used to validate the vendor's proof of identity.

    ID Number

    Text Input

    Input the actual number based on the selected ID type.

    Upload ID

    Upload (Drag and Drop/Click)

    You can upload a scanned copy or a photo of the proof of the selected ID. The file formats supported are PNG, JPEG, and JPG.

    Add

    Click Button

    Clicking Add confirms the ID details and uploads them. This action is mandatory to save proof data before proceeding to the next step.

    MSMED Details

    Toggle

    Enable if the vendor falls under the MSMED (Micro, Small & Medium Enterprises Development) Act.

    MSMED Status

    Dropdown (Visible only if enabled)

    Select status: Low, Medium, High, or Critical, based on the MSMED evaluation of the vendor.

    MSMED Category

    Dropdown (Visible only if enabled)

    Select whether the vendor is recognized under MSMED: Yes or No.

    URN

    Text Input

    Enter the MSMED-provided Unique Registration Number (URN) if applicable. Example: MSMED12345.

    Enter email

    Email ID of the vendor's contact person. Example: vendor@example.com

    Phone Number

    Select country code & enter

    Provide the vendor contact number, including the country code.

    Example: +91 98765XXX10

    ID Number (GSTN)

    Enter alphanumeric ID

    GST identification number for the vendor. This is required for taxation purposes.

    Example: 27AAGPM1234C1Z5

    Upload ID (GSTN)

    Upload document

    Upload the supporting document for the entered GSTN.

    Accepted formats: PNG, JPEG, JPG

    IFSC Code

    Enter IFSC code

    Unique code to identify the vendor’s bank branch for domestic transfers.

    Example: SBIN0000456

    Bank Name

    Enter bank name

    Name of the bank where the vendor holds their account.

    Example: State Bank of India

    Currency

    Select from the dropdown

    Currency in which the vendor prefers payment. Default value shown: INR.

    Beneficiary Name

    Enter name

    Name of the vendor account holder (must match bank records).

    Example: EverestIMS Technologies Pvt Ltd

    Account Number

    Enter bank account number.

    The vendor’s bank account number is used to receive payments.

    Example: 123456789012

    Re-enter Account Number

    Re-enter bank account number.

    The confirmation field is used to verify the vendor’s account number to avoid payment errors.

    Type

    Provide a valid email address. This will be used for login if enabled.

    Example: emily@example.com

    Phone Number

    Select Country Code + Type

    Enter the representative’s mobile number.

    Example: +91 9876543210

    User Type*

    Select from the dropdown.

    Define the user’s role within the organization. Roles may vary depending on access level.

    Enable Login

    Toggle ON/OFF

    Enable this if the user needs access to the system. Enabling this allows you to set credentials.

    Password*

    Type

    Set a secure password for the user if login is enabled.

    Site

    Select from the dropdown

    Assign the user to a specific site (if applicable).

    Example: Bangalore HQ

    john.doe@company.com
    john.doe@company.com
    View Release Notes

    Change

    ITIL defines Change as "the addition, modification, or removal of any authorized, planned, or supported service or service component that could affect IT services." In other words, a Change is adding, removing, or modifying anything that could directly or indirectly affect the organization's services and operations. The changes could include documentation, processes, applications, or IT infrastructure changes.

    Change Management is a set of processes defined to manage the lifecycle of a change request from start to closure. It aims to minimize risks and disruptions to IT services and business operations while the changes are being implemented.

    How does it work?

    Domain experts, management, architects, or solution architects are involved in planning and implementing a change request.

    Types of Change

    Type

    Description

    Emergency changes are used in urgent situations where immediate change implementation is necessary to fix major issues or avoid significant business impact.

    • Created when a critical issue (like a server outage or security flaw) needs resolution.

    • Follows an accelerated approval path or may skip it altogether depending on settings.

    • A CAB review may still be scheduled post-implementation for audit compliance.

    • Documentation and justification are mandatory to ensure traceability.

    Use Case Example:

    The production server crashes at midnight. The support team performs a hotfix immediately. Right after, an emergency change is logged to ensure that this change is recorded and reviewed.

    Retrospective changes are created to record already implemented changes, often outside of standard workflows. These are essential for capturing unexpected or reactive actions taken in real-time.

    • Useful for manual interventions or critical on-the-spot fixes.

    • Allows post-facto documentation including reason, impact, and CI information.

    • Ensures visibility and inclusion in audit logs or reports.

    • Can be routed for post-change review if needed.

    Use Case Example:

    A network engineer applied a configuration fix during a late-night alert. Since no prior change request was raised, they document it afterward using this change option for internal tracking and compliance.

    The "Change" page lists all change requests in two views: Panel View and Grid View. It lists all changes with details like a summary card, change description, status, subject, team, requester name, and actions, sorted by time.

    Change Management involves people from different dimensions of a business. They work together to analyze, plan, and implement the change request.

    There are two ways to view change details in the right-side panel. They are:

    Panel View - You see change details as a Summary Card in the Panel view. The summary card gives a brief summary of the change. This summary contains all the important information needed to work on the change. Details include:

    • Change ID: Auto-generated when a change is created.

    • Requester: Name of the requester

    • Change Manager: Name of the manager overlooking the change request.

    • Status: Displays the current status of the change. Users can change the status from here as well.

    The panel view for tickets has been revamped. The improved interface offers enhanced data visibility, with aging metrics conveniently displayed. This helps in faster navigation and reduced system load for a seamless user experience.

    Clone Change

    The Clone Change option allows technicians to quickly create a new Change Request (CR) by copying key details from an existing change. This reduces manual data entry, ensures consistency, and speeds up the creation of repeat or similar changes.

    The following fields are automatically copied from the selected change:

    • Subject

    • Change Type

    • Change Manager

    • Change Followers

    Fields to Update During Cloning:

    Grid View- In the Grid view, you see change details in tabular form. Clicking on the Change ID shows the change details.

    • Change ID: This is auto-generated when a change is created. Click on the Change ID to view the communication history, reply to and forward emails, add notes, analyze, view, and add work logs.

    • Subject: Subject of the change (derived from the change subject line).

    • Reason for Change: The reason for detailing why the change was requested.

    • Change Type: Type of change: Standard, Major, Minor, and Emergency.

    • When an asset is added to a change, the system checks if the same asset is already linked to other active changes.

    • If a conflict is detected, a warning message displays the conflicting Change IDs.

    • Conflict detection is informational only and does not block the user from proceeding.

    • In the Change Calendar, overlapping scheduled changes involving the same asset are highlighted to indicate potential conflicts.

    Change relationships follow the same structure as defined in . For a detailed explanation of how linked records work, refer to the Problem Management page.

    When a Change Task is created from the module, NCCM sends the Job Execution Details, Job Status, and Job ID to the Change Management module through an API call. The Job ID is stored against the Change Task to maintain traceability between the change and the associated NCCM job.

    If the Change Type is set to NCCM and the user has the required NCCM job permissions, a Job button is displayed next to the Add Task option.

    Clicking this button opens the corresponding page in a new browser tab. The related NCCM job grid is automatically filtered using the Change Summary, allowing users to quickly track the execution status of the job linked to the Change Task.

    Delegation enables users to assign their approval responsibilities to another user for a specified period. Ensures that ongoing approvals are not delayed when the primary approver is unavailable due to planned leave, travel, or other reasons.

    to learn more.

    Implementing a change requires intensive planning, risk analysis, defining tasks, and approvals. To help users achieve this, the "Change" module has the following tabs:

    • Planning - A comprehensive plan is essential for successfully implementing a change. In the planning tab, a user can enter the following details:

      • Rollout Plan - A rollout plan is a detailed step-by-step description of how the change will be implemented in the production environment. The rollout plan is created in such a way that there is minimal impact on the organization. A rollout plan describes whether the change will be implemented in a phased manner or as a whole.

      • Rollback Plan - A rollback plan is a verified step-by-step fallback or back-out plan in case the change implementation doesn't go as expected. It is essential to have a rollback plan when implementing a major change.

    • Attachments - When uploading attachments to a change ticket, Users can classify and organize files for clarity and compliance.

    • Risks - It helps identify, evaluate, and reduce potential risks associated with a change before it is implemented. It offers visibility into possible business, technical, financial, or operational impacts and ensures that suitable mitigation plans are established.

    Risk Records

    Risk Records are used to document or create a knowledge base of the risks associated with a change. They capture critical information such as the risk name, type, description, and mitigation plan.

    Add Record

    Click on Add Record to add the details below:

    Risk Assessment

    It provides a structured way to evaluate the potential risks associated with a change. It involves defining questions with multiple options, assigning weights, and mapping the responses to criticality levels.

    The outcome of the assessment is represented through a riskometer, which indicates the overall risk level associated with the change.

    • Authorized Role: Only Change Managers can perform risk assessments.

    • Riskometer: Displays the criticality level based on assessment responses.

    • Workflow Dependency: Workflows can be configured so that changes move to CAB Approval only after risk assessments are completed.

    • Risk Level:

    Workflow Integration

    • Risk Assessment Mandatory Toggle – Available in every workflow state; disabled by default. If enabled, the assessment must be completed before moving to the next state.

    • CAB Approval Dependency – Transition to CAB Approval can be restricted until the Change Manager completes the risk assessment.

    • Priority Adjustment – Assessment results can automatically update the change request’s priority based on evaluated risk.

    • Workflow Toggle: By default, the Risk Assessment Mandatory toggle is disabled. If enabled, completing the risk assessment becomes mandatory during state transitions.

    Add Assessment

    Risk Assessments cannot be added directly from the Risk tab. Instead, they are created using , which define the assessment questions, weights, and criticality values.

    Skip Assessment: This toggle can only be updated by the Change Manager. When enabled, the risk assessment step can be bypassed.

    Sample Questions | Basic Details

    Riskometer Functionality

    The Riskometer dynamically evaluates the overall risk involved in a change request based on the answers provided.

    Each question is assigned a weight, and each selected option contributes a predefined risk value. The system then calculates the weighted percentage and displays the cumulative risk score on the Riskometer.

    This visual indicator updates automatically and represents the level of risk associated with the change.

    Risk Level Calculation

    The Riskometer determines the final risk level using the total risk weight. The calculation follows these rules:

    • Critical (Red): Risk score above 80

    • High (Orange): Risk score between 61–80

    • Medium (Green): Risk score between 41–60

    • Low (Blue): Risk score between 21–40

    The selected answers are:

    • Q1: Between 20–50 assets → High → Value = 2 (80%)

    • Q2: 1–4 hours downtime → High → Value = 2 (80%)

    • Q3: Core services impacted → Critical → Value = 1 (100%)

    • Q4: Rollback possible but time-consuming → High → Value = 2 (80%)

    Total Weight = 17

    Step 2: Weight % Calculation

    • Q1 → (4 ÷ 17) × 100 = 23.53%

    • Q2 → (5 ÷ 17) × 100 = 29.41%

    • Q3 → (3 ÷ 17) × 100 = 17.65%

    • Q4 → (2 ÷ 17) × 100 = 11.76%

    Step 3: Risk Contribution of Each Question

    Formula:

    Risk Contribution = Risk Value Percentage × Weight Percentage of Question​/ 100

    • Q1: (80 × 23.53) ÷ 100 = 18.82

    • Q2: (80 × 29.41) ÷ 100 = 23.53

    • Q3: (100 × 17.65) ÷ 100 = 17.65

    • Q4: (80 × 11.76) ÷ 100 = 9.41

    Step 4: Final Risk Score

    18.82+23.53+17.65+9.41+10.59=80

    Total Risk Score = 80

    Step 5: Riskometer Result

    • Score = 80

    • According to thresholds: High Risk (Orange)

    *These quick action tools are available only for Major and Minor Changes.

    The Change page also has the following actions.

    *Select at least one change request to enable these options

    This pop-up allows change managers or authorized users to close change requests with the appropriate closure type, category, notes, and timestamped records.

    Priority: Displays the priority of the change. Technicians can change the priority of the change.

  • Service: Service category in which change is requested.

  • Actions: Quick action icons to work on the change.

  • Location
  • Rollout Plan

  • Rollback Plan

  • Status: Displays the current status of the change. Users can change the status from here as well.

  • Impact Service: Service Category which the change could impact.

  • Priority: The priority of the change.

  • Risk: Risk level of the change.

  • Requester: Displays the name of the requester (initial)

  • Change Manager: Name of the manager overlooking the change request.

  • Change Implementer: Name of the user responsible for change implementation.

  • Actions: Quick action icons to work on the change.

  • Impact - A user can enter the anticipated impact of the change on various dimensions of the organization. It can be categorized into the following:

    • Business

    • Location

    • Department

    • Group

    • User

  • Planned Start Date - The intended date to begin implementing the change.

  • Planned End Date - The intended date to end implementing the change.

  • Tasks - This allows users to define and manage individual tasks involved in executing a change. Each task can be customized with fields such as title, type, priority, due date, and assignee.

  • A short explanation of the task.

    Example: Perform a full DB backup before deployment.

    Type*

    Select from the drop-down

    Choose the nature of the task:

    • Default – Generic task with no specific category.

    • Pilot – Task for trial or limited rollout.

    • Staging Development – Tasks in staging/testing environments.

    Status

    Select from the drop-down

    Choose the current task status:

    • To-Do (Open)

    • Ongoing (In Progress)

    • Blocked (On Hold)

    • Done (Close)

    Priority

    Select from the drop-down

    Indicates task urgency:

    • Low

    • Medium

    • High

    Due Date

    Select date

    Target completion date for the task.

    Actual Start Date

    Select date

    Date when the task was actually initiated.

    Actual End Date

    Select date

    Date when the task was completed.

    Team

    Select from the drop-down

    Choose the team responsible for executing the task.

    Assignee

    Select from the drop-down

    Assign the task to a specific team member.

    Submit

    Click

    Saves the task to the change ticket.

    Cancel

    Click

    Discards the task and closes the dialog.

    Choose a category to classify the attachment:

    • Default Category

    • Change Screenshot

    • Team Document

    • Team Docs

    Description

    Enter text

    Provide a brief note or context about the uploaded attachment.

    Upload

    Click to confirm

    Uploads the selected file(s) to the Change record.

    Cancel

    Click to abort

    Closes the pop-up without saving the changes.

    Defines the category of the risk.

    • Business – Risks affecting operations or service delivery

    • Technical – Risks related to systems, infrastructure, or technology

    • Financial – Risks impacting costs, budget, or revenue

    Mitigation Plan

    Add mitigation details

    Outlines the steps or strategy to reduce, transfer, or eliminate the identified risk. Example: Schedule backup before change and prepare rollback plan

    Description

    Provide description

    Offers detailed context about the risk, including possible causes, expected impact, and scenarios in which the risk might occur.

    Example: Risk of service outage if the server upgrade fails during peak hours

    Change priority is automatically updated based on the assessment result.

    Between 20 and 50 assets

    High

    Less than 20 assets

    Low

    What is the expected downtime duration for the change?

    5

    More than 4 hours

    Critical

    1–4 hours

    High

    Less than 1 hour / Zero downtime

    Low

    What level of business services will be impacted?

    3

    Core services (e.g., customer-facing apps, payment systems)

    Critical

    Internal services (e.g., reporting, HR, internal tools)

    Medium

    Non-critical services (e.g., test/dev environments)

    Low

    How complex is the rollback or recovery plan for this change?

    2

    No rollback possible

    Critical

    Rollback possible but time-consuming

    High

    Simple and tested rollback plan

    Low

    What level of dependency exists on external vendors or third-party systems?

    3

    Multiple critical vendor/third-party dependencies

    Critical

    Limited vendor dependency with partial risk

    Medium

    No vendor dependency

    Low

    Very Low (Blue): Risk score 20 or below

  • Q5: Limited vendor dependency” → Medium → Value = 3 (60%)

  • Q5 → (3 ÷ 17) × 100 = 17.65%

    Q5: (60 × 17.65) ÷ 100 = 10.59

    Attachment

    Shows all the attachments of the current change request.

    Change Source

    Shows the source of the change, like email, web, phone, etc.

    Task

    Shows the tasks involved in the change.

    *Risk

    Shows the risks involved in the change.

    *Add Ticket

    If any issues occur while implementing the change, a ticket can be raised.

    Change aging for helpdesk/ ITSM close and resolve conditions

    Grid View includes Aging Metric. Track Change resolution time accurately. Click 'Resolve' or 'Close' to stop the aging clock. Get detailed aging reports based on resolved status.

    Workspace task App

    Enjoy a seamless and streamlined experience with the powerful capabilities of the Task Common Module for enhanced task management within the application.

    *Tag

    Select a change request to view the tag option. Tagging is a way to group change requests.

    *Assignment

    Select one or more change requests to assign to a team.

    *Delete

    Select one or more change requests to delete them.

    Pause

    To pause the auto-reload.

    Configure

    To configure the summary card and column selection.

    Add final remarks on what was done, implementation outcome, or lessons learned. Example: “ES3 server restored with latest patch deployment.”

    Closed by

    Select from the drop-down

    Choose the user who is closing the change. Example: Deepak Kumar

    Close Type

    Select from the drop-down

    Defines the method and reason for closure:

    • Auto Closure: The system was closed due to no further updates after a set period.

    • Not Solved: Change was implemented, but the issue was not resolved.

    • Solved: The issue was resolved successfully via this change.

    Actual Closure Date

    Auto-filled or editable

    Actual date and time when the change was completed or formally closed. Example: Aug 01, 2025, 12:53 PM

    Agreed Closure Date

    Select date

    The closure date agreed during CAB or planning discussions. Example: July 31, 2025

    Closure Category

    Select from the drop-down

    Captures the outcome of the change:

    • Successful: Change achieved the intended goal without issues.

    • Successful with Issues: Change succeeded with minor/managed issues.

    • Rollback: Change was reverted due to failure or risk.

    Complete (Button)

    Click to confirm closure

    Finalizes the closure and updates records. Post-closure changes require admin override.

    Example

    Standard Change

    Standard Changes are the ones that frequently occur in an organization. These changes are low-risk and have a pre-defined set of documented and approved processes to be followed. This pre-defined and approved process is called a template.

    Reset the Password of an email account.

    Minor Change

    A minor change is a small, low-impact, and low-risk change that only occasionally occurs in an organization. It needs approval from the Change Advisory Board(CAB). It is essential to document all the important information for future reference. A minor change could be converted to a standard change in the future.

    Changes to the company website.

    Major Change

    A major change is a high-risk and high-impact change that could impact an organization's services if it is not planned properly. It requires an in-depth proposal on risk analysis, financial implications, and cost-benefit analysis. It also requires approval from the Change Advisory Board(CAB) and management.

    Changes to Network Infrastructure

    Emergency Change

    Emergency changes are unexpected disruptions that must be assessed and implemented as soon as possible to restore an organization's normal functioning.

    Dealing with a server outage

    Retrospective Change

    Designed to record changes that were implemented urgently without prior documentation or approval. These ensure compliance by logging the change post-implementation for audit and visibility.

    Fixing a critical bug without prior approval.

    Field

    Description

    Requester

    Select the requester for the new change. This can be the same or different from the original change.

    Assignment Details

    Update the assignee or assignment group, if required.

    Label

    Action

    Description / Example

    Title*

    Enter text

    Name or heading for the task.

    Example: Database Backup, Server Reboot

    Description*

    Label

    Action

    Description

    Upload Area

    Drag and drop / Browse to upload

    Upload files (Formats: PNG, JPEG, PDF, DOCX, XLSX, etc., Max size: 20MB).

    Category*

    Label

    Action

    Description / Example

    Name

    Enter a name

    Specifies the unique title or identifier of the risk. Example: Database downtime risk.

    Risk Type

    Question

    Weight

    Options

    Option Value

    How many assets will be affected by this server change?

    4

    More than 50 assets

    Name

    Description

    Comment

    A user/technician can see the comments on the change and also can add new comments.

    History

    Shows the history of the current change request from the time it was created.

    Interaction

    Name

    Description

    Quick Edit

    To perform quick edit actions like change manager, status, priority, urgency, severity, impact service, and the assignee. Use the "Detailed Edit" button to edit the Change details.

    Edit

    To edit the Change in detail.

    Delete

    Label/ Icon

    Description

    Expand Icon

    To View the change filters.

    Search Bar

    To help search for a specific change request using the Change ID, assignee, etc.

    Calendar

    Label

    Action

    Description / Example

    Status

    Auto-filled or selected manually

    Displays the change status (It will be closed).

    Close Change*

    Emergency Change

    Retrospective Change

    What do you see on the screen?

    Working on a Change

    Views of the Change Request

    The new change will retain the same subject structure as the original change, ensuring consistency.

    Note:

    • The quick action bar appears as a floater on each change line and is common in both Panel and Grid views.

    • The summary card details can be configured to suit requirements. Click on the "Configure" icon to customize the details you want to see on the screen.

    • The Configure icon is available only in Grid View.

    Conflict Detection

    Relation

    NCCM Job Association with Change Tasks

    Delegate Approval

    Planning and Risk Analysis

    Risks can be recorded for all change types—Major, Minor, Emergency, and Retrospective. They do not apply to Standard Changes, since these are pre-approved, low-risk, and follow a predefined process.

    These records can only be created and managed by privileged members, ensuring that risk documentation is accurate and controlled.

    Only the Change Manager is authorized to perform risk assessments.

    Assessment results can automatically update the change request’s priority based on evaluated risk.

    Miscellaneous

    Additional Icons

    Quick Actions

    Page Actions

    Close Change

    NCCM
    CLI Jobs
    Risk Templates

    Enter content using the editor

    Select from the drop-down

    Select from the dropdown

    Critical

    Shows the history of the change request created by the requester.

    To delete the Change. This action is irreversible.

    To view changes and releases scheduled on the calendar. The calendar supports Month, Week, Day, and List views and allows filtering releases based on status, type, priority, risk, team, and other criteria. Filtered releases are displayed according to their scheduled duration.

    Enter closure summary

    Problem Management
    Click here
    Automation – Tasks handled via scripts or automation tools.
  • Field – On-site/field-level tasks.

  • Recurring – Tasks that repeat on a schedule.

  • Maintenance – Preventive or scheduled maintenance tasks.

  • Work Order – Actionable job-oriented tasks.

  • 3rd Party – Task assigned to an external vendor.

  • NCCM – Tasks related to NCCM configurations or templates.

  • Cancelled (Close)

    Critical

    Test Plan

  • Dev Plan

  • Impact Assessment

  • Risk Assessment

  • Requirements

  • Rollout Plan

  • Rollback Plan

  • Other

  • Other – Any risk outside the above categories
    Partially Implemented: Some objectives were met; others deferred or missed.
  • Cancelled: Change was withdrawn before implementation.

  • Unsuccessful: Change failed and caused no improvement.

  • Escalation

    Escalation allows you to configure automated SLA notifications when a ticket is close to breaching or has already breached. You can define conditions, escalation sequences, and choose who should be notified (Users, Tags, or Roles).

    Escalations are configured inside an SLA Profile, and you can set multiple conditions based on SLA timers (Response/Resolution), priority, and breach status.

    Configure Escalation

    Label

    Action

    Description / Example

    Click Save to activate the escalation configuration in the SLA profile.

    Condition

    Click Add Another Condition

    Create a new escalation rule based on SLA type (Response/Resolution), breach status (Breached / Not Breached), and priority.

    When

    Select SLA Type

    Choose which SLA timer the condition applies to, e.g., Response.

    Is

    Choose Breached / Not Breached

    Define whether the escalation should trigger before SLA breach or after the SLA has breached.

    Priority

    Select priority values

    Choose the priorities (Critical/High/Medium/Low) for which escalation should apply.

    Sequence

    Click Add New Sequence

    Add one or more escalation sequences under the same condition.

    Escalate On

    Select from the drop-down

    Defines when an escalation is triggered based on the SLA condition. Options include Minutes and Percentage (%).

    • When the condition is Not Breached, users can select Percentage (%) or Minutes. Percentage triggers escalation based on the configured percentage of the SLA target time (e.g., 20% of the SLA time elapsed).

    • When the condition is breached, the unit defaults to Minutes. Escalation triggers after the specified number of minutes post-breach (for example, 5 minutes after the breach).

    • For Percentage (%), only values between 1 and 100 are allowed. Invalid values disable the Save action and display a validation message.

    Notify To – Users

    Select users

    Notify selected individual users. The system ensures a user receives only one notification, even if added via Tag and Users.

    Notify To – Tags

    Select tags

    Notify all users linked to the selected Tag (e.g., L2-Support).

    Notify To – Roles

    Select from the role list.

    Available roles: Requester, Assignee, Team, Submitter, Owner, Followers, etc. A notification is sent to the live role mapped to the ticket.

    Change Management

    ITIL defines Change as "the addition, modification, or removal of any authorized, planned, or supported service or service component that could affect services." In other words, a Change is adding, removing, or modifying anything that could directly or indirectly affect the organization's services and operations. The changes could include documentation, processes, applications, or IT infrastructure. In Infraon, the module that handles all the change requests is called "Change."

    Change Management is a set of processes defined to manage the lifecycle of a change request. It aims to minimize risks and disruptions to IT services and business operations while implementing changes.

    Benefits of Change Management

    • Reduced system downtime and outage

    • Faster change implementation

    • Decreased negative impact on business and IT services

    • Visibility into future IT changes

    Change Manager - A Change Manager is responsible for reviewing the submitted change requests, scheduling Change Advisory Board(CAB) meetings, updating the change records, reviewing the rollback and rollout plans, coordinating the implementation of changes, and reviewing the implemented changes. Usually, a high-level manager or a Domain Expert is assigned as a Change Manager to a change request.

    Change Advisory Board(CAB) - A Change Advisory Board (CAB) may consist of Business, IT Operations, Development, Customer, Domain Experts, and Solution Architects, depending upon the type of the change. A CAB is carefully selected to ensure all facets of an organization are represented while discussing the impacts, benefits, and implementation of a change. CAB requires financial data, the technical advantage of the change request, the number of resources required, criticality, and so on, to make an informed decision on the change request. Depending upon the severity of the change, the Change Manager may decide whom to include in the discussions. A CAB chooses whether to approve or reject a change.

    Infraon's Change Management module enables users/organizations to implement changes through the following steps seamlessly:

    • Change Detection is the first step of Change Management. For example, a customer may request a change in the services or ask for additional services. This is logged as a change request. A change request may also arise from a ticket, request, or problem.

    • Change Recording - A technician or user with the required permissions can log a change in the module.

    • Planning—In this stage, the change request is planned. A comprehensive plan is essential for the successful implementation of a change. A detailed plan showcases the risks, impacts, rollout plan, rollback plan, and associated downtime(if any) to all stakeholders. Planning is important in getting approvals from the Change Advisory Board (CAB).

    Apart from these, Infraon also covers change ownership, monitoring, tracking, and communication - throughout the life cycle of each change request.

    Changes are managed through the "Change" module. Users with appropriate permissions can raise changes. Changes follow multiple state(s) and status(es) throughout their life cycle.

    Customized Status(es) can be configured from the 'Workflow' module to suit the requirement.

    Demo data for ITSM module change for new Org

    Knowledge Base Modules! Explore added knowledge articles to understand the functionality and purpose of KB modules.

    Analysis - A detailed analysis is performed to understand a change's risks and impacts on the organization or service(s).

  • Change Approvals - The change plan needs to be reviewed, and the Change Advisory Board (CAB) decides. The change plan may be approved or rejected.

  • Change Implementation - Once approved, the change manager ensures the change is implemented as detailed in the plan and at the right time. A Change Manager also ensures coordination between different teams involved in the change implementation.

  • Review - Once a change is implemented, a post-implementation review is conducted to confirm whether the change was successful. A review is also performed to determine if the change achieved its objectives. If the change implementation is unsuccessful, the rollback plan is activated promptly.

  • Closure - This is the last step in the Change management process. After conducting a post-implementation review, the change can be closed with closing comments on whether the change was successful, executed on time, and so on.

  • State

    Status

    Status Scenario

    Open

    New

    When a new change is logged in the system.

    In Progress

    Essential Roles in Change Management

    Change Management Process

    State and Status

    Easily convert resolved Changes to Knowledge Base articles. KB icon appears post-resolution, ensuring efficient knowledge management.

    Change Management

    Planning

    When the planning of the change request is in progress.

    In Progress

    Analysis

    When the possible risk analysis is in progress.

    In Progress

    Implementation

    When the proposed change plans are being implemented.

    In Progress

    Deployment

    When the change is being deployed in production.

    In Progress

    Verification

    When the deployed change is being verified.

    On Hold

    Pending

    If any changes are pending to be implemented.

    Close

    Closed

    After Post Implementation Review, the change can be closed with closing comments.

    Close

    Cancel

    If the change implementation is canceled.

    ITSM Change Management

    Add Report

    Click Add Report in the top-right corner of the Report page to create a new report. The Add Report page contains three tabs:

    • Category

    • Configuration

    • Filter

    Each tab serves a specific purpose in setting up the report.

    Category

    Allows users to select the report category and the specific report they want to create. The selected report determines the type of data and reporting options available for configuration.

    Label
    Action
    Description/Example
    Label
    Action
    Description/Example
    Label
    Action
    Description/Example
    Label
    Action
    Description/Example
    Label
    Action
    Description/Example
    Label
    Action
    Description / Example
    Label
    Action
    Description / Example

    After selecting the specific Report, click Next to add Configuration.

    Allows users to enter the report name and configure the report settings, such as selecting the required columns and other options available for the selected report. Users can preview the report and save the configuration.

    Configuration boxes vary based on the selected Report. You will see three to four sections in the configuration tab. Refer to the table for more information.

    Report Configuration | Specific Configuration

    Label
    Description

    After selecting the appropriate boxes on the Configuration tab, click Next to add details on the Filter tab.

    Allows users to define conditions to narrow down the report data. Users can apply available filters, such as asset tags, resource tags, and custom filters, depending on the selected report.

    Filter options vary based on the selected Report. You will see three sections in the Filter tab.

    You can apply a filter to see only the details you selected.

    Add Report | Filter

    Label
    Description

    After applying filters, click View Report to see your report on the Report dashboard.

    The View Report option allows you to generate and preview the report based on the selected report configuration, filters, and other parameters.

    The report preview displays the data based on the configuration and filters selected by the user. The displayed columns and data depend on the report type and the options selected during configuration.

    For example, asset-related reports can display the columns selected during report configuration, while filters such as Duration, Asset Tag, and custom filters determine the data included in the report.

    The Report Setup Options section explains the available fields and settings used to configure a report in Infraon. Users can select the required columns, define applicable devices using tags, configure custom filters, and link related reports.

    Depending on the selected report type, additional configuration options may be available. These settings determine the data included in the report and how it is grouped, filtered, calculated, or displayed. The available options vary depending on the selected report type.

    After selecting View Report, you can provide a title and description for the generated report.

    Report Configuration | Title and Description

    Field
    Description

    Report Configuration | Left Panel

    Label
    Action
    Description/Example

    Report Configuration | Specific Configuration

    Label
    Action
    Description/Example

    Click Data Privacy to open the Mask/Unmask Requester Information panel.

    The Data Privacy panel provides controls for masking or unmasking requester information in the report.

    Report Configuration | Data Privacy

    Label
    Action
    Description/Example

    Admins can enable hiding the requester’s info in reports to comply with data privacy regulations.

    The report configuration screen provides Public and Private options to control the report's visibility.

    Label
    Action
    Description/Example

    Example:

    Select the required users and/or teams to provide access to the private report.

    Only the users and teams selected in the Assignee section are assigned to the private report.

    Allows users to configure and manage report generation schedules by selecting the report format, scheduling frequency, execution date and time, and email delivery details. Users can enable or disable schedules, update existing configurations, and submit the report configuration.

    Report Configuration | Schedule

    Label
    Action
    Description/Example

    For example: Scheduled on 6 October 2026, 12:00 (Asia/Kolkata)

    The configured schedule can also be reflected in Schedule History, where details such as the report name, schedule type, execution times, status, file type, and generated file can be viewed.

    The Preview Report displayed in the generated report depends on the selected report type and the configuration applied while creating the report.

    The report displays the data relevant to the selected report and its configured columns, filters, timescale, and other report-specific settings.

    Example

    The data displayed varies according to the selected report.

    • An Agent Uptime Report displays agent and asset-related information based on the selected columns.

    • An SLA Report displays SLA-related information based on the selected SLA Profile, Metric, Timescale, and other applicable settings.

    • An Asset Delivery Penalty Report displays delivery and penalty-related information based on its configured fields.

    Therefore, the report data varies depending on the selected report type and its configuration. The available columns and generated data are determined by the selected report.

    Reports can be exported in the formats supported by the selected report, such as PDF, CSV, or XLSX. The exported report contains the data generated according to the configured report settings.

    For reports with linked reports, the exported output can contain the linked report data as separate sections or tables. HTML export is also supported for applicable reports.

    Inventory Agent Installation Report

    Displays inventory agent installation and uptime details for managed assets. The report includes fields such as Agent Name, Asset Name, Serial Number, IP Address, Location, Installation Date, Last Contact Time, Agent Version, and Agent Uptime in Minutes. By default, the report displays all assets without applying any grouping. Users can optionally group the report by criteria such as Location to organize the results before previewing or saving the report. The report dynamically reflects updated asset and agent-related information after asset modifications. The report supports Send Now, Schedule Report, Clone, Edit, and Delete actions. Users can export the generated report in PDF, XLSX, and CSV formats.

    Displays inventory agent installation and uptime details for managed assets. The report includes fields such as Agent Name, Asset Name, Serial Number, IP Address, Location, Installation Date, Last Contact Time, Agent Version, and Agent Uptime in Minutes. By default, the report displays all assets without applying any grouping. Users can optionally group the report by criteria such as Location to organize the results before previewing or saving the report. The report dynamically reflects updated asset and agent-related information after asset modifications. The report supports Send Now, Schedule Report, Clone, Edit, and Delete actions. Users can export the generated report in PDF, XLSX, and CSV formats.

    Agent Uptime Report

    View / Configure

    Asset Audit Summary Report

    Users can filter this report using options like Change Type, Custom Filters, and Location conditions.

    Provides visibility into API consumption across API Users. By default, the report displays Date/Month, API User, Total Calls, Endpoint, Method, and Distinct IPs. Optional columns, such as Full Name and Email, can be included by selecting them. Data can be filtered using fields such as API User, Endpoint, Method, and Email to analyze API usage patterns. The report groups API activity by user, endpoint, and HTTP method, helping administrators monitor API consumption, identify frequently used endpoints, track unique source IP addresses, and review license utilization trends. Supports report preview, scheduling, and export in Excel, CSV, and PDF formats.

    Asset Depreciation Report

    Click the Helpdesk Reports on the left panel and select the Depreciation Report

    Audit Reports

    Users can select Audit Report, enter the report name, configure the required fields and custom filters, and preview the report. They can save, edit, clone, or delete the report. Users can generate the report after modifying the conditions and export it in Excel, CSV, or PDF formats. The report can be scheduled for email or folder delivery, including immediate delivery. Users can also select a timescale to filter the report data for a specific period.

    Displays audit information based on the selected category, fields, custom conditions, values, and timescale. The report includes audit details such as Sl. No., Module, Event, and Description. Users can apply custom filters to refine the displayed audit data and select a timescale to generate the required results. The report can be previewed, generated, edited, cloned, or deleted based on the user's requirements. Users can export the report in Excel, CSV, and PDF formats and send it through email or folder dump either immediately or on a scheduled basis. For MSP users, the displayed data is based on the user's configured visibility.

    Availability Reports

    Select the availability report box to send the report.

    Select the availability report box to send the report. The availability report helps technicians analyze situations in which problems have occurred. It can be plotted against time in each interval and viewed as a data table, line chart, area chart, bar chart, etc. Example: Login hours, shift hours, availability percentage, etc.

    Device Reachability Report

    Users can configure the report by selecting the required columns, asset tags, custom filters, and timescale before previewing or generating the report. Users can filter the report data based on selected asset tags or custom filter conditions. The report supports Branch Name and Branch Code columns, which can be selected, edited, exported, scheduled, and included in immediate report delivery. Users can enable Additional Metrics to select metrics such as Packet Loss %, Latency (msec), CPU Utilization, Memory Utilization, Disk Utilization, Reboot Counter, and System Uptime. Selected metrics are displayed as separate columns without creating duplicate rows for the same device. The report can be viewed, generated, edited, cloned, deleted, exported in Excel, CSV, and PDF formats, and scheduled for email or folder delivery.

    Active Event Report

    Click the Event Reports on the left panel and select the Event Report.

    The event report provides statistical information about the specific event for the selected time interval.

    Active Event Summary Report

    Click the Event Reports on the left panel and select the Event Summary Report.

    Label

    Action

    Description / Example

    API Metering Data Report

    Users can configure this report by selecting required columns, applying custom filters, defining a timescale, choosing a View By option (Day or Month), and specifying the number of records using the Top setting.

    Provides visibility into API consumption across API Users. By default, the report displays Date/Month, API User, Total Calls, Endpoint, Method, and Distinct IPs. Optional columns, such as Full Name and Email, can be included by selecting them. Data can be filtered using fields such as API User, Endpoint, Method, and Email to analyze API usage patterns. The report groups API activity by user, endpoint, and HTTP method, helping administrators monitor API consumption, identify frequently used endpoints, track unique source IP addresses, and review license utilization trends. Supports report preview, scheduling, and export in Excel, CSV, and PDF formats.

    SLA Report

    Authorized vs Unauthorized Trend Report

    View Report Details

    Displays the trend of authorized and unauthorized configuration changes over the selected time-period. The report provides a graphical and tabular representation of change counts over time. Data is generated based on configuration comparison results within the selected filters.

    Note: Graph representation is not included in CSV/Excel exports.

    Blacklisted Software Details

    Users can select the Blacklisted Software Details Report, configure the required fields, and preview the report. They can filter the report using asset tags or custom filters, select the required columns, and generate the report based on the selected conditions. Users can save, edit, clone, or delete the report. The report can be scheduled for email or folder delivery, including immediate delivery, and exported in Excel, CSV, or PDF formats.

    Displays details of blacklisted software installed on managed assets. Users can filter the report based on asset tags, categories, conditions, and values and select the columns required for the report. The report data is generated according to the selected filters and columns and is displayed based on the logged-in user's visibility.

    License Allocation History

    Users can select License Allocation History Report, configure the report, and preview the results. They can apply custom filters and timescale settings, select the required columns, and generate the report based on the selected conditions. Users can save, edit, clone, or delete the report. The report can be scheduled for email or folder delivery, sent immediately, and exported in Excel, CSV, or PDF formats.

    Statistics

    You can modify your report by adding statistical details like CPU utilization, Availability, etc.

    Columns

    You can choose assets from the column. This column is optional; you can proceed to the next tab without filling it.

    Duration

    Select the particular duration that you want to see on the report. By default, it is set to the last hour.

    Asset Tag

    Select any asset tag for your report.

    Incident Tags

    Title

    Enter a name for the report.

    Description

    Enter a description for the report, if required.

    Columns

    Select or deselect the required report fields.

    Allows you to select the required columns for the report. The selected fields are displayed as columns in the generated report and are included when the report is exported. Note: The available columns depend on the selected report type.

    Applicable Device

    Select

    Asset Scope

    Select the scope of assets to be included in the report.

    Determines which assets are considered when generating the report.

    Active

    Data Privacy

    Click Data Privacy to open the privacy settings.

    Opens the Mask/Unmask Requester Information panel, where you can configure how requester information is displayed in reports.

    Name

    Enable or disable the toggle under Mask or Unmask.

    Public

    Select Public to make the report available according to the public report visibility settings.

    A public report can be accessed by users who have the required report visibility permissions.

    Private

    Select Private to restrict the report's visibility.

    Schedule

    Click Schedule to open the scheduling panel.

    Opens the Schedule settings for the report.

    Report Type

    Select the format in which the scheduled report should be generated.

    Agent

    Asset

    Audit

    Availability

    Event

    ITSM

    NCCM

    Software

    Only users with Administrator privileges can view and access System Reports.

    Release and Change reports include related record information during report extraction. While configuring the report, selecting the Relation column displays IDs of all linked records, such as Tickets, Changes, Problems, Releases, and Requests.

    • The Relation column lists related record IDs for each Release or Change.

    • If no relation is found, the column remains empty.

    • The Location Name / Installed Location filter supports the IN and IS conditions. Selecting IS allows you to choose an empty value to retrieve assets that lack a location assignment.

    • A custom field filter for Asset Custom Field (Zone, Circle, Time, etc.) is now available in all summary reports. These fields are part of the custom attributes added in IT Assets and help refine report data directly within the tool for quicker analysis. The export option remains available for full report downloads.

    The Service Catalogue field is available as a custom filter in ITSM reports. Users can select one or more service catalogue entries while creating or editing a report.

    When applied, the report data is filtered to display only records associated with the selected service catalog entries. The filter is supported in both report configuration and preview mode.

    Configuration

    Filter

    Report Configuration

    Report Setup Options

    The configuration fields displayed in this section vary depending on the selected report type. These fields are available only for reports that require additional configuration.

    Data Privacy

    The Mask and Unmask options determine whether requester information is hidden or displayed. Ensure that unmasking is enabled only for users with the appropriate authorization.

    Public and Private

    Public and Private control the visibility of the report. They are separate from Data Privacy, which controls the masking or unmasking of requester information.

    Schedule

    Preview Report

    Exporting the Report

    Displays agents' uptime for assets over a selected time range, allowing users to analyze availability and operational duration. By default, the report shows overall uptime from the agent installation date to the current date. Users can apply predefined filters (e.g., Last 7 Days, Last 30 Days) or select a custom date range to view uptime for specific periods, such as weekly or monthly analysis. Supports filtering using asset tags and custom conditions, column selection, sorting, and preview before saving. Reports can be exported in CSV, XLSX, and PDF formats and scheduled for automated delivery via email or to a folder.

    Generate the Depreciation Report for Assets and select the relevant report from the provided list. Submit the report request and select the financial year start date to generate the report based on your needs. The generated report provides accurate and up-to-date information about asset depreciation.

    Asset Summary Report

    The report also supports Nested Grouping, allowing users to group report data using multiple Group By levels. Users can select up to four grouping fields, and the exported report maintains the same grouping structure as displayed in the report view.

    Provides a consolidated view of assets with configurable grouping and filtering options. Users can group assets using fields such as OS Name, Device Type, Status, Vendor, and other available asset attributes for reporting and audit purposes. The report supports a Split By option that breaks down asset counts by a selected attribute. When enabled, the report preview displays asset distribution with accurate split counts. The selected Split By configuration is retained during save, edit, view, and export operations.

    Asset Detailed Report

    Click on the Helpdesk Reports on the left panel and select the Asset Reports. Click on the Detailed Asset Report

    Comprehensive asset hardware, software, and activity log in one report, with a detailed asset report by selected tags and duration, and generates information that contains the asset name, IP address, inventory details, and more.

    Asset Allocation Report

    Users can configure the report by selecting the required columns, asset tags, custom filters, and timescale before previewing or generating the report. Users can filter asset data based on Allocation Time, Deallocation Time, or Acceptance Time and apply conditions such as Serial Number or Location Name / Installed Location. The report can be exported in Excel, CSV, and PDF formats, scheduled for email or folder delivery, or sent immediately. Users can also edit, clone, or delete the report configuration.

    Displays asset allocation information based on the selected columns, custom filters, asset tags, and timescale. The report supports Allocation Time, Deallocation Time, Acceptance Time, Acceptance timestamp, AMC Extension date, Asset Source, Service Hub, and Requester columns. Users can filter asset data using criteria such as Serial Number and Location Name / Installed Location, including assets with blank locations. The report can be filtered based on Allocation Time, Deallocation Time, or Acceptance Time and displays date and time values according to the user's current timezone. The report data is based on the logged-in user's visibility. Users can export the report in Excel, CSV, and PDF formats, including a Single Workbook Excel option, and can send or dump the report immediately or according to a configured schedule.

    Asset Audit Report

    Users can configure the report by selecting the required asset tags, custom filters, timescale, Sort By, and Sort Order before previewing or generating the report. Users can filter asset audit data using criteria such as Serial Number, Location Name / Installed Location, Asset Source, and Service Hub. The report can be exported in Excel, CSV, and PDF formats, including the Single Workbook Excel option. Users can schedule the report for email or folder delivery, or send or dump it immediately. The report can also be edited, cloned, or deleted based on their requirements.

    Displays asset audit information based on the configured fields, filters, timescale, and sorting options. The report is used to review and analyze asset-related audit data according to the user's visibility and selected criteria. Users can configure custom filters, such as Serial Number, Location Name / Installed Location, and Asset Source, to refine the displayed data. The report supports previewing and generating results, exporting data in Excel, CSV, and PDF formats, scheduling email or folder delivery, and performing immediate email or folder dump actions. The Single Workbook Excel option allows the report data to be downloaded as a single Excel workbook.

    Asset Replacement Report

    Users can configure the report by selecting the required asset tags, custom filters, timescale, Sort By, and Sort Order before previewing or generating the report. Users can filter replacement data using custom criteria, including Device Type, where the selected device type is matched against the current or previous asset device type. The report can be exported in Excel, CSV, and PDF formats from both the report view and grid. Users can schedule the report for email or folder delivery, or send or dump it immediately. The report can also be edited, cloned, or deleted based on their requirements.

    Displays asset replacement information based on the configured report fields, filters, timescale, and sorting options. The report lets users review asset replacement data and identify replacement-related information for current and previous assets. Users can apply asset tag and custom filters to refine the report data. The Device Type custom filter supports available device type values and filters the report when the selected value matches either the current or previous asset device type. The report supports previewing and generating updated results, exporting data in Excel, CSV, and PDF formats, scheduling email or folder delivery, and performing immediate email or folder delivery. Report data is displayed according to the logged-in user's visibility, and the selected timescale is included in the report data.

    Asset Report

    Users can configure the report by selecting the required columns, custom filters, Timescale Column, and time range before previewing or generating the report. The report supports fields such as PO Number, Recent Asset Allocation Time, Recent Asset Deallocation Time, Recent User Acceptance Time, Last Update Time, Agent Sync Time, AMC Extension Date, Serial Number, Location Name / Installed Location, Asset Source, Model Year, Service Hub, and supported Requester Columns. Users can apply custom filters such as Serial Number, Location Name / Installed Location, Asset Source, and PO Number to refine the report data. The report also supports an Asset Scope filter with Active and Deleted options, while Archived is available when the Asset Archival feature is enabled. When Deleted or Archived scope is selected, the corresponding deletion or archival information is automatically included in the report. Users can enable Show Stack Module to display stack module information grouped by asset. The report can be exported in Excel, CSV, and PDF formats.

    Displays asset information based on the selected columns, filters, timescale, and asset scope. The report is used to view and analyze asset details, including allocation and deallocation information, user acceptance time, PO number, agent synchronization details, AMC extension information, asset source, model year, Service Hub, requester details, and other configured asset data. The Timescale Column supports options such as Last Sync Time, Deleted Time, and Archived Time, allowing users to generate report data for a selected time range. When Asset Scope is set to Deleted, the report displays Deleted Time, Deleted By, and Delete Source; when set to Archived, it displays Archived Time, Archived By, Archive Reason, and Archive Notes. These scope-specific columns are automatically included based on the selected scope. The report supports previewing, generating, filtering, and exporting data, while selected time-based information is displayed according to the user's timezone.

    Asset Request / Owner Report

    Users can configure the report by selecting the required asset columns and applying Duration, Tags, Assignee, and Custom Filters before previewing or submitting the report. Users can edit the selected columns, filters, assignee, tags, and timescale, or clone an existing report and modify its configuration. Custom filters can be applied using criteria such as Serial Number, Location Name / Installed Location, and Asset Source. The report also supports Requester Columns, which can be selected, expanded, collapsed, or selected using Select All. Users can export the report using the Single Workbook Excel option, which downloads the asset data as a single Excel workbook. The report can also be edited, cloned, or deleted based on the user's requirements.

    Displays asset information based on the selected requester/owner, columns, duration, tags, assignee, and custom filter criteria. The report is used to view asset details associated with requesters or owners and to refine the displayed data using the available report configuration options. Users can select supported Requester Columns to display requester information, including correctly formatted dates and translated values, with multiple or no requesters handled in the report output. The report also supports fields such as AMC Extension Date, Asset Source, and Service Hub. Custom filters can be used to refine results by Serial Number, Location Name / Installed Location, or Asset Source, including filtering assets with blank locations using the IS condition. The report supports previewing and viewing the configured data, editing or cloning the configuration, and downloading the report using the Single Workbook Excel option.

    Asset Wise Software License Allocation Summary

    Users can configure the report by selecting Group By, Nested Grouping, Split By, and Custom Filters before previewing or generating the report. The Group By field defaults to Publisher and provides fields grouped under Asset, Asset Custom Field, Software License, and License Custom Field categories. Users can enable Nested Grouping to organize the report across multiple grouping levels, with each level displaying distinct Asset Count and License Count values. The Split By option provides a category-wise breakdown, including an Other bucket for missing values. Users can apply custom filters using Asset fields, Asset Custom Fields, Software License fields, and Software License custom fields. The report can be edited, cloned, viewed, and generated with updated configurations, and the generated data can be exported in Excel, CSV, and PDF formats.

    Displays a summary of software license allocations across assets, grouped by the selected criteria. The report is used to analyze software license allocation at the asset level and distinguishes between Asset Count and License Count. Only assets with at least one active software license allocation are included in the report. Users can group the data by Publisher or other supported Asset, Asset Custom Field, Software License, and License Custom Field fields. Nested Grouping provides multiple levels of grouping with per-level asset and license counts, while Split By provides a breakdown based on the selected category. Custom filters can be applied to refine the report using software fields such as Publisher, License Type, and Vendor, as well as configured Software License custom fields.

    Consumable Asset

    Users can configure the report by selecting the required columns, custom filters, and custom field columns before previewing and saving the report. The report supports editing the selected columns and filters, cloning existing report configurations, and deleting reports. Users can schedule the report for delivery and use the Email Report option to send the report to specified recipients. The report data is displayed according to the user's visibility permissions over consumable assets. Users can also download the generated report in the selected format.

    Displays consumable asset information based on the selected columns, custom filters, and custom field columns. The report is used to view and manage consumable asset data according to the user's configured report criteria and visibility permissions. Users can select standard and custom field columns to control the information displayed in the report and apply custom filters to refine the results. The report supports saving, editing, cloning, deleting, scheduling, and emailing the generated report. It is available under the Asset Reports category for asset-based licenses/subscribers and supports report export in the available formats.

    Displays device availability and reachability information for monitored devices. The report is used to validate whether devices are available and reachable and to analyze network and system performance metrics. When a device interface is temporarily brought down without rebooting the device, the report can reflect Availability and Reachability separately, while a device shutdown causes both values to reflect the device being unavailable. The report supports additional performance metrics, with N/A displayed when selected metric data is unavailable. System Uptime is displayed in a standard time format, and selected metrics are retained when the report configuration is saved. Branch Name and Branch Code values are reflected from the asset data and are included in report exports and scheduled deliveries. Missing values for Resource Alias, Resource Description, and Resource Tags are displayed as blank cells rather than hyphens. Report data is displayed according to the logged-in user's visibility, including MSP user visibility.

    Dormant Port Report

    Users can configure the report by selecting asset tags and custom filters before previewing or generating the report. Users can also add linked reports by selecting reports from the available dropdown, with the linked report data displayed after the Dormant Port Report data. The report supports sorting based on the selected Sort option. Users can edit, clone, or delete the report configuration and can export the report in Excel, CSV, PDF, and Word formats where supported. The report can also be scheduled for email or folder delivery, including immediate email or folder delivery.

    Displays dormant port information based on the configured report criteria. The report is used to review dormant port data and refine the results using asset tags, custom filters, and sorting options. Users can preview and generate updated report data, link additional reports, and view the linked report data after the primary report. Report data is displayed according to the logged-in user's visibility. The report supports export, scheduling, immediate delivery, and report management actions such as add, edit, clone, and delete. Actions performed on the report, such as adding, editing, or deleting, are recorded in the Audit Module.

    Downtime Report

    Users can configure the report by selecting columns, asset tags, resource tags, custom filters, timescale, and event type before previewing or generating the report. The report supports Branch Name and Branch Code columns, which can be selected, edited, exported, cloned, and included in scheduled or immediate report delivery. Users can enable Show Down Nodes to display either only nodes that were down during the selected timescale or all up/down nodes for the selected duration. Custom filters support resource fields such as Resource Name, Resource Alias, Resource Description, Link Mode, Resource Type, ISP Name, Link ID, Link Name, Link Bundle Name, Link Bundle Capacity, and Resource State, as well as resource custom fields. Users can also configure Penalty settings when the required permission is available and select a configured penalty configuration. The report supports Business Hour selection, which adds a Business Hour column when configured. The Maintenance toggle allows users to display maintenance-related columns and data. Users can edit, clone, or delete the report, export it in Excel, CSV, PDF, and supported Word formats, and schedule it for email or folder delivery, including immediate delivery.

    Displays downtime information for assets and resources based on the configured report criteria and selected timescale. The report is used to analyze downtime events and identify affected assets or resources during a specified period. Users can refine the results using asset tags, resource tags, event type, and custom filters. The Show Down Nodes option can restrict the report to nodes that were actually down during the selected timescale. When configured, the report can calculate penalty-related information based on the selected penalty configuration, including Penalty Amount, Service Cost, and Penalty Percentage, as applicable. The report can also display the selected Business Hour and maintenance information such as Maintenance Profile, Maintenance Time, and Maintenance Schedule. Maintenance details are displayed when configured for the corresponding asset or resource, and multiple maintenance profiles for the same asset can be shown with their respective durations. Report data is displayed according to the logged-in user's visibility, including MSP user visibility.

    Downtime Report (Availability Statistics)

    Users can configure the report by selecting the required columns, asset tags, resource tags, custom filters, Top value, Business Hour profile, stats, timescale, and sort order before previewing or generating the report. Users can apply custom filters using the available criteria and filter the report based on selected asset or resource tags. The report supports Branch Name and Branch Code columns, which can be selected, edited, exported, cloned, and included in scheduled or immediate report delivery. Users can select a Business Hour configuration to display the corresponding Business Hour column and values. The report can be viewed, generated, edited, cloned, or deleted, exported in Excel, CSV, PDF, and supported Word formats, and scheduled for email or folder delivery, including immediate delivery.

    Displays downtime and availability statistics based on the configured report criteria and selected timescale. The report is used to analyze availability-related data for assets and resources and can be refined using tags, custom filters, Top value, Business Hour profile, selected stats, and sort order. Users can select specific columns, including Branch Name and Branch Code, and the selected branch information is reflected in the report, exports, cloned reports, and scheduled or immediate deliveries. When Business Hour is selected, the report displays the configured business hour name or time window in a Business Hour column; when no Business Hour is selected, the column is not displayed. Report data is displayed according to the logged-in user's visibility, including MSP users.

    Flap Count Report

    Users can configure the report by selecting the required columns, asset tags, resource tags, custom filters, event types, and timescale before previewing or generating the report. Users can apply custom filters and filter the report data based on selected asset or resource tags. The report supports Branch Name and Branch Code columns, which can be selected, edited, exported, cloned, and included in scheduled or immediate report delivery. Users can view and generate the report based on updated conditions, and edit, clone, or delete the report configuration. The report can be exported in Excel, CSV, and PDF formats and scheduled for email or folder delivery, including immediate email or folder delivery.

    Displays flap count information based on the configured report criteria, selected event type, and timescale. The report is used to view and analyze flap-related data for assets and resources. Users can refine the report using asset tags, resource tags, custom filters, event types, and timescale. Branch Name and Branch Code can be included as report columns, and the configured branch information is reflected in the report, exports, cloned reports, and scheduled or immediate deliveries. Report data is displayed according to the logged-in user's visibility, including MSP users.

    Link Percentile Report

    Users can configure the report by selecting the required asset tags, resource tags, custom filters, Top value, stats, timescale, chart type, resolution, and Percentile value before previewing or generating the report. Users can select Line, Bar, or Area chart types and enable Show Summary based on their requirements. The report can be viewed and generated with updated conditions, and users can edit, clone, or delete the report configuration. Users can export the report in Excel, CSV, and PDF formats and schedule it for email or folder delivery, including immediate email or folder delivery.

    Displays link percentile data based on the configured report criteria, selected statistics, timescale, resolution, and Percentile value. The report is used to analyze link performance using graphical representations and percentile measurements. Users can filter the report using asset tags, resource tags, and custom filters, and limit the displayed rows using the Top value. The report supports Line, Bar, and Area charts, with an optional Show Summary configuration. When a Percentile value is configured, the corresponding percentile line is displayed in the graph. Report data is displayed according to the logged-in user's visibility, including MSP users.

    Reachability Vs Availability Report

    Users can configure the report by selecting asset tags, resource tags, custom filters, timescale, resolution, limit, and sort options before previewing or generating the report. Users can add linked reports by selecting reports from the available dropdown, with the linked report data displayed after the Reachability vs Availability Report data. The report supports a maximum limit of 1000 records. Users can view, generate, edit, clone, or delete the report configuration and export the report in Excel, CSV, PDF, and supported Word formats. The report can also be scheduled for email or folder delivery, including immediate email or folder delivery. Add, edit, and delete actions are recorded in the Audit Module.

    Displays Reachability and Availability data based on the configured criteria, selected timescale, and resolution. The report is used to compare device reachability and availability over a selected period. Users can refine the report using asset tags, resource tags, custom filters, timescale, resolution, limit, and sort options. When a device is rebooted during a specific period and subsequently comes back online, both Reachability and Availability are shown as 0% for that period. Linked report data is displayed after the primary report data when configured. Report data is displayed according to the logged-in user's visibility.

    Site Downtime Report

    Users can configure the report by selecting asset tags, resource tags, custom filters, timescale, Group By, event type, Business Hour, SLA options, and the Based on option before previewing or generating the report. Users can select All Node Down or Any Node Down to determine how downtime is calculated for grouped nodes. The report supports Business Hour-based downtime calculation and can display additional columns when SLA options are enabled. Users can view, generate, edit, clone, or delete the report configuration and export the report in Excel, CSV, and PDF formats. The report can also be scheduled for email or folder delivery, including immediate email or folder delivery.

    Displays site downtime information based on the configured criteria, grouping, event type, Business Hour, and selected downtime calculation option. The report is used to analyze downtime across nodes within a site or location. With All Node Down, downtime is calculated based on the intersection of the periods when all nodes are down. With Any Node Down, downtime is calculated based on the periods when one or more nodes are down, including the applicable overlapping and non-overlapping downtime periods. Business Hour limits the calculation to the configured business-hour window. Users can group the report using the selected Group By option and filter the data using asset tags, resource tags, custom filters, timescale, and event type. When SLA is enabled, additional SLA-related columns are included in the report. Report data is displayed according to the logged-in user's visibility, including MSP users.

    The event summary report gives comprehensive statistical data for all the events for the selected time interval.

    Event Aging Report

    Users can configure the report by selecting the required columns, asset tags, resource tags, custom filters, and timescale before previewing or generating the report. Users can apply custom filters using the required category, condition, and value to refine the report data. The report supports Branch Name and Branch Code columns, which can be selected, previewed, exported, cloned, and included in scheduled or immediate report delivery. Users can view and generate the report based on updated conditions, and edit, clone, or delete the report configuration. The report can be exported in Excel, CSV, and PDF formats and scheduled for email or folder delivery, including immediate email or folder delivery.

    Displays event aging information based on the configured columns, filters, tags, and selected timescale. The report is used to view and analyze event data based on aging criteria and configured conditions. Users can filter the report using asset tags, resource tags, and custom filters, and select the required columns, including Branch Name and Branch Code. Branch information is reflected in the report, exports, cloned reports, and scheduled or immediate deliveries. Report data is displayed according to the logged-in user's visibility, including MSP users.

    Events Aging Summary

    Users can configure the report by selecting the required asset tags, resource tags, custom filters, Group By, and other report fields before previewing or generating the report. Users can apply custom filters using the required category, condition, and value to refine the report data. The report supports grouping by Severity, with the available severity values depending on the feature flag configuration. When the feature flag is enabled, the report includes Critical, Major, Minor, Warning, Unknown, Normal, and Disabled; when disabled, it includes Critical, Major, and Minor. Users can also group the report by Location Name, where assets without a mapped location are displayed under the Others category. The report can be viewed and generated based on updated conditions, edited, cloned, or deleted, and exported in Excel, CSV, and PDF formats. Users can schedule the report for email or folder delivery, including immediate email or folder delivery.

    Displays a summary of event aging information based on the configured grouping, filters, asset/resource tags, and report conditions. The report is used to analyze event data by selected grouping criteria such as Severity or Location Name. Severity grouping displays the available severity categories according to the feature flag configuration. When grouped by Location Name, event data for assets with mapped locations is displayed under the respective location, while assets without a mapped location are grouped under Others, and the total event count includes both mapped and unmapped location assets. Report data is displayed according to the logged-in user's visibility, including MSP users.

    History Event Report

    Users can configure the report by selecting the required columns, asset tags, resource tags, custom filters, and timescale before previewing or generating the report. Users can apply custom filters using the required category, condition, and value to refine the report data. The report supports Branch Name and Branch Code columns, which can be selected, previewed, exported, cloned, and included in scheduled or immediate report delivery. Users can view and generate the report based on updated conditions, and edit, clone, or delete the report configuration. The report can be exported in Excel, CSV, and PDF formats and scheduled for email or folder delivery, including immediate email or folder delivery.

    Displays historical event information based on the configured columns, filters, tags, and selected timescale. The report is used to view and analyze historical event data, including the available severity events. Users can filter the report using asset tags, resource tags, and custom filters, and select the required columns, including Branch Name and Branch Code. Branch information is reflected in the report, exports, cloned reports, and scheduled or immediate deliveries. Report data is displayed according to the logged-in user's visibility, including MSP users.

    History Event Summary Report

    Users can configure the report by selecting the required columns, asset tags, resource tags, custom filters, and timescale before previewing or generating the report. Users can apply custom filters using the required category, condition, and value to refine the report data. Users can view and generate the report based on updated conditions, and edit, clone, or delete the report configuration. The report can be exported in Excel, CSV, and PDF formats from both the report view and grid. Users can schedule the report for email or folder delivery, including immediate email or folder delivery. Report data is displayed according to the logged-in user's visibility, including MSP users. When the feature flag is enabled, users can group events by severity and view Critical, Major, Minor, Warning, Unknown, Normal, and Disabled events. When the feature flag is disabled, only Critical, Major, and Minor severity events are displayed.

    Displays a summary of historical event information based on the configured columns, filters, tags, and selected timescale. The report is used to view and analyze historical event data. Users can filter the report using asset tags, resource tags, and custom filters, select the required columns, and generate the report for the selected timescale. Report data respects the visibility of the logged-in user. Severity-based event grouping varies based on the feature flag configuration.

    Login Logout Report

    Users can configure the report by selecting the required asset and event-related columns and applying custom filters before previewing or generating the report. Users can select and modify columns and custom filters to refine the report data. The report can be saved, edited, cloned, or deleted. Users can schedule the report for delivery and send the report through email by selecting the report type and recipient email addresses.

    Displays login and logout event information based on the selected columns and configured custom filters. The report allows users to view login/logout activity for assets and analyze event-related information. Report data is displayed according to the logged-in user's visibility and asset access. Users can modify the column and filter configuration, clone the report with its existing configuration, schedule report delivery, or send the report through email.

    Click on the report to configure and generate SLA-based reports.

    Tracks SLA violations and calculates penalties based on predefined contract rules. The report highlights breached SLAs within the selected time interval and provides a penalty summary categorized by ticket, service, team, customer, location, service category, and requester username. Approved By displays the usernames of approvers associated with the request/ticket, while Approval Comment displays the comments added during the approval process. If approval details are unavailable, the report displays Not Approved or No Comment based on the report data. SLA Exclusion ensures that excluded tickets or durations are not considered in SLA evaluation, breach calculations, or reported metrics.

    Task Report

    Select the Task Report option from the ITSM reports category and proceed to configure columns and filters.

    The Task Report provides visibility into all tasks across the system based on the selected filters. Users can configure columns such as Task Title, Assignee, Status, Priority, Due Date, and more to generate customized reports. Filters such as status, assignee, priority, and module help narrow down the task data. The report supports preview, export (CSV, XLSX, PDF), scheduling, cloning, and editing.

    Location Report

    Click on the organization on the left panel and select the address book. Click on the 'Export' icon.

    Manage and track the location of the assets by exporting the address book details from the organization's address book. With the ability to import and export location details, quickly generate comprehensive location reports for the assets.

    SLA Compliance Report

    Configure and generate a report

    Shows incident performance against selected SLA Profiles and Metrics. Filters data based on SLA Profile, Metric, Timescale, and Group By options (Level, Team, Assignee, Catalogue, Impact Service). Includes Incident Closed Count, SLA Violations, Compliance%, and Non-Compliance%. Supports CSV export. Example: View all incidents under a selected SLA Profile (e.g., High Priority SLA) and Metric to check how many met or breached the SLA, grouped by team or level, along with compliance percentages.

    Installed vs purchased report advance

    Click on the reports on the left panel and select software reports.

    Access the 'Software Installed vs Purchase' report in the software report section. Track software names, purchase details, installation status, and compliance metrics.

    Backup Failed Devices Report

    View Failed Backup Details

    Displays devices for which the configuration download (backup) has failed during execution. The report provides device-level details, including IP Address, Asset Name, Vendor, OS Version, Configuration Profile, Status, and Customer/Entity (MSP-based visibility). Data is generated based on failed configuration download results within the selected filters and time interval.

    Backup Not Configured Report

    View devices not configured for backup

    Displays device details where configuration download (backup) is not configured. The report helps identify assets that do not have a download job or configuration profile associated for backup. Supports custom filters, MSP-based visibility, scheduling, and export options (CSV, PDF, XLSX).

    Change Job Trend Graph Report

    View Change Job Trend Details

    Displays the trend of CLI and upload job executions on a day-by-day basis in a graphical format. The report tracks the number of CLI jobs and upload jobs executed during the selected timescale. Supports filtering by IP Address, Device Group, Asset Tag, and custom filters, along with timescale selection, scheduling, and export options.

    CLI Job Report

    View CLI Job Details

    Displays detailed information of executed CLI jobs within the selected time range. Includes Job Name, Creation Time, Requester, Client IP, Device IP, Protocol Type, Device Account, Approval Status, Access Duration, Access Attempts, Change Request ID, Approver, and Session timelines. Supports filtering by Asset Tag, Custom Filters, Timescale, Resolution, and Top N limit, with export in CSV, XLSX, and PDF formats.

    CLI Jobs Approval Audit Report

    View CLI Job Approval Details

    Displays approval audit details for CLI jobs, including execution status, approver information, job execute time, and related device details. Data is generated based on CLI job approval audit records within the selected filters and timescale.

    Configuration Change Report

    View Configuration Change Report

    Displays detailed configuration change history for devices, including Running and Startup configuration changes. Includes Total Changes summary, Authorized vs Unauthorized changes, IP-based change tracking, configuration type, file version, and download time. Supports timescale filtering, custom filters, scheduling, and export options (CSV, PDF, XLSX).

    Configuration Discrepancies Report

    View Configuration Discrepancy Details

    Displays devices where the last downloaded configuration differs from previous, baseline, or startup/running configurations. The report identifies deviations across comparison types such as Current vs Previous, Current vs Baseline, and Startup vs Running. Provides device-level details, including IP Address, Asset Name, Configuration Profile, and discrepancy status.

    Configuration Download Result Report

    View Configuration Download Result Details

    Generates a detailed summary of configuration download activities for network devices. The report includes the status of each download (success or failure), device details, and any encountered errors.

    Configuration Download Status Report

    View Report Details

    Displays the current status of configuration download operations.

    Device CLI Statistics Report

    View Device CLI Job Statistics Report

    Provides a statistical summary of CLI job execution status counts, including Total CLI Jobs, Waiting for Approval, Approved, Rejected, Expired, In Progress, and Session Ended. Supports timescale selection, custom time range, asset tag filtering, column selection, Top limit, scheduling, and export options (CSV, PDF, XLSX).

    Device Download Statistics

    Statistics View device download statistics

    Displays statistical data for devices where configuration download (backup) has been executed. Provides device-level download metrics, including IP Address, Creation Time, Total Downloads, Successful Downloads, and Failed Downloads. Supports custom filters, asset column selection, visibility filters, MSP filters, and export options (CSV, PDF, XLSX).

    Device Policy Statistics Report

    View Report Details

    Displays statistics related to policies associated with devices.

    Device Upload Job Statistics Report

    View Upload Job Statistics

    Displays total, successful, and failed configuration upload jobs per device within the selected time range. Includes device details such as IP Address, Hostname, Vendor, Model, and OS Type. Supports filtering by Organization, Asset Tags, Custom Filters, Timescale, and Top N limit, with export in CSV, XLSX, and PDF formats.

    Device Vulnerability Report

    View vulnerability overview

    Displays consolidated vulnerability details for managed devices under NCCM. Provides vulnerability-level information, including Vulnerability ID (CVE), Severity, CVSS Score, Published Date, Identified Time, Resolved Status, Resolved By, Resolved Time, Resolve Comments, and related device information. Supports default filters, resolution-based filtering, custom filters, scheduling, audit tracking, MSP visibility, and export options (CSV, PDF, XLSX).

    Device Vulnerability Statistics Report

    View vulnerability statistics by device

    Displays summarized vulnerability statistics for each device (IP address/node). Provides consolidated metrics including Total Vulnerabilities, Unresolved, Resolved, EOL, and EOS, along with device attributes such as IP Address, Hostname, Vendor, Model, OS Type, and Created Time. Supports tag-based filtering, custom filters, column selection, timescale selection, scheduling, sorting, MSP visibility, and export options.

    Jobs Account Audit Report

    View Jobs Account Audit Details

    Displays audit records for download job account activities within the selected time interval. Provides job-level and device-level details, including Device IP Address, Device Account, Connection Protocol, Agent, Connect Time, Connect Status, Job Type, Job Name, and execution information. Supports timescale selection, custom filters, column selection, scheduling, and export options (CSV, PDF, XLSX).

    Network Compliance Report

    View Compliance Details

    Provides a consolidated compliance overview for all active (non-deleted) managed devices. Displays IP Address and Hostname along with Backup Status, Startup vs Running comparison, Current vs Baseline comparison, Policy Association, Policy Compliance Status, and Vulnerability Status. Supports filtering, timescale, resolution, Top N limit, and export options (CSV, XLSX, PDF).

    Network Summary Report

    View Network Summary Details

    Displays device summary information based on Vendor, Configuration Profile, Device Credentials, Series, OS, and OS Version. Provides overall network distribution in table and chart formats for the selected configuration. Supports asset tags, custom filters, MSP-based visibility, scheduling, sorting, and export options.

    Operational Data Report

    View Operational Data Report

    Summarizes operational command execution data for devices. Provides details such as Asset ID, Asset Name, IP Address, Hostname, Vendor, Serial Number, Command, and Result. Includes a sidebar view for detailed command results. Supports custom filters, Top limit, scheduling, and export options.

    Patch Compliance Report

    View Patch Compliance Report

    Summarizes device patch and OS compliance details, including Asset ID, IP Address, Hostname, Vendor, Model, Serial Number, Current OS Version, Latest OS Version, End of Support, End of Life, Vulnerabilities, and Compliance Status. Includes vulnerability advisory details such as Advisory ID, CVSS Score, and Resolution Status. Supports timescale filtering, custom filters, scheduling, and export options.

    Policy Associated Devices Report

    View devices associated with policies

    Displays devices associated with selected policies along with assigned rule information. Shows IP address, hostname, vendor, model, assigned policies, service status, asset state, and operational status. Supports asset tags, custom filters, column selection, sorting, top configuration, MSP visibility, scheduling, and export options.

    Policy Audit Report

    View Policy Audit Details

    Displays policy-level audit logs generated for configuration and compliance-related activities. Includes Timestamp, Client IP, User Name, Audit Category, and Message. Supports add, edit, clone, delete, preview, export, custom filters, sorting, Top limit, and scheduling.

    Policy Compliance Device Report

    View policy compliance per device

    Displays policy and rule compliance details per IP address/device. Shows policy name, rule group, rule status, and compliance metrics for each device. Supports asset tags, custom filters, sorting, Top limit configuration, MSP visibility, scheduling, and export options.

    Policy Comply Devices Report

    View Policy Comply Devices Report

    Displays devices that comply with assigned configuration policies. Provides detailed device information, including Asset details, Category, Location, State, and associated tags. Supports asset tags and custom filters, column configuration, Top limit, resolution, business-hour filtering, scheduling, and export options.

    Policy Detailed Report

    View detailed policy execution results

    Provides comprehensive policy execution results categorized by policy, rule group, and rule, along with associated asset details. Includes execution time, rule type, configuration file, review task name, and configuration type. Supports filtering, chart/table views, sorting, scheduling, MSP visibility, and export options.

    Policy History Report

    View Policy History Details

    Displays historical policy compliance records for devices, including policy name, rule group, rule, rule type, configuration type, compliance status, and timestamp. Supports Asset Tags and custom filters, add/edit/clone/delete, preview, export (CSV, XLSX, PDF), scheduling, sorting, and Top limit.

    Policy Not Associated Devices Report

    View Policy Not Associated Devices Report

    Displays devices that are not associated with any configuration policy. Provides asset-level information, including Asset ID, Asset Name, Alias, Category, Location, Status, and related attributes. Supports asset tag filtering, custom filters, column selection, Top limit, scheduling, and export options.

    Policy Summary Report

    View policy execution summary

    Displays a summarized view of policy execution status across devices. Includes a pie chart visualization and tabular summary of total devices, configured devices, and non-configured devices. Supports tags, custom filters, column selection, sorting, resolution, business-hour filtering, MSP visibility, scheduling, and export options.

    Policy Violation Devices Report

    View Policy Violation Devices Report

    Displays devices that have violated assigned configuration policies. Provides device-level details, including Asset ID, Asset Name, IP Address, Hostname, Vendor, Model, Status, Service Status, and related policy information. Supports asset tag filtering, custom filters, column selection, Top limit, sorting, scheduling, and export options.

    Recent Change Report

    View Report Details

    Displays the most recent configuration changes made to devices.

    Security Audit Report

    View Report Details

    Displays security-related audit activities and changes.

    Unauthorized Change Report

    View Unauthorized Configuration Changes

    Displays configuration differences that indicate unauthorized changes between the running and startup configurations. The report provides device details and configuration comparison results. Data is generated based on configuration download and comparison results within the selected timescale. Only valid and accessible assets are included.

    Unauthorized Changes Trend Graph

    View Unauthorized Changes Trend

    Displays a graphical representation of unauthorized configuration changes over the selected time range. Shows trend-based data (date/time vs change count) to help identify frequency and patterns of unauthorized changes across devices. Supports filtering by Vendor, Device Group, Asset Tags, Custom Filters, and Timescale, with export options (CSV, XLSX, PDF).

    Upload Job Approval Audit Report

    View Upload Job Approval Details

    Displays approval workflow details for upload jobs, including approval status, approver name, action time, execution time, and job result. If Next Action Time is unavailable, the last action time is used instead. Data is generated based on the upload job approval audit logs within the selected filters and timescale.

    Upload Job Audit Report

    View Upload Job Audit Details

    Displays upload job execution results for the selected time interval. Provides device-level details, including IP Address, Job Name, Task Status, Execution Time, Result Status, and Customer/Entity (MSP-based visibility). Data is generated based on upload job execution logs within the selected filters and timescale.

    Upload Job Command Summary Report

    View Report Details

    Provides a summary of commands executed as part of upload jobs.

    Upload Job Summary Report

    View Report Details

    Provides a summary of configuration upload jobs and their execution status.

    User Activity Report

    View Report Details

    Displays user activities performed within the system.

    Vulnerability Detailed Report

    View detailed vulnerability information

    Displays complete vulnerability-level details mapped to each device IP. Includes IP Address, Vendor, OS Type, Version, Series, Model, Vulnerability ID, Vulnerability Title, CVSS Score, Severity, Published Date, Identified Time, Resolved Status, Resolved By, Resolved Time, URL, Resolve Comments, Summary, End of Life, and End of Support. Supports custom filters, tag filtering, timescale selection, column configuration, scheduling, sorting, MSP visibility, and export options.

    Vulnerability Report

    View vulnerability overview

    Displays consolidated vulnerability details for managed devices under NCCM. Provides vulnerability-level information, including Vulnerability ID (CVE), Severity, CVSS Score, Published Date, Identified Time, Resolved Status, Resolved By, Resolved Time, Resolve Comments, and related device information. Supports default filters, resolution-based filtering, custom filters, scheduling, audit tracking, MSP visibility, and export options.

    Vulnerability Summary Report

    View Vulnerability Summary Details

    Displays vulnerable device details categorized by severity levels, including Critical, High, Medium, and Low. Provides summary and detailed vulnerability statistics for the selected time interval. Includes device-level details such as IP Address, Asset Name, Severity, CVSS Score, and Vulnerability Status. Supports custom filters, timescale selection, business-hour selection, Top limit, MSP-based visibility, scheduling, and export options.

    Displays the history of software license allocation over the selected period. Users can apply custom filters and select a timescale to view allocation data for a specific period. The report supports configurable columns and allows users to control the visibility of the report by making it private for selected users or teams or public for all users.

    Software by Publishers

    Click on the reports on the left panel and select software reports.

    Enable all columns in Software by Publish Reports. Gain detailed insights into respective assets, including application name, vendor, help link, and more. Filter by asset tag and custom criteria for comprehensive software tracking.

    Software Details Report

    Click on the reports on the left panel and select software reports.

    Access detailed reports for respective software in Software Detail Reports. Identify software status as 'Discovered' if found through the agent, or 'Managed' if manually added.

    Software Installation

    Users can select Software Installation Report, choose the required columns, and configure filters before previewing the report. They can group the report by Asset Name, Application Name, Application Type, or Application Vendor, with Software selected by default. Users can modify the grouping, generate the updated report, and save the configuration. The report can be sent immediately or scheduled, cloned, edited, or deleted, and exported in Excel, CSV, or PDF formats.

    Displays details of software installed on managed assets. The report provides information such as Asset Name, Application Vendor, and Application Version. Users can group the results based on different asset or application attributes to organize and analyze the installed software information. The report reflects the selected grouping and filter conditions when generated or exported.

    Software Installed vs Purchase Report

    Users can select Software Installed vs Purchased Report from the Software Reports category and apply optional custom filters before viewing the report. They can save, edit, clone, or delete the report and generate the report to view the software installation and purchase counts. Users can also schedule the report or send it to selected email addresses.

    Displays a comparison between software purchased and software installed. The report provides details such as Software Name, Software Version, Total Purchased, Managed Installations, Remaining, and Compliance Status. The report helps users compare purchased licenses with managed installations and identify the remaining licenses and compliance status. The report is available for software subscribers/license users.

    Software License Summary

    Users can configure this report by selecting required columns, applying custom filters, choosing a Timescale Column (Effective From, AMC Start Date, AMC Expiry Date, End Date, Invoice Date), and defining a Timescale.

    Displays software license details based on the selected configuration. The report includes fields such as License Name and Description (available by default), as well as selectable columns such as Free (available licenses) and Allocated (assigned licenses). Users can filter data using custom conditions and time-based criteria. The report supports preview before saving and allows export in Excel, CSV, and PDF formats. It helps track license usage, availability, and lifecycle based on selected time filters.

    Software Metering Report

    Users can select Software Metering Report, choose the required columns, and configure the Applicable Devices using Asset Tags. They can link related reports using Link Reports and select a date range using Timescale. The report can then be generated based on the selected columns, devices, linked reports, and time period.

    Displays software metering information based on the configured metering rules and applicable devices. Users can select the required report columns, filter the report based on Asset Tags, link related reports, and specify a date range to view the required metering information.

    Show Top

    You can select the top 5 or 10 to see only the top 5 or 10 reports.

    Search

    You can search for the desired column using the search tab.

    Select all

    Enabling it will select all the columns provided in the configuration section.

    Asset Scope

    Allows you to select the asset scope to include Active, Deleted, or Archived assets in the report. The asset scope option is only available in Asset Report.

    Data Masking

    Allows sensitive asset information to be masked, including IP Address, Host Name, Serial Number, MAC Address, and License Key. The data masking option is only available in Asset Report.

    Resolution

    You can select the resolution duration in minutes, hours, days, or months. Note: The resolution option is only available in Availability Report.

    Module Name

    Allows you to select the ITSM module such as Incident, Change, or Request for which the report data should be generated. The Module Name option is only available for SLA Report.

    SLA Profile

    Allows you to select the SLA Profile used for evaluating SLA. This option is only available for SLA Report, Asset SLA Request Report, Configure SLA Penalty Report, Incident SLA Compliance Report, and Ticket SLA Dataset Compliance.

    Metric

    Allows you to select the SLA metric used for evaluating the report data. The available metrics depend on the selected SLA Profile. This option is only available for SLA Report, Asset SLA Request Report, Configurable SLA Penalty Report, Incident SLA Compliance Report, and Ticket SLA Dataset Compliance.

    Penalty

    A toggle that enables or disables penalty calculation. When enabled, the Penalty Configuration option is displayed. This option is only available for SLA Report, Asset SLA Request Report, Configurable SLA Penalty Report, Incident SLA Compliance Report, and Ticket SLA Dataset Compliance.

    Penalty Configuration

    Allows you to select the configuration used to calculate penalties. This option is available for SLA Report, Asset SLA Request Report, Configurable SLA Penalty Report, Incident SLA Compliance Report, and Ticket SLA Dataset Compliance.

    Custom Columns

    Allows you to select additional custom fields to be displayed in the report. This option is only available for SLA Report and Asset SLA Request Report.

    Resource Only

    Allows you to restrict the report data to resource-level information. This option is only available for Asset SLA Request Report.

    Penalty Rules

    Allows you to configure the rules used to determine penalty calculations based on specified conditions. This option is only available for Configurable SLA Penalty.

    Add Rule

    Allows you to add a new penalty rule to the report configuration. This option is only available for Configurable SLA Penalty.

    Impact Service

    Allows you to specify the Impact Service to which the penalty rule applies. This option is only available for Configurable SLA Penalty.

    Match Conditions

    Allows you to select the condition type used to trigger a penalty rule, such as Penalty Multiplier, Fixed Downtime, or Metric Threshold. This option is only available for Configurable SLA Penalty.

    Define Conditions

    Allows you to specify the condition or threshold under which the configured penalty rule is applied. This option is only available for Configurable SLA Penalty.

    Enable

    Allows you to enable or disable the configured penalty rule or option. This option is only available for Configurable SLA Penalty.

    Business Hours

    Allows penalty calculations to be restricted to the configured business hours. This option is only available for Configurable SLA Penalty.

    24-hour cap

    Limits the applicable downtime calculation within a 24-hour period when processing a penalty rule. This option is only available for Configurable SLA Penalty.

    Group Datasets by

    Allows you to determine how report data is divided into separate datasets for reporting. This option is only available for Ticket SLA Dataset Compliance.

    Daily Recharge (Rs)

    Allows you to specify the daily recharge amount used for calculating the applicable penalty. This option is only available for Asset Delivery Penalty Report.

    Penalty Computation Basis

    Allows you to specify the basis used to calculate the penalty amount. This option is only available for Asset Delivery Penalty Report.

    Select the incident tags that you want to see on your report. Note: This option is only available in Incident Report and Incident Summary Report.

    Assignee

    Select the assignee name to whom you want to send the report. Note: This option is only available in Incident Report and Incident Summary Report.

    Create a Custom Filter

    Create a custom filter by selecting a category, condition, and value to refine the report data based on specific requirements.

    Change Tag

    Select the change tags that you want to include in the report. Note: This option is only available in Change Report and Change Summary Report.

    Use Applicable Devices to define the devices or records included in the report. You can select tags based on the report module. Example: For an Incident Report, select Incident Tag to include only incidents associated with the selected tags. Similarly, use Request Tag, Problem Tag, Change Tag, or Release Tag for their respective report types. If no Asset Tags are selected for a report where this filter is optional, the report can still be generated and may display the complete or unfiltered results.

    Asset Tags

    Select the required asset tags.

    Filters the report based on the selected asset tags.

    Incident Tag

    Select the required incident tags.

    Filters the report based on tags assigned to incidents.

    Change Tag

    Select the required change tags.

    Filters the report based on tags assigned to changes.

    Custom filters

    Click to create or configure custom filter conditions.

    Allows you to define advanced conditions to control which records are included in the report.

    Link Reports

    Select the required reports from the available reports.

    Allows related reports to be associated with the current report.

    Select Active as the Asset Scope.

    The report includes assets that are currently active.

    SLA Profile*

    Select the required SLA profile.

    Defines the SLA profile to be used for generating the report.

    Metric

    Select the required metric.

    Specifies the SLA metric used for the report. Example: Gold.

    Timescale

    Select the required time period.

    Defines the period for which the SLA data is generated. Example: Current Month.

    Penalty Configuration

    Select the required penalty configuration.

    Specifies the penalty configuration applied to the SLA report. Example: Test Incident Penalty.

    Resource Only

    Enable or disable the option.

    Restricts the report to resource-related SLA data when enabled.

    Group By

    Select the field by which the report data should be grouped.

    Groups the generated report data based on the selected field. Example: Team.

    Timescale

    Select the required reporting period.

    Defines the time period for which the report data is generated. Example: Current Month.

    Forecast Data

    Select the forecast period.

    Defines the future period for which forecast data is included in the report. Example: Next 60 Days.

    Limit

    Select the required result limit.

    Specifies the number or category of results to be included in the report. Example: Top.

    Threshold

    Configure the threshold value or condition.

    Defines the threshold used when evaluating or presenting report data.

    Percentile

    Configure the percentile value.

    Specifies the percentile used for the report calculation or threshold evaluation.

    Unit Scale

    Select the required unit scale.

    Defines the unit scale used to represent the report values. Example: Default.

    Chart Type

    Select the required chart type.

    Defines how the report data is visually represented.

    Resolution

    Select the required resolution.

    Defines the level of detail or granularity used when displaying the chart data.

    Split By

    Select the field by which the chart data should be divided.

    Splits the displayed data based on the selected field.

    Timescale

    Select the required time period.

    Defines the period for which the chart data is generated. Example: Last 60 Mins.

    Financial Year Start

    Select the month in which the financial year begins.

    April means the financial year is calculated from April.

    Limit

    Select the required result limit.

    Specifies the number of results displayed in the report. Example: Top 5.

    Poll Points

    Enter the required number of poll points.

    Defines the number of polling points considered when generating the report data.

    Show Stack Module

    Enable or disable the toggle.

    Controls whether stack module information is displayed in the report.

    Mask: Obfuscates the requester's name in reports to protect personal information and comply with data privacy requirements.

    Unmask: Displays the requester's name without masking for authorized access.

    Contact

    Enable or disable the toggle under Mask or Unmask.

    Mask: Obfuscates the requester's contact information in reports. Unmask: Displays the requester's contact information without masking for authorized access.

    Email

    Enable or disable the toggle under Mask or Unmask.

    Mask: Obfuscates the requester's email address in reports.

    Unmask: Displays the requester's email address without masking for authorized access.

    Save

    Click Save to apply the selected privacy settings.

    Saves the masking and unmasking preferences configured for requester name, contact information, and email address.

    A private report is restricted and not available as a public report.

    Select Private to restrict the report to specific users or teams.

    When Private is selected, the Assignee section opens.

    Assignee

    Select User/Teams for private.

    The Assignee section allows you to select the users or teams who can access the private report.

    Users

    Select one or more users from the list.

    Displays the available users who can be assigned access to the private report. Each user displays their name and email address. Selects the user to whom the private report is assigned.

    Teams

    Select one or more teams from the list.

    Displays the available teams that can be assigned access to the private report. Selects the team to whom the private report is assigned.

    Cancel

    Click Cancel.

    Closes the Assignee section without applying the selection.

    Submit

    Click Submit.

    Applies the selected users or teams to the private report.

    Available formats shown in the Schedule panel are PDF, XLSX, and CSV.

    Active

    Enable or disable the toggle.

    Enables or disables the configured report schedule.

    Schedule Mode

    Select the required scheduling frequency.

    Available options include Once, Every, Daily, Weekly, and Monthly.

    Date and Time

    Specify when the report should be generated.

    Example: 6 October 2026, 12:00 PM.

    Email – To

    Enter the recipient email address.

    Specifies where the scheduled report should be sent.

    Email – Subject

    Enter the email subject.

    Defines the subject of the email containing the scheduled report.

    Email Body

    Enter the message to be included in the email.

    Allows you to provide additional information along with the scheduled report.

    Update Schedule

    Click Update Schedule to save the schedule.

    Saves the selected report format, schedule frequency, date/time, and email details.

    Submit

    Click Submit after completing the report configuration.

    Saves the report configuration. After the report is created, it can be accessed from the Reports page and generated when required.

    Infraon Requester Portal

    CLI Jobs

    CLI Jobs/sessions in NCCM create direct CLI sessions (SSH or TELNET) between the Device and the User through the NCCM application. Using a CLI Job, the user can write direct commands on devices similar to the Putty application.

    to access the detailed CLI Jobs content and manage your network jobs effectively.

    Click here

    Add a Dashboard

    Instructions to 'Add Dashboard'

    To add a new dashboard:

    • Navigate to the Dashboard module.

    • Expand the left panel by clicking the right arrow key.

    • Click the plus (+) icon to create a new dashboard.

    • Provide a name (this name will represent and help identify the dashboard) for the dashboard and click Create.

    Once created, the next step is configuring Widgets, which dynamically display data from various modules in graphical or tabular formats.

    Infraon widgets are pre-built components designed to pull key insights from your infrastructure, ITSM modules, and network data, and display them in clear, interactive formats such as:

    Widgets are grouped into multiple categories, such as Assets, Statistics, Events, Views, ITSM, NCCM, and System ensuring complete coverage across IT operations and business service management.

    The Assets category provides insights into IT and Fixed Assets, including inventory distribution, purchases, license usage, consumables, and vendor information. IT teams can track asset lifecycles, utilization, and financial impact.

    The Statistics category helps monitor performance metrics, availability, trends, and resource utilization. It is crucial for proactive oversight and SLA reporting.

    The Events category provides a breakdown of all system events and alarms, helping teams prioritize incidents by severity and track event history over time.

    The Views category provides device-level status and network visualizations, enabling topology-based monitoring and drill-downs.

    The ITSM category consolidates ticketing, request, change, release, and problem metrics in one location. It allows support teams to track SLA compliance, workload, and turnaround times.

    Count Summary Widget

    The Count Summary widgets offer high-level aggregation and drill-down capabilities for the Ticket, Request, Problem, Change, and Release modules. These widgets support flexible data grouping and multiple drill-down levels, empowering users to visualize and analyze operational metrics with greater depth.

    The NCCM category provides insights into configuration backups, baseline comparisons, vulnerabilities, and policy compliance for network devices.

    The System category monitors platform/system health for proactive troubleshooting.

    Select the widget you want to configure, then set up its parameters.

    While each widget serves a predefined purpose (e.g., asset tracking, ticket monitoring, event summaries), they can be fully customized by applying filters, selecting specific time ranges, or adjusting visual elements such as color schemes.

    The Configuration tab allows you to define how a widget should display information. Different configuration fields will appear depending on the widget category and chart type selected. The table below combines all available fields across different widget types for reference.

    The Filter tab allows you to refine and narrow widget data by applying specific filters. Instead of displaying all available information, you can limit the results to focus on relevant data points (e.g., filtering tickets by priority or assets by tags).

    Click on Add to finalize your configuration and add the widget to the dashboard.

    You can perform the following actions while editing a dashboard:

    Edit Dashboard | Add Dashboard

    Click on Submit to save and apply the changes to your dashboard.

    The Global Filters section in the Edit Dashboard page is used to configure dashboard-level filters that dynamically apply across all configured widgets. These filters help users narrow down dashboard data by selected criteria, such as infrastructure, assets, locations, and ITSM-specific parameters.

    Users can configure:

    • Standard Global Filters

    • Date Filters

    • ITSM Global Filters

    Configurations | Global Filters

    Label
    Action
    Description / Example

    Ticket and Request dashboard widgets support custom field-based filtering and grouping, enabling users to analyze data using workflow-specific attributes. Supported custom fields of type Dropdown, Checkbox, and Radio Button can be used in both Filter and Group By configurations for supported summary widgets.

    Custom field support is available in the following widgets:

    • Incident Summary

    • Total Incident Count

    • Incident SLA Compliance By Templates

    • Incident Response Time Count

    While configuring a supported widget, users can navigate to the Filter section to apply custom field-based filters and use the Group By option to group widget data based on selected custom field values.

    The Group By dropdown displays both default fields and supported custom fields (Dropdown, Checkbox, and Radio Button) for the selected module.

    For the Count Summary widget, Group By values update dynamically based on the selected module. When users switch between modules such as Incident and Request, the available custom fields are refreshed, and users must reselect the required Group By field.

    If multiple workflows contain custom fields with the same name, the workflow name is automatically appended to the field name to avoid duplication and help users identify the correct field when selecting a filter or Group By.

    Nested Grouping allows users to analyze Summary widgets data across multiple hierarchical levels within a dashboard widget. It helps organize asset data in a structured, expandable format for deeper visibility into asset distribution and categorization.

    This feature is available in the Summary widgets and supports up to 4 levels of grouping.

    • Navigate to Dashboard → Edit Dashboard.

    • Select the Asset Summary widget.

    • Go to the Configuration tab.

    • Enable the Nested Grouping toggle.

    Nested Grouping | Configuration

    Label
    Action
    Description / Example

    Grouping Structures | Example

    Purpose
    Example

    After saving the widget configuration, the Asset Summary widget displays data in a hierarchical tabular structure within the dashboard.

    Users can expand grouped levels, view grouped asset counts, open sidebar asset details, export data, and edit the existing widget configuration.

    Bar Chart

    Shows comparative metrics in horizontal/vertical bar form.

    Example: Tickets by Priority, License Usage.

    Area Chart

    Highlights cumulative growth or changes over time with shaded areas.

    Example: Static Trend of Tickets.

    Gauge Chart

    Displays progress against a target or threshold (like a speedometer).

    Example: SLA Compliance Rate.

    Sunburst Chart

    Provides hierarchical data in concentric circles for drill-down insights.

    Example: Business Service Summary.

    Data Panel

    Asset Count Panel

    Data Panel

    License Usage

    Bar Chart, Data Table

    True-up Cost

    Data Panel

    Top Publishers

    Bar Chart, Data Table

    Consumable Summary

    Data Panel

    Location-Wise Asset Summary

    Bar Chart, Data Table

    Agent Status

    Data Panel

    Asset Location Drilldown Table

    Data Table

    Asset Location Drilldown Summary

    Data Panel

    Asset Aging Summary

    Bar Chart, Data Panel

    Agent Count

    Displays agent counts in a panel view with Total, Active, and Inactive agents. When the Creation Time filter is applied, all counts are shown. When the Down Since filter is applied, only the inactive agent count for the selected time range is displayed. View: Data Panel

    Area Chart, Data Table, Bar Chart

    Resource Trend

    Line Chart

    Resource Status Panel

    Data Panel

    Statistic Panel

    Data Panel, Gauge Chart

    Node Status Panel

    Data Panel

    Link Status Panel

    Data Panel

    Node Availability Summary

    Data Table

    Critical Device Summary

    Data Panel

    Branch Availability Summary

    Data Table

    Service Provider Index

    Data Panel

    ISP Link Availability Summary

    Data Table

    Device Type Availability Summary

    Data Table

    Network Performance Index

    Data Panel

    Node Summary

    Data Panel

    Link Summary

    Data Panel

    Wireless Controller

    Data Panel

    Aging Summary

    Data Table

    Node Aging Summary

    Data Table

    Link Aging Summary

    Data Table

    Event Aging

    Data Panel

    Branch Summary

    Data Panel

    Branch Details

    Data Panel

    Branch Availability

    Data Panel

    Device Status

    Data Panel

    Change Count

    Data Panel

    Change Created Vs Closed

    Pie Chart, Bar Chart, Area Chart, Line Chart

    Assignee Summary

    Displays a summary of requests grouped by assignee, with options to filter by module, timescale, and technician. Users can view counts per assignee, open a detailed Change list in a slider with pagination, and manage the widget (add, clone, edit, delete).

    The Filter tab allows you to apply custom filters, including Priority, Status, Team, Service Catalog, Department, and Location. Multiple filters can be applied together, and the widget displays only matching data. Validation ensures that required values are entered and that filters are retained during editing and cloning.

    Example: Monitor requests assigned to technicians, filtered for High priority and Open status. View: Data Table.

    My Activity

    Data Table

    Enables filtering and grouping data by the chosen attribute for focused monitoring.

    Drill-Down Level 1

    Select an option from the group by fields and the widget view

    First-level drill-down using the chosen field, showing a quick breakdown (e.g., open/closed status).

    Drill-Down Level 2

    Add secondary grouping and view option.

    Allows further segmentation of data (e.g., breakdown by priority within status) and supports multiple levels for deep analysis.

    Timescale

    Choose time period (e.g., current week)

    Filters widget data by the selected timescale, aiding trend analysis.

    Auto Reload

    Set refresh interval

    Ensures summary data is updated automatically at specified intervals.

    Chart Type

    Select a data panel, a pie chart, a bar chart, or a data table

    Provides various visualization options for presenting summary and drill-down data.

    Recent Downloads

    Data Table

    Baseline Vs Running

    Data Panel

    Baseline Vs Startup

    Data Panel

    Previous Vs Running

    Data Panel

    Previous Vs Startup

    Data Panel

    Startup Vs Running

    Data Panel

    Vendor Summary

    Data Panel

    Download Summary

    Pie Chart, Data Table

    Vulnerable Nodes

    Data Panel

    Top Vulnerable Nodes

    Data Panel

    Recent Authorized Changes

    Data Panel

    Recent Unauthorized Changes

    Data Panel

    Unauthorized Change Count

    Data Panel

    Policy Alarms

    Pie Chart, Bar Chart, Line Chart, Data Panel, Data Table

    Policy Failed Nodes

    Data Panel

    Policy Not Associated

    Data Panel

    Policy Violated Nodes Summary

    Data Table

    Policy Status Summary

    Data Table

    Recent Unauthorized Changes

    Displays the most recent configuration changes that are identified as unauthorized during configuration comparison. The widget retrieves data from download job audits whose authorization checks returned unauthorized results.

    Users can click View to open a side panel that displays configuration comparison details, including time, version, configuration type (running/startup), download time, and hostname. Options are available to view only differences or the full configuration and export the comparison as a PDF. Filters such as Timescale, MSP filter, and custom filters (for example, Vendor and IP Address) are supported.

    View: Data Panel

    Recent Authorized Changes

    Displays the most recent configuration changes that are identified as authorized during configuration comparison. The widget shows the download job audit results for the authorization check, which is successful.

    Users can click View to open a comparison panel that displays details such as time, version, configuration type, download time, and hostname. The widget supports viewing differences, full configuration comparison, PDF export, Timescale selection, MSP-based filtering, and additional custom filters.

    Auto-reload configuration is supported as per the widget settings.

    View: Data Panel

    Backup Failed

    Displays the count and details of devices where the configuration download (backup) has failed during execution. Data is derived from configuration download job results within the selected timescale.

    Supports filtering using Timescale, MSP (Customer/Entity), and custom filters (for example, Vendor, IP Address, Tag, Entity). The widget supports auto-reload based on configuration.

    Used to monitor failed backup attempts and quickly identify affected assets requiring re-execution or troubleshooting.

    View: Data Panel

    Backup Success

    Displays the count and details of devices where the configuration download (backup) has completed successfully. Data is retrieved from successful download job audit results within the selected timescale.

    Supports Timescale, MSP (Customer/Entity) filtering, custom filters, and auto-reload configuration. Custom entity field (Customer/Entity) visibility follows MSP configuration rules.

    Used to validate successful configuration backup operations and monitor compliance with backup schedules.

    View: Data Panel

    Policy Severity Status

    Displays policy compliance results categorized by severity level (Critical, Major, Minor, Comply/Success) for each policy. Provides an overview of the severity distribution across devices based on policy evaluation results.

    Supports chart type selection, resizing, auto-reload, tag filtering, assignee filtering, MSP visibility, and custom filtering. Data visibility is role-based (Admin, Non-Admin, MSP).

    Used to monitor policy compliance posture and identify high-severity violations across managed devices.

    View: Chart Panel

    Policy Status

    Displays the overall status of each policy based on evaluation results. Shows policy name, status, device count, and rule severity distribution.

    Users can click on policy names to navigate to the Policy module. Clicking the device count opens a side panel with the associated device list and export option (CSV). Supports Timescale, custom filters, MSP filtering, chart type selection, and auto-reload.

    Used to analyze policy-level compliance and device distribution under each policy.

    View: Data Panel

    Policy Violated Node Summary

    Displays a summary of devices (nodes/assets) where policy violations are detected. Shows Hostname/IP Address, Policy Count, and associated rule severity details.

    Clicking IP/Hostname redirects to the respective IT-Asset view page. Supports Timescale, tag, assignee, custom filters, MSP visibility, resizing, and auto-reload configuration.

    Used to identify affected assets and drill down into violation details for remediation.

    View: Data Panel

    Policy Status Pie

    Displays a pie chart showing the distribution of policy status (e.g., Comply vs Non-Comply or Configured vs Not Configured) based on policy evaluation results.

    Users can apply Timescale, Custom, and MSP filters to refine data. Clicking on a pie segment opens a count grid showing the list of devices for the selected status.

    Visibility depends on user role and MSP scope.

    View: Pie Chart

    Policy Configured Summary

    Displays a summary pie chart showing the number of policies configured versus not configured across devices. Data updates based on selected Timescale, Custom filters, and MSP filters.

    Clicking on a pie segment opens a grid view displaying the list of devices corresponding to the selected status.

    Visibility is determined by user role and MSP-level access control.

    View: Pie Chart

    Download Summary

    Displays the summary of configuration download job statuses within the selected timescale. The widget shows the total count of download jobs grouped by status, such as Download Success, PING Failed, Device Access Denied, Invalid Commands, and other failure categories.

    Users can configure Title, Timescale, Auto Reload, and Chart Type (Pie / Table). Custom filters and MSP-based filters are supported when enabled.

    View: Pie Chart and Data Table.

    Top Vulnerable Nodes

    Displays the top Node devices with the highest vulnerability count based on the selected timescale. The widget shows Hostname, IP Address, Vendor, and Vulnerability Count.

    Users can configure Title, Top Count, Timescale, and Auto Reload. Custom filters and MSP filters are supported when enabled. Supports CSV export of displayed data.

    View: Data Table.

    Vulnerable Nodes

    Displays the list of devices with detected vulnerabilities within the selected timescale. The widget shows device-level vulnerability details based on applied filters.

    Supports Title, Timescale, and Auto Reload configuration. Custom and MSP filters are supported when enabled. Supports CSV export of vulnerability data.

    View: Data Table.

    Policy Failed Nodes

    Displays the count of nodes with failed policy compliance based on the selected timescale. The widget shows only the numeric count of failed nodes.

    Users can configure Title Style, Font Color, Background Color, Timescale, and Auto Reload. Custom filters and MSP filters are supported when enabled.

    View: Data Table.

    Policy Alarms

    Displays policy compliance status grouped by severity: Critical, Major, Minor, and Comply. Clicking on Pie/Bar segments or Table counts opens the filtered device grid. A line chart does not support on-click actions.

    Users can configure Title, Timescale, Auto Reload, and Chart Type. Custom and MSP filters are supported when enabled.

    View: Data Panel, Pie Chart, Bar Chart, and Data Table.

    Policy Not Associated

    Displays the count of devices that do not have any policy associated with the selected timescale. Supports configuration of Title, Title Style, Font Color, Background Color, Timescale, and Auto Reload. Custom filters and MSP filters are supported when enabled.

    View: Data Panel.

    Choose how data is grouped (e.g., Device Type, Day, Assignee, Requester). Determines the primary categorization for the widget.

    Type*

    Dropdown

    Select the data type or event type relevant to the widget.

    Example: Active Events, Closed Tickets.

    Top*

    Dropdown

    Define how many top results to display.

    Example: Top 10 Assets by Value.

    Drill-Down (Add Level)

    Add additional field levels

    Let's users add hierarchical drill-downs for deeper analysis.

    Example: Group by Device Type → Location → Vendor.

    Timescale*

    Dropdown

    Select the time range for data visualization.

    Options: Last Hour, Current Day, Current Week, Current Month, etc.

    Auto Reload*

    Dropdown

    Set automatic refresh intervals for the widget.

    Example: 5 mins, 15 mins, 30 mins, 1 hour, etc.

    Chart Type

    Icon selector

    Choose the display format. The available types are Panel View, Data Table, Line Chart, Bar Chart, Area Chart, Gauge Chart, Sunburst Chart, and Pie Chart.

    Cross Launch URL

    Input field

    Provide a URL that can be cross-linked for detailed analysis or drill-through.

    Example: Linking a Ticket Summary widget to the Ticket Management module.

    Color Palette

    Selector

    Choose a predefined color scheme for graphs and charts. Helpful in aligning with brand or theme.

    Show All

    Toggle (On/Off)

    Option to display all available results instead of a limited set.

    Example: Show all services in Business Service Summary.

    Filter resources (users, services, or configurations) by tags.

    Example: Cloud Resource, Database Server, API Service, etc.

    Assignee

    Select from the dropdown

    Restrict (ticket, etc.) data to a particular assignee. Helpful in tracking workload distribution.

    Custom Filters

    Add field-value pair

    Filters are visible based on selected preferences. Different filters are available on the Infraon platform, which can be applied to a widget to filter data displayed in the Dashboard.

    Here is the list of custom filters depending on the field :

    • Asset ID

    • IP Address

    • Device Type

    Field

    Select field type

    Choose the attribute to filter on.

    Example: Location, Department, Priority, etc.

    Value

    Select the corresponding value

    Define the actual filter criteria.

    Example: Critical, High, Medium, Low.

    Add Filter

    Click to add a new row.

    Add multiple filters for complex queries.

    Add new widgets using the same configuration and filter process described earlier.

    Assignee

    Click Assignee on the top bar.

    Assign the dashboard to a specific User or a Team. Select from the pop-up list (e.g., Approval Team, Change Team).

    Global Filter

    Click Global Filter on the top bar

    Apply overall filters to the dashboard:

    • Global Filter: Toggle on/off. Add filters such as Location, Department, and Make to refine dashboard and widget data.

    • Date Filter: Enable/disable to view data within a selected time range.

    Resize Widgets

    Click and drag the widget’s edges

    Increase or decrease widget size to fit the dashboard layout.

    Reposition Widgets

    Double-click and drag a widget

    Move the widget’s position anywhere on the dashboard canvas.

    Disable Date Filter

    Enable or disable the date filter option.

    Displays the date range filter on the dashboard view page to filter widget data by the selected time duration.

    Disable ITSM Global Filter

    Enable or disable ITSM-specific global filter configuration.

    When enabled, users can configure ITSM-based filters for dashboard widgets.

    ITSM Global Filter

    Select one or more ITSM filter types from the dropdown list.

    Supported Options include: Impact Service, Catalog, Category, Sub-Category, Priority, Location, Team, Workflow, and Source.

    Incident Aging
  • Incident Created vs Resolved

  • Incident Aging Summary

  • In SLA - Out SLA Incidents

  • Average Turnaround Time – Incidents

  • Incident Aging Summary Timebar

  • Incident SLA Aging Summary

  • Count Summary

  • Ticket Summary

  • Request Summary

  • Select required fields under Levels.

  • Add additional levels if required.

  • Click Apply Changes to preview.

  • Click Add and then Submit to save the dashboard.

  • Add Level

    Click to add a grouping level

    Adds additional grouping levels for deeper asset categorization. Supports up to 4 levels.

    Delete Level

    Click the delete icon

    Removes the selected grouping level from the hierarchy configuration.

    Level Sequence

    Arrange selected fields

    Determines how asset data is grouped in the widget. The first field becomes the parent level, followed by child levels.

    Apply changes to preview

    Click to generate preview

    Displays widget data in a hierarchical structure based on the selected grouping levels before saving.

    Auto Reload

    Select refresh interval

    Automatically refreshes widget data based on the selected interval without changing the grouping configuration.

    Department Asset Analysis

    Department → User → Status

    Chart Type

    Description / Example

    Data Panel

    Displays high-level KPIs or summary metrics in a compact panel format.

    Example: Total Tickets Today, Total Active Assets.

    Data Table

    Presents detailed data in a structured table with sorting, filtering, and drill-down options.

    Example: Asset Location Drilldown Table.

    Line Chart

    Widget

    View

    Resource Count Summary

    Pie Chart, Data Panel, Bar Chart

    New Purchases

    Data Panel

    Widget

    View

    Stat Summary

    Pie Chart, Data Table, Bar Chart

    Multistat Summary

    Pie Chart, Data Table, Bar Chart

    Widget

    View

    Event Summary

    Bar Chart, Pie Chart, Line Chart, Data Panel, Data Table

    Event Count

    Data Panel

    Event Trend

    Widget

    View

    Text/URL Panel

    Data Panel

    Topology View

    Data Panel

    Geo Map Drilldown Summary

    Widget

    View

    Count Summary

    Data Table

    Count Summary Timebar

    Data Table

    Change Summary

    Label

    Action

    Description

    Widget Name

    Select module (Ticket, Request, Problem, Change, Release Summary)

    Displays the summary count based on the chosen ITSM category, auto-refreshes for a real-time view.

    Group By

    Widget

    View

    Backup Success

    Data Panel

    Backup Failed

    Data Panel

    Widget

    View

    System Health Summary

    Data Panel

    Label

    Action

    Description / Example

    Title*

    Enter text

    A mandatory field is needed to provide a unique name for the widget.

    Example: Asset Summary, Ticket Trend.

    Group By*

    Label

    Action

    Description / Example

    Asset Tags

    Select from the dropdown or search.

    Filter assets by pre-defined tags.

    Example: Critical Devices, Production Servers, etc.

    Resource Tags

    Label

    Action

    Description / Example

    Edit Name

    Click the pencil icon beside the dashboard name.

    Rename the dashboard as per your requirement.

    Example: “Organization Summary” → “Team SLA Dashboard”.

    Add Widget(s)

    Disable Global Filter

    Enable or disable the standard global filter configuration.

    When enabled, users can configure dashboard-level global filters.

    Global Filters

    Select one or more filter types from the dropdown list.

    Nested Grouping

    Enable or disable toggle

    Activates hierarchical grouping for the widget. When enabled, Drill-Down is disabled, and multiple grouping levels can be configured.

    Levels

    Select one or more fields

    Asset Distribution by Location

    Location → Department → Device Type

    Asset Status Review

    Status → Device Type → Model

    Hardware Categorization

    Widget

    Assets

    Statistics

    Events

    Views

    ITSM

    Event and Summary Filters in Ticket Dashboard Widgets

    The Event and Summary fields are available as custom filters in dashboard widgets to further refine ticket data displayed in widgets such as Ticket Summary, Ticket Assignment Summary, Aging Summary, Count, and Created vs Closed.

    These filters allow users to narrow widget data by text-matching ticket summaries or event types across the Incident, Problem, Change, and Request modules.

    Supported operators:

    • Event: in, contains, not in

    • Summary: in, contains, not in

    When applied, the widget refreshes to display only records that match the configured filter criteria.

    Note: Service Category is available in the custom filter for ITSM widgets. Selecting one or more categories filters the widget data accordingly.

    Note:

    • The Summary and Event fields appear in the filter field dropdown when adding a custom filter.

    • The contains operator allows partial text matching (for example, filtering all tickets with the word server in the summary).

    • Filters cannot be applied without entering a value. If the value field is left empty, a validation message is displayed, and the filter is not applied.

    • Clearing the custom filter restores the widget to display all applicable records.

    NCCM

    System

    Configuration Details | Add Dashboard

    • Fields marked with * are mandatory.

    • Not all fields appear for every widget; they vary based on category and chart type.

    • Widgets can be previewed by clicking Apply changes to preview before saving.

    Filter Details | Add Dashboard

    • Filters vary depending on the widget category.

    • Multiple filters can be applied together for granular results.

    • Use Apply changes to preview to validate filtered results before saving the widget.

    Edit Dashboard

    Global Filters

    Custom Fields

    How does it work

    Example:

    If a workflow includes a custom field named Business Service, users can use it as a filter when configuring the Incident Summary or Incident Aging widget to display ticket data only for the selected business service.

    If the same custom field exists in multiple workflows, the filter displays entries such as:

    • Business Service – IT Workflow

    • Business Service – Network Workflow

    Nested Grouping

    How does it work?

    View Widget

    Visualizes trends over time with a line graph. Ideal for SLA breaches or request resolution trends.

    AMC Expiry

    Static Trend

    Bar Chart, Line Chart, Pie Chart, Area Chart

    Data Panel

    Pie Chart, Bar Chart, Data Panel, Data Table

    Choose grouping field (State, Status, Urgency, Priority, Severity, Release Type, Impact Service)

    Dropdown

    Select from the dropdown or search.

    Click Add Widget(s) on the top bar

    Supported options include: Location, State, City, Device Type, Make, Model, Branch, Branch Code, Asset Tags, Asset Custom Fields, Resource Tags, Resource Custom Fields, Link Name, Link Mode, ISP Name, Region, and PO Number.

    Used to define the hierarchy of asset grouping. Each selected field becomes a grouping level in the widget.Example: Location → Department → Device Type.

    Vendor → Model → Asset Type

    Asset Type

  • IT Asset Status

  • Fixed Asset Status

  • Group By

  • Location Name

  • Installed Location

  • Organization Name

  • Is Active

  • Designation

  • Floor

  • Building

  • SAP ID

  • Location

  • OLD Associated Assets

  • Colour

  • Service Catalogue

  • Organization Name

  • Department

  • Team

  • And more.