Ask AwraIQ about features, pricing, onboarding, login, integrations, security, demos, mobile apps, automation, reports, or support.
Switch third-party AI off for your organization. See every call it made.
One switch under Settings › AI & Data stops every in-app feature from sending anything to an AI provider. Ten module switches turn AI off where you want it quiet. And a usage log shows the last 30 days of calls by provider and purpose, so you can see where your data went without anyone keeping a copy of what was in it.
Workspace-wide switch · Ten module switches · Providers named · 30-day usage log · Content never logged · Web and mobile app
- Insights, forecasts and quotation comparisons add a written summary.
- The helpdesk copilot drafts, summarises and triages.
- Each answered call adds a row: provider and purpose.
- Nothing is sent to an AI provider, from any in-app feature.
- Insights, forecasts and comparisons still show their figures.
- The change itself is written to the audit log, with who made it.
Changing it needs the edit-settings permission. Everyone in the organization is affected at once.
What the product does with the switch on, and with it off.
Switching third-party AI off removes the written layer, not the work underneath it. The figures are computed by AWRA either way; what a provider adds is the sentence that explains them, the draft that saves typing, or the rephrased answer.
The switch, the modules, the providers and the log, on two screens.
Settings › AI & Data holds the workspace switch, the providers that receive requests and the usage log. Settings › AI modules holds a switch per module. The mobile app carries the same switches, over the same API.
- InventoryStock insights, demand forecasts, smart reorder, stock answers
- ProcurementVendor insights, quotation analysis, supplier evaluation
- SalesSales insights, overdue-invoice and sales answers
- AccountingAccounting insights and their summaries
- HRPeople Pulse insights, summary and HR answers
- ProjectsProjects insights and their summary
- AssetsAsset insights on the asset screens
- HelpdeskReply drafts, summaries, triage, support insights
- POSPoint-of-sale insights
- AutomationWorkflow run health, failures and its summary
| Purpose | Provider | Calls, 30 days | Last call | Content |
|---|---|---|---|---|
| In-app assistant | Groq | 412 | 28 Oct 2026 09:14 | not stored |
| Dashboard and module insights | Groq | 236 | 28 Oct 2026 08:02 | not stored |
| Helpdesk drafts and summaries | Groq | 88 | 27 Oct 2026 17:45 | not stored |
| Forecast narratives | Groq | 41 | 27 Oct 2026 06:30 | not stored |
| Dashboard and module insights | Google Gemini | 9 | 21 Oct 2026 11:20 | not stored |
| Quotation analysis | Groq | 6 | 19 Oct 2026 14:08 | not stored |
The content column is drawn here to make the point. The real screen has no such column, because there is nothing to put in it: the log holds the provider, the purpose, the time and the prompt’s length in characters.
Every model call goes through one door, and the switch is on the door.
A switch checked feature by feature is a switch some feature forgets. Here the check sits in the one service every language-model call passes through, so a feature added next month is covered the day it ships.
A feature asks for words
An insight wants its summary, an agent asks for a draft, the assistant has matched a piece of guidance. The figures are already computed by then.
The door checks your organization
Is third-party AI on, and is there room in the plan’s monthly AI allowance? If either answer is no, nothing is sent and the feature shows what it has without the written part.
Groq, then Gemini
The request goes to Groq. If Groq is unavailable it goes to Google Gemini. Each is called on its own API, with no gateway in between.
One row in the log
When a call is answered, the log records the provider, the purpose, the time and the prompt’s length. The prompt and the answer are not written to it.
A setting for everyone, changed by the people you choose.
The workspace switch
Seen by anyone with the view-settings permission and changed only by a role with edit-settings. Administrators hold both.
The module switches
A separate permission, manage_ai_settings, because turning a module’s AI off changes it for everyone who uses that module.
Recorded when it moves
Switching third-party AI on or off writes an entry to the audit log naming the person who did it, so the question of when AI was enabled has an answer.
Same switches on mobile
The mobile app shows the switch, the module switches, the providers and the usage, under the same permissions as the web.
Counted against your plan
Each answered call counts toward the plan’s monthly AI allowance. When it is used up, features carry on without the written layer until the next month.
The public assistants are separate
The website and Academy assistants answer visitors from published material, not your organization’s records, so they sit outside this switch.
What AWRA OpsHub does today
- A workspace switch for third-party AI under Settings › AI & Data, checked in the one service every language-model call passes through, so no in-app feature sends anything to a provider while it is off.
- Features that keep their figures with the switch off — insights, forecasts and quotation comparisons show what they computed, without the written summary.
- Forecasts and quotation scoring on AWRA’s own service, unaffected by the switch.
- Answers about your own figures in the in-app assistant, taken from your records and never passed through a model.
- Ten module switches — inventory, procurement, sales, accounting, HR, projects, assets, helpdesk, point of sale and automation — under their own permission.
- The providers named on the settings page with what each is used for, its region and the data it receives, read from the published sub-processor register.
- A 30-day usage view of calls by provider and purpose, with the count and the time of the last call; the content of a request is never logged.
- An audit log entry each time the workspace switch is turned on or off, naming who did it.
- The same switches and usage in the mobile app, over the same API.
More we can add to your workspace
- A per-call view of the usage log with each call’s time and screen, and a CSV export of it for your own records.
- A date range on the usage view reaching further back than the last 30 days.
- A choice of provider per organization, such as Gemini only, or Groq only.
- AI usage events in the audit log stream, so your SIEM sees each call beside the rest of the trail.
- A switch per role, so AI summaries reach managers while other roles see figures only.
- A self-hosted inference option, answering requests inside our own environment with no third-party provider involved.
Where we point you to a specialist
- We do not keep the content of an AI request in the usage log. A log of what was sent would be a second copy of your records in a place nobody reviews, which is the opposite of what a control is for. The log says who received a request and why; the record itself stays where it lives.
- We do not route requests through a model aggregator. Each provider is called on its own API, so the list on the settings page is the whole list.
The per-call view with a CSV export is the item that most often decides a security review, and the audit-stream events are the one that puts AI usage in front of the team that already watches everything else. Tell us what your reviewers ask for, and we will come back with a written spec, a timeline and a price.
The features it governs, and the pages that publish the detail.
Frequently asked questions
What happens when we switch third-party AI off?
Which AI providers receive requests?
What does the usage log record?
Who can turn third-party AI on or off?
How are the module switches different from the workspace switch?
Does anything still work with third-party AI off?
Is our data used to train AI models?
Do the assistants on the public website follow this switch?
Help Center
Need a quick answer while you read?
Run inventory, procurement, assets, sales, and field work with approved AWRA guidance for setup, migration, integrations, security, pricing, and support.