SENTRA GUARD & VIEW

What changed in each version of SENTRA GUARD & VIEW.

Newest first. Latest version: v1.25.1.

v1.25.1 · 2026-10-27#

Downtime SENTRA VIEW and each GUARD restart for about 10 seconds; firewalls keep running.

VIEW Roles & permissions: role names are written across the top of the table in full (they were cut off when turned sideways)

Downtime SENTRA VIEW and each GUARD restart for about 10 seconds; firewalls keep running.

GUARD roles are now fully custom: a master admin creates, renames, re-shapes and deletes any role from a permission table of 35 plain-English permissions (Users & roles). Master Admin is fixed and always holds everything
Every GUARD screen and action now checks a named permission, so a custom role (e.g. "Billing Desk") sees and does exactly what it is given; buttons a role can't use are hidden
Admin, Operator and Viewer ship with the permissions they always had, so an upgraded GUARD behaves the same until someone edits them; a deleted shipped role stays deleted
Deleting a role in use asks which role its people move to; someone who manages users without being a master admin can't hand out a role with more than they hold or touch a master admin
Each role carries a default sign-in role for the ATS / NTS boxes (unless set per user); SENTRA VIEW jump-ins keep the fixed level from the link
SENTRA VIEW: only the Super Admin adds, edits or deletes roles, and may now change or delete any role, the shipped ones included (OMM Admin follows every permission until edited); deleting a role in use moves its grants to the role chosen
SENTRA VIEW: the permission table's column headers sit exactly over their checkboxes, with a fixed Super Admin column, a sticky first column and sideways scrolling on phones
SENTRA VIEW: Access across the fleet lists each GUARD's own roles (custom ones included) when adding or editing a user

Downtime SENTRA VIEW and each GUARD restart for about 10 seconds; firewalls keep running.

Fleet price book: SENTRA VIEW › Plans & pricing sets plans, prices and the billing currency once and pushes the whole book to every GUARD (a GUARD that is offline gets it when it's back); each GUARD shows as in step, waiting or differs, with Push again
Nothing changes until the price book is first saved; it can start from a GUARD's current plans so nobody's prices change by surprise. New prices apply from each GUARD's next billing run; issued invoices never change
While VIEW sets prices, a GUARD's Plans & pricing is read-only ("Prices are set by SENTRA VIEW") and its currency follows VIEW; a GUARD on its own (no VIEW link) keeps managing its own plans
Plans can now be added and retired (not only the four built-in ones). Retired plans stay for the customers and invoices on them but can't be picked for new customers; plans are never deleted and the last active plan can't be retired
VIEW's Add customer and plan pickers use the price book; new permission "Set the fleet price book" (billing.prices)

Downtime SENTRA VIEW and each GUARD restart for about 10 seconds; firewalls keep running.

Product names: protection is now shown as "Web App · ATS (AI Threat Shield)" and "Internet · NTS (Network Threat Shield)" everywhere in VIEW and GUARD (short tags ATS / NTS), instead of WAF and CleanPipe / DIA

Downtime SENTRA VIEW and each GUARD restart for about 10 seconds; firewalls keep running.

Signed releases: SENTRA VIEW takes updates from the SENTRA release server (updates.sentra-ai.com) and installs a release only after checking it end to end: SENTRA root key, release key, signed release list, package and every file.
VIEW hands each GUARD the proof with every release; the GUARD checks every file again before installing, and nodes check what their GUARD hands them (SENTRA SHIELD, SENTRA NTS, the node agent).
A release that fails a check is refused ("signature check failed") and nothing changes; withdrawn releases are never installed.
Software updates shows where updates come from and switches between the SENTRA release server and a developer source (git, for SENTRA's own labs). A VIEW that already updated from git keeps it until switched; new installs use the release server.
VIEW changes customers, firewalls, nodes and billing on its GUARDs; billing can run on a GUARD or from VIEW.