Ngage can only do what the person asking can do
Every request runs within the signed-in user’s own ERP permissions, with approvals you choose and every step on an audit trail.
Controls on every request
Ngage acts as the person asking, waits for a yes where you set one, and writes down each step.
Ngage Audit record - Asked by
- planner@example.com
- Request
- Raise a fault report for pump P-114.
- Ran as
- The asker, with their own IFS permissions
- 09:41:03 Planned Read the asset, draft the report, wait for a yes
- 09:41:06 Ran Read asset P-114 and its open work orders IFS
- 09:41:09 Came back 2 open faults, seal wear IFS
- 09:42:30 Approved By the planner, in NgageChat
- 09:42:31 Ran Created the fault report IFS
- 09:42:32 Came back Fault report 2231, status Reported IFS
Your own permissions
Ngage acts as the signed-in user, never as a shared service account.
Approvals you choose
Writes can wait for a person’s yes. You decide which actions wait.
Your sign-in
Single sign-on with Microsoft Entra ID or OIDC. Your MFA and conditional access still apply.
Every step on the record
An immutable audit trail: who asked, what was planned, what ran and what came back.
How Ngage reaches your ERP
Through each ERP’s official interfaces, never the database.
In IBM Maximo, IFS and SAP
Every read and write goes through each ERP’s official interfaces, so its own rules still apply.
The database, never touched
Ngage never reads or writes an ERP database directly.
Nothing installed in IFS
On IFS: no code on IFS servers and no schema changes.
Where the language model runs
Enterprise deployments run on Google Cloud Vertex AI. These are the settings that apply.
| Control | Setting |
|---|---|
| Zero data retention | Configured: provider caching and request logging off |
| No training on your data | Google does not train on your data without permission |
| Your region | The Google Cloud region you choose |
| Your keys | Customer-managed keys (CMEK), where configured |
| In transit | TLS |
What these protections depend on
The limits of the claims above, stated plainly.
Certifications are Google’s
They do not certify Ngage or your deployment.
Settings vary by deployment
Retention, region and keys follow your contract.
Ngage records are separate
Provider retention does not govern Ngage history, logs or exports.
Described, not certified
Our privacy overview is not an independent audit.
Bring your security review
We go through the evidence with your security team, item by item.
What a review covers
- Google Cloud project and model
- Contract and abuse-logging scope
- Cache and logging settings
- Cloud service-account permissions
- Retention of Ngage records