Governed web chat
New conversation
Notifications
Inbox
Every Fortress event for you lands here, whatever happens on email or chat. Messages carry metadata only: event, asset, severity, a one-line summary and time.
Governance
Approvals
Requests you are an approver for, including governed actions requested with this portal's /action command. Decide here; email links and chat buttons lead to the same signed, single-use decision. Commands the agent wants to run on the appliance wait for approval in the Control UI.
Approval decision
Review request
Notification identity
Confirm your email
Confirm that notifications for may be sent to the address your administrator entered.
Operations
Shift handoff
What this shift hands to the next: open work from the plant apps with its owner and next step, restrictions the incoming lead acknowledges one by one, and the questions in between. Walk through it together; acknowledging is a receipt, never authorization to operate equipment.
AgenticMemory
Knowledge
Reviewed lessons, site knowledge, documents and the plant apps' notes — only what you are allowed to see, each with its source and status. Your private memory is yours alone; anything shared is published only after a second person reviews it.
Governance
AI clients (MCP)
Customers' own AI tools ask Fortress through its MCP endpoint. Each client is bound to one Fortress account (its role and scope apply) and has a trust class: on_prem sees what that person sees in the console; external (cloud-hosted AI) gets answers minimized by AgenticDLP, and AgenticRouter decides each call.
Cloud API keys
Store a provider key once for all registered Fortress apps. Keys are encrypted on this appliance and never displayed after saving. Apps use Core’s cloud broker; they do not receive the key.
Integrations
Channels
Configure how local Fortress users are reached. Credentials are write-only: once saved they are never shown again. Every change is written to the audit chain.
Routing
Notification groups
Selected Industry Preset
Groups decide who hears about which events, through which channels, when, and who may approve. Preset groups can be customized, renamed, or replaced with industry-specific operational templates. Inbox and email are always included for every member.
Appliance AI
Local model
One model runs every Fortress app on this appliance: the console chat, Manufacturing Intelligence, Industrial Intelligence and AI clients. Changing it here applies to all of them within a minute, without a restart.
Installed models
Verify loads a model with this appliance's context size and checks that it replies and calls a tool (the apps need tool calling). Use selects it for every app after it passes. A first load can take a few minutes.
Qualified models
Every option reads text and images and calls tools. Install one on the appliance with ollama pull <name> (or an offline bundle), then Verify and Use it here. Production on the larger models wants 48 GB of GPU memory.
Appliance governance
Egress
Decides whether anything may leave this appliance for a cloud model. Local only keeps every request on the appliance. Governed cloud allows minimised requests through AgenticDLP and AgenticRouter, narrowed below per channel and per app. Opening egress asks for your password.
Channels and apps
A ceiling can hold one channel or app to local while the site uses governed cloud. It never opens anything when the site is local only.
Account security
Sign-in security
To reset an individual user's authenticator, open Users, edit that user and select Reset authenticator.
Local identity
Users
Local accounts on this appliance. Every Fortress app signs people in here. Scope limits which assets a person can investigate or approve in each app: the whole site, an area, or single assets.
Customer onboarding
Customer integrations
Bring the customer's systems into a reviewed, accepted integration. Track access, mappings, commissioning, approvals and handover for each source.
Core configuration
CMDB
Select a configuration item.
Load base data
Fill the workbook from your asset register, upload it, check the dry run, then commit. Nothing is written until you commit, and a committed import can be rolled back.
History
Each connected system's probe reads what that system already knows and loads it through the same checks as an import. Probes only read; they never change plant systems.
Deployment license
The subscription term and signed offline-file validity are separate. Import a refreshed file from the Fortress website console before its validity window ends.
Expiration keeps local inference, audit export, AgenticGate and AgenticDLP available. It blocks new managed cloud access and scope changes. Licensing does not provide unattended remote access.
Evidence
Audit
Agentic Insights access
Remote Support
Agentic Insights can reach this appliance only while this switch is On. Off is the default, and support turns Off by itself when the time you set runs out, when the appliance restarts, or if anything fails. Every change and every support session is recorded on this appliance.
Right now
Checking…
Change record
Kept on this appliance, hash-chained, append-only, never collected by Agentic Insights. Includes switch changes, support sessions, and each command run during a session.
Tailnet rule for this site
Who can connect
Licensing heartbeat
Exactly what is sent
Sent outbound over HTTPS whether support is on or off. It never carries your content, and it cannot turn anything off on this appliance.