Bots homepage

The Ivanti Bots homepage provides an overall view of all Neurons Bots over two tabs: General Bots and Survey Bots.

General bots are used to identify, prevent and remediate a range of issues using a combination of queries, actions, user interactions and other logic.

Survey bots (in rollout) offer the same general capabilities as general bots, but have a dedicated reporting interface and results page. These provide an in-depth historical insight into results and casual factors for a range of use cases, powered by user ratings, choices, or free text input.

In the top-right corner:

• Select the Trigger History button to view an audit history of all the bots run activity. Learn more about the Trigger History.

• Select the Endpoint Interactions button to view the numbers of interactions with endpoints over time. Learn more about Endpoint Interactions.

• Select the Manage user stages button to create, modify, and manage permissions of user stage directly from the top-level Bots page. This enhancement allows administrators and authorized users to:

  • Access User Stages without opening a bot.

  • Manage User Stage sharing and permissions from a centralized location.

  • Grant or modify access more efficiently.

    For more information, see User Stages.

• Select the Settings button to configure Notifications, MS Teams App Welcome Message, and MS Teams User Detection Order.

  • Notifications: You can select for which scheduled bot and survey events notifications will be displayed (Started, Completed, Failed), and specify which Roles or Users will receive them.

  • MS Teams App Welcome Message: When new users install the Ivanti Neurons Bot app in MS Teams, you may customize a welcome message for them. You have the option to include Markdown syntax in the message and preview it before applying. You can use the default message if preferred. See adaptivecards.microsoft.com.

  • MS Teams User Detection Order: You can choose from the following detection orders to determine how auto-detect resolves the MS Teams user for a device:

    • Prioritize Entra ID over inventory-based detection (default): This uses a two-phase approach: it first queries Entra ID for the user’s GID, then falls back to inventory-based detection using other data such as the user’s name. Under Prioritize Entra ID, there are four sub-options to control how MS Teams identifies users:

      • Prefer using GID for inventory-based detection when available (default): Uses the user’s GID if available. GID refers to the user’s Entra ID, which comes from the data services field.

      • Prefer using UPN for inventory-based detection when available: If the default method causes significant mismatches in certain environments (commonly in hybrid environments), you can switch to UPN. This option uses the UPN (User Principal Name) from the inventory when available; if not, it falls back to GID.

      • Use GID only for inventory-based detection: Uses only the GID. If GID is not available, it will not use UPN. This works better when users have duplicate names.

      • Use UPN only for inventory-based detection: Uses only the UPN. If UPN is not available, it will not use GID.

    • Skip Entra ID, use inventory-based detection: This skips Entra ID integration entirely and relies only on inventory-based detection.

General Bots

The grid on the General tab displays the following details for all bots:

• Alerts
  The bot requires an action. The action required prevents the bot from running. Such as, a stage has been disabled.
  The bot has warnings. The warnings do not prevent the bot from running, but does prevent any edits from being saved and published. Such as, a stage has been deprecated.
  If a bot has both warnings and actions required then only the action icon displays in the column.
• Name & Description: The name and description given to the bot when created in the Bot editor. You can select to rename or edit the description from the Actions menu. Click on a bot name to display the Bots Results page.

• Owner: Displays the name of the bot owner. If no owner is assigned, for example, if the owner has been deleted, the bot is displayed as Unassigned.

• Shared: Displays the bot's sharing access level. There are three sharing statuses:

  • Private: The bot is visible only to you.

  • Public: The bot is visible to all Neurons Platform users in your organization.

  • Shared: The bot is shared with selected users or groups.

• Trigger Type: The bot trigger type; Schedule or Custom Action. Learn more about Triggers.
• Status: The status of the bot:
  • Draft: The bot is a draft version that has not been published. The bot cannot be run.
  • Inactive: The status shows inactive when a bot has been published but not made active. An inactive bot cannot be run with Devices or People View but can be run manually with the Neurons Bots UI.
  • Active: The bot has been published and has been made active. The bot can be run.
  • Disabled: The status shows disabled when a bot is active, but the user isn't entitled to run it. The bot cannot be run.

  • Expired: This status is shown when the schedule end time has passed.

The state indicates whether the bot can be run or not, the bot must be set to active to be invoked either by a Schedule or Custom Action. To do this go to the Bot editor > Trigger settings > Trigger status and set the toggle to Active. Learn more about Trigger settings.

• Trigger count: The number of times the bot has been triggered.
• Last triggered: The date and time the bot was last triggered. For more trigger and device details, refer to Trigger history.
• Category: : Displays the category of the bot. Select , it displays the list of the categories of the bot, where you can select the category as per your preference.

Create Bot

Select to start building a new bot. Learn more aboutBots creation.

Actions

Select the check box in the first column of the bots grid and select Actions to choose from the following:

• Rename: Select to rename the selected bot. The Rename bot dialog appears. Enter the new name for the bot and select Rename. A toast notification appears in the top right to inform you if the bot has been renamed successfully.
• Edit Description: Select to edit the bot description. The Edit description dialog appears. Edit the description and select Save.
• Clone: Select to clone the latest version selected bot. The Clone bot dialog appears. Enter the name for the new cloned bot and select Clone. A toast notification appears in the top right to inform you if the bot has been cloned successfully. When a bot is cloned, the user who performs the clone becomes the owner of the cloned bot. Any existing schedule configuration is preserved; however, the schedule trigger is disabled until it is reviewed and reactivated by the owner.
• Delete: Select to delete the bot. The Delete bot dialog appears. Select Delete to confirm the action. A toast notification appears in the top right to inform you if the bot has been deleted successfully.
  Deleting the bot will permanently delete all versions of the bot and the run history. You cannot undo this action. Bots can be deleted only by the owner or an administrator. Unassigned bots can be deleted only by an administrator.

• Ownership: Determines the owner responsible for managing the bot. A bot without an assigned owner is displayed as Unassigned. An administrator can take ownership of an unassigned bot or assign it to another user, allowing them to manage the bot and its access settings. If ownership is transferred, the previous owner may lose access to the bot and is redirected to the Bots home page after the change is applied.

  When a bot contains an active schedule, transferring ownership automatically disables the schedule. This behavior prevents unintended changes to the target scope that could occur if the new owner has access to a different set of devices or resources than the previous owner. Before the ownership transfer is completed, a warning message informs you that:

  • The active schedule will be set to Inactive.

  • Future scheduled executions will not run until the schedule is reviewed and reactivated.

  • The new owner must validate the configuration and manually reactivate the schedule, if required.

    The schedule trigger settings are retained when ownership is transferred. The target group(s) setting is disabled and cannot be edited until it is updated by the new owner or an administrator. The new owner can review the existing schedule settings and reactivate the schedule without recreating the configuration.
    If the owner of a scheduled bot is removed from the system, the schedule is automatically disabled for the same reason.

• Sharing: Determines who can view or edit a bot. Sharing controls the bot's visibility and the level of access granted to other users. You can make a bot public, restrict access to specific users, or grant view or edit permissions as needed.

  A bot can be:

  • Public: The bot is visible to all Neurons Platform users in your organization.

  • Private: The bot is visible only to the bot owner.

  • Shared: The bot owner can share the bot with selected users or groups.

  Depending on the sharing configuration, users may receive either view-only or edit permissions. If a user opens a link to a bot that they do not have permission to access, a Permission Denied message is displayed. After acknowledging the message, the user is redirected to the Bots home page.

  When a user has permission to view a bot but does not have permission to edit it, the bot opens in read-only mode. The user can view the bot configuration but cannot make or save changes. This restriction also applies to the bot's trigger configuration. If the bot has a schedule configured, the Target Group(s) setting is unavailable for editing unless the user is the bot owner or an administrator.

  Bots saved as drafts do not support Object Ownership. As a result, the Ownership and Sharing actions are not available for draft bots.

  When applying the Ownership or Sharing actions to multiple bots, all selected bots must be eligible for the action. The action cannot be completed if the selection includes bots that you do not own or bots that are in a draft state. If the action fails, an error message identifies the bots that prevented the action from being completed.

  Object Ownership and Sharing control visibility and access within the Bots feature list. The ability to view a custom action in the Device View or Devices List is still controlled by adding users / roles to the "Limit user access" option of a Bot's trigger settings. Without setting this, a Bot will still be visible as a Custom Action regardless of Ownership or Sharing status.
  

• Categorize: Select to update the category or assign a new category to the existing bot or uncategorized bots. You can assign categories to the bot not only at the time of Save and Publish but also update categories from the bot’s grid as well. Once you select Categorize, the categorize window appears. You can select an existing category from the drop-down, or you can enter a category name to create a new category and select Update.

Survey Bots

The grid on the Survey tab displays the following details for all bots:

• Alerts
  The bot requires an action. The action required prevents the bot from running. Such as, a stage has been disabled.
  The bot has warnings. The warnings do not prevent the bot from running, but does prevent any edits from being saved and published. Such as, a stage has been deprecated.
  If a bot has both warnings and actions required then only the action icon displays in the column.
• Name & Description: The name and description given to the bot when created in the Bot editor. You can select to rename or edit the description from the Actions menu. Click on a bot name to display the Survey Results page.

• Owner: Displays the name of the survey owner. If no owner is assigned, for example, if the owner has been deleted, the survey is displayed as Unassigned.

• Shared: Displays the survey’s sharing access level. There are three sharing statuses:

  • Private: The survey is visible only to you.

  • Public: The survey is visible to all Neurons Platform users in your organization.

  • Shared: The survey is shared with selected users or groups.

• First Run Time: The date and time the first instance of the survey was run.
• Last Run Time: The date and time the last instance of the survey was run.
• Survey Rating: The overall survey score for all runs.
• Number of responses: The number of survey responses received, a combined value for all runs.
• Response rate: The percentage response rate.

Create survey

Select to start building a new survey. Learn more about Bots creation.

Actions

Select the check box in the first column of the bots grid and select Actions to choose from the following:

• Rename: Select to rename the survey. The Rename survey dialog appears. Enter the new name for the survey and select Rename. A toast notification appears in the top right to inform you if the survey has been renamed successfully.
• Edit Description: Select to edit the survey description. The Edit description dialog appears. Edit the description and select Save.
• Clone: Select to clone the latest version selected bot. The Clone survey dialog appears. Enter the name for the new cloned survey and select Clone. A toast notification appears in the top right to inform you if the survey has been cloned successfully. When a survey is cloned, the user who performs the clone becomes the owner of the cloned survey. Any existing schedule configuration is preserved; however, the schedule trigger is disabled until it is reviewed and reactivated by the owner.
• Delete: Select to delete the survey. The Delete survey dialog appears. Select Delete to confirm the action. A toast notification appears in the top right to inform you if the survey has been deleted successfully.
  Deleting the survey will permanently delete all versions of the survey and the run history. You cannot undo this action. Surveys can be deleted only by the owner or an administrator. Unassigned surveys can be deleted only by an administrator.

• Ownership: Survey ownership follows the same ownership model used for General bots. Survey owners are responsible for managing the survey and its access settings. Ownership is managed at the survey level and applies across the survey and its associated iterations. For more information, see General bots' actions.

• Sharing: Survey sharing follows the same sharing model used for General bots. Survey owners can control who can view or edit a survey through sharing settings. Access to survey iterations is determined by the visibility and access settings of the parent survey, providing consistent access control across the survey and its associated iterations. For more information, see General bots' actions.

• Categorize: Select to update the category or assign a new category to the existing survey. You can assign categories to the survey not only at the time of Save and Publish but also update categories from the survey’s grid as well. Once you select Categorize, the categorize window appears. You can select an existing category from the drop-down, or you can enter a category name to create a new category and select Update.

View by category

Beside the “Actions” tab, you can select the View by category check box to view the bots or surveys as per their category in a segregated line, where you can expand or collapse each category.

Related topics

Bots creation

Bots editor

Bots Results