1. Introduction
This document provides information on the features, improvements, and known issues for this Neeve release. The Neeve Portal is currently in Beta stage. It may be missing features or have small bugs. We are targeting monthly releases to continue improving the product experience and adding new functionality.
2. Changes in this release (Neeve Portal v1.7, October 2026)
2.1 New Features
Network diagnostics from the Neeve Portal. Diagnostics can now be enabled on a System Network and run from the Neeve Portal, with no one needed on site. On the network details page, an Org Admin enables diagnostics with a single click on a DHCP network, or by entering an available IP address on the subnet for a STATIC network; a status indicator then shows the diagnostics service as Starting, Healthy, or Status unavailable when the node is offline. Diagnostics can also be enabled later from the network's edit form, and on a DYNAMIC network once the network has been assigned its CIDR/IP. The Run Diagnostics dialog, opened from the network details page, runs Network Info, Ping, Traceroute, DNS Lookup and Bandwidth tests against the selected node and network, with settings such as ping count and traceroute maximum hops, and a Copy output action for pasting results into a support ticket. Org Admins and Site Operators can run the tests. Results are not kept after the dialog is closed.
Single login for a site's System Network and its Cloud BMS. A System Network with Remote Access Agent (RAA) enabled can now be associated with the organization's Cloud BMS, so that a user who logs in to that site through the Neeve Agent reaches both the site's devices and the Cloud BMS with one login, instead of logging in to each separately. The option, Associate this system network with Cloud BMS, appears on the network form when RAA is enabled and the organization has a Cloud BMS, and is off by default. The association attaches the Cloud BMS endpoint to the site's connector; it does not grant access to the site, so a user without access to the site cannot reach the site or the Cloud BMS through it. Every user who does have access to the site can reach the Cloud BMS once the network is associated — see Known Limitations before enabling it. Removing the association, or disabling RAA on the network, detaches the Cloud BMS; a user who is already logged in keeps access until they switch sites or log in again.
2.2 Enhancements
Faster TCP connection onboarding, with status shown in the Portal. When a System Network is created with Remote Access Agent enabled, its TCP connection is now provisioned in the background: the Portal responds immediately rather than waiting for provisioning to finish, and onboarding completes faster than before. The onboarding status is shown on both the Launcher and the network pages, and refreshes automatically every five minutes as well as on page refresh. If provisioning fails, the status shows Failed with the reason, and a Retry action re-runs provisioning without deleting and recreating the network. Cloud BMS endpoint onboarding benefits from the same change.
Launcher opens in Hierarchy view for users with more than 20 endpoint connections. When you sign in with access to more than 20 endpoint connections, the Launcher now opens in Hierarchy view instead of Tiles. With 20 or fewer connections it opens in Tiles (List on mobile), as before. This sets only the initial view: you can switch between Tiles, List and Hierarchy at any time, and a bookmarked link that specifies a view continues to open that view. There is no setting to change this default.
2.3 Bug Fixes
Bulk endpoint onboarding no longer fails partway through. Onboarding a large batch of endpoints — tested with 50 endpoints and two connections each — could previously leave some endpoints or connections uncreated, with no clear indication of which were missing. (NEEVEDEV-7726)
3. Prerequisites
3.1 Cloud Requirements
The following cloud platforms are supported:
Amazon AWS
Microsoft Azure
VMware vSphere v6.x
Google Cloud
3.1.1 Cloud Connector Compute Requirements
2 vCPU
2GB RAM
10GB HDD
Public IP address
4. Issues
4.1 Known Limitations
The following limitations exist within the Neeve portal. Due to the beta nature of the Neeve Portal, not all features are available within the Neeve Portal.
New in this release
Portfolio Admins and Site Admins can currently enable the Cloud BMS association on a System Network. This is intended to be limited to Org Admins, and a fix is planned for a subsequent release.
Cloud BMS access cannot be limited to specific users on an associated network: every user with access to the site reaches the Cloud BMS through the single login. Workaround: do not enable the association on a network where Cloud BMS access must be restricted to some of the site's users.
The Associate this system network with Cloud BMS option is available even when the Cloud BMS site has no TCP connection yet, so an association can be enabled before there is a connection for it to use. Create the Cloud BMS site's TCP connection before associating networks with it. A fix is planned for a subsequent release.
Disabling Cloud BMS for an organization is not blocked while a System Network is still associated with it. The change is accepted and the network keeps its association setting, pointing at a Cloud BMS that is no longer enabled. Remove the association from each network before disabling Cloud BMS. A fix is planned for a subsequent release.
When a node is onboarded with a DHCP network and diagnostics enabled in the same onboarding flow, the node's service listener rule for diagnostics is not applied and every diagnostics request from the Portal fails. Workaround: onboard the network first, then enable diagnostics from the network details page. A fix is planned for a subsequent release.
After a node switches from its wired WAN connection to cellular, the node details page continues to show the cellular connection as disconnected and does not show the cellular connection details, although the node is online via cellular. A fix is expected in a subsequent release.
When a node is Unreachable, the interfaces on its node details page keep their last known status (for example, Connected) instead of reflecting that the node is offline. A fix is in progress.
Endpoint connections in a Cloud VDI site show a status of Terminated rather than Connected, because a Cloud VDI site has no tunnel to a Cloud Connector for the status to reflect. The connections themselves are unaffected. A fix is planned for a subsequent release.
Carried forward from previous releases
The Node Config UI displays APN details read from the SIM's carrier profile rather than the custom APN you configured. The configured APN is applied correctly; only the displayed value is wrong. A fix is expected in a subsequent release.
A configured APN can be overwritten with a new value, but it cannot be unset. There is currently no option to remove an APN configuration once saved.
APN names accept special characters that are not valid in an APN. Validation is not applied on this field.
Changing the CIDR of a DHCP network that has TCP connections enabled stops those TCP connections from working. Workaround: disable Remote Access Agent (RAA) on the network and re-enable it; this restores the routes. This will be addressed as part of TCP onboarding changes.
Setting a DHCP address pool where the start and end addresses are the same does not produce an inline error. A toast message appears when you attempt to create the network.
Entering a DHCP TAN subnet smaller than /24 does not produce an inline error. The deployment is blocked, but the message appears only on save.
DNS resolution behavior on a DHCP System Network depends on the network's default destination. The DHCP service (dnsmasq) acts as the DNS server for devices on the network, and forwards queries to an upstream resolver: when the default destination is WAN Network, the node's configured DNS server is used; when the default destination is Tunnel, 8.8.8.8 is used.
If your portal is provisioned with Cloud BMS it can not be deactivated. This does not impact customer's portals without Cloud BMS. There is no currently available workaround.
Privilege escalation for a user doesn't trigger an email notification. There is no current workaround, please inform your users that their privileges have been increased.
For any configuration change or edit, the page requires a refresh to reflect the change.
When bulk onboarding endpoints, the success/failure toast messages fill the screen. Refer to the audit logs for more granular detail of which endpoints were successfully/unsuccessfully onboarded.
For users with access to multiple organization, logging out in one organization does not log them out of other organizations they are currently logged into. Please logout of all orgs manually, as required.
Users with access to a single endpoint or endpoint connection are listed under the parent org in the Hierarchy. There is currently no workaround.
Users with access or admin rights to multiple sites or portfolios are not listed under each of the associated sites or portfolios. The user will be listed under the site or portfolio where they have the highest privilege. A user's specific privilege can be viewed under the user's details page.
When marking a tile on the Launcher page as favorite, it will automatically be moved to the top of the first page. This can cause the tile to appear to disappear when marking a tile as favorite from the bottom of the page or on other pages other than Page 1. To verify access, return to the top of the first page of the Launcher screen.
Any change made to a System Network from the Secure Edge portal will be overwritten if a subsequent change is made to the same network from within the Neeve Portal. Once changes are made to a network from Secure Edge portal, subsequent changes should be made from Secure Edge portal to avoid configuration losses.
When using the "Setup and Configure Remote Access" onboarding flow to onboard Secure Edge Professional and Enterprise Nodes, the illustrations within the flow will not accurately reflect the form factor of these nodes. The network configuration step shows the correct diagram and should be followed as guidance on how to connect these models of nodes.
Export csv features limits the number of entries to 1000.