Refresh New client

Each company's subscription, one switch per module. Click a cell to turn a module on or off — you confirm first, the change is logged, and it reaches that company's portal within a minute. Off never deletes anything: switching back on restores the module exactly as it was.

Every instance measured: who is signing in, how much database room is left, what the AI assistant is costing, and whether anything is erroring — refreshed on demand. Spend figures are estimates, the same math as each company's Billing tab. Health counts server-side failures captured since this build went live, kept for the retention window; click a health flag to see the entries. Suspend here uses the exact same switch as the Instances tab. Each row can carry its own AI rate card and alert thresholds (the sliders button on its row) and download a per-month statement; alert flags are read-side only — nothing emails, nothing blocks.

Include demo Include retired Alert defaults Export CSV Refresh

Accounts across every company. The full editor is the same User Management screen you already know, opened across all companies with a Company column and filter — bulk changes still apply within one company at a time (permission roles belong to an instance).

Each company can send its portal email — notifications, announcements, reset codes — from its own domain instead of the shared AgriSphere address. Register the domain here, hand the three DNS records to the company's IT, and watch the status. Once Amazon confirms the records, mail switches to the company's domain automatically — provided their notification sender address (Company Profile → notification email) is set to an address at that domain; a company still sending from the shared address keeps doing so. Until verification (and whenever anything is unsure) email keeps going out from the shared sender, so nothing ever stops delivering.

Check statuses Add domain

Let a company's people sign in with their Microsoft work accounts. Enable the company here and paste its Microsoft tenant ID (their IT finds it in Entra admin center → Overview). Sign-in only works for people who already have a portal account at the matching work email — nobody is created automatically — and only from the Microsoft organizations you list here. Password sign-in keeps working for a company unless you set "Require Microsoft sign-in" for it — that switch turns password and passkey sign-in off for its people (never for AgriSphere accounts), and you can clear it here at any time.

Refresh Set up company

Everything a user flagged with a thumbs-down, plus every answer where Terra hit an error. Set a status as you work through them, and export the list to hand to a build session.

Open (new + reviewing)NewReviewingResolvedDismissedAll Both kindsThumbs-downErrors All timeLast 7 daysLast 30 daysLast 90 days Export .md Export .json

Set to reviewingSet to resolvedSet to dismissedSet to new Apply to selected Clear selection

Every Terra conversation on this instance. Click one to read the full exchange.

All timeLast 7 daysLast 30 daysLast 90 days Search

Window: Last 7 daysLast 30 daysLast 90 daysLast year Counts cover chat turns; voice calls aren't included.

Window: Last 3 monthsLast 6 monthsLast 12 months Estimates only: recorded tokens × the configured per-model rates. Prompt-cache discounts aren't modeled, and voice (speech in/out) isn't tracked.

Named accounts, each pegged to one company. This list shows THIS instance's accounts (multi-company admin accounts appear on every instance). New and reset accounts get a temporary password and must change it at first sign-in.

0 selected — assign permission set: Read-only (clear role) Apply to selected job title: — No job title (clear) Apply Assign locations Clear selection

Table editing no changes yet Save all changes Done

Loading…

Loading…

A permission role is a named set of explicit capabilities — what its members can create, edit, publish, move back to draft, delete, or attach, per module. Assign one to accounts with the base role user (from the Users tab — per account or in bulk). Accounts without a permission role are read-only; editor and admin always have every capability. Every role belongs to ONE client instance — a role created here can only be assigned to this instance's accounts. AgriSphere staff switch instances (client menu) to manage another client's roles.

Loading roles…

All Incidents (Excel) All Training Sessions (Excel) All BBS Observations (Excel) All Equipment (Excel) All Locations (Excel) Policy Attachment Library — file list (Excel) Full Data Export — one workbook, every data type