User Guide

For the people who run the tools, not the people who build them. No technical knowledge needed: you pick an App, click Run, and get a finished result back.

An App is a ready-made tool an admin or consultant built for you. You don’t write prompts or code — you run it and view the result. You only ever see the apps your role allows.

1. Signing in

Open the Netridium link your administrator gave you and sign in with your email and password. If you were invited, follow the link in your invitation to set a password first.

Choosing a password. It must be at least 12 characters and can’t be your own name or email address. We also check it against a public list of passwords found in past data breaches — if yours appears there you’ll be asked to pick a different one, because attackers try those lists first. There’s no requirement to mix in capitals, digits, or symbols: a memorable phrase of a few words is both easier to remember and harder to guess than something like P@ssw0rd!. The form shows you what’s still missing as you type.

Two-step verification. Your workspace may require a code from an authenticator app as well as your password. If it does and you haven’t set one up, you’ll be prompted to before you can go any further — see §8.

Single sign-on. Some workspaces sign in through their own company identity provider instead. If yours does, choose Sign in with SSO and enter your work email. Signing out of Netridium doesn’t sign you out of your identity provider, and vice versa — sessions expire on their own schedule.

2. Finding your way around

The left sidebar has three parts.

Pinned at the top: the apps you pinned, grouped into their folders. Pinning is per-person, so this list is yours alone — see §3.
Recent below it: the last five apps you opened or ran, each tagged with the system it reads (QBO, Xero, Maxio, SFDC). The newest arrival is at the top of the group; opening something that is already listed leaves it exactly where it is, so the list doesn’t shuffle under you. It fills itself in as you work — there’s nothing to set up, and nothing to tidy. It’s yours alone, even on a computer you share: the next person to sign in sees their own list. It’s kept in this browser, so it starts empty on a new device.
Inbox, Apps and History at the bottom. (Admins see more links here; if you don’t have them, you’re not an admin.)

Every heading and folder opens and closes, and stays how you left it.

Apps is your catalog and your viewer in one page. History is the record of runs. Inbox lists runs that have paused and are waiting for you to answer a question — a number beside it shows how many.

3. Finding and running an App

Open Apps. You’ll see everything your role permits, grouped into folders, each row showing the name and a short description, the systems it reads, when you last ran it, and its current status. The search box filters by name, folder, and description.

To run one:

Click Run.
If it asks for inputs, a short form appears — pick a date, choose an option, type a value — then submit. Required fields are marked and the form checks them before anything starts.
If it can change data, one more step appears: your values are shown back to you with a warning, and you confirm before it runs. See §5.
If it has neither, it starts right away.

Pin an app (the pin icon on its row) to keep it in your sidebar. Pins are per-person — pinning something doesn’t change anyone else’s sidebar.

4. Watching progress

Runs happen in the background, so you don’t have to wait on the screen. The status updates live:

Status	Means
Queued	Accepted and waiting to start.
Running	Working now. History calls this Processing.
Needs input	Paused, waiting for a person to answer a question. See below.
Ready	Finished — the result is there to open with View.
Failed	Something went wrong. Open the app, or look in History, for the reason.
Canceled	Someone stopped it. Shown in History.

You can move around the portal — open another app, check a different result — and come back; the status keeps updating, and it survives navigating away and returning. You can Cancel a run that’s still going.

When a run needs your input

Some apps stop part-way and ask a question: a yes or no, a choice from a list, a checklist, a short form, or an approval of something drafted for you. The question appears in the middle of that app’s page. If there is more than one question, each appears in turn.

While a question is up, the page behind it is dimmed and can’t be clicked. The menu on the left and the bar at the top still work, so you can go and do something else. The question stays with its app: it doesn’t appear on other pages. The run shows Needs input, the Inbox counts it, and the question opens again when you come back to the app — or you can answer it from the Inbox.

Cancel run (or the ✕) stops the run instead of answering. The run ends as Canceled and the question disappears, including from the Inbox. Note that No and Reject are answers, not cancellations — the run carries on and does whatever its author decided for that answer.

The Inbox is where you find questions you weren’t there for — from a scheduled run, one addressed to your role, or one asked a while ago. Each one shows what is being asked for, who it is for, how long it will wait, and an Answer button. You’ll get an email when a run you started is waiting on you.

Answer it and the run carries on from where it stopped. Nothing is redone.
For an approval, read what you’re approving. You can edit the text before you approve, or reject it.
A note says when something was drafted by AI. Approving lets the run act on it.
A question you leave unanswered waits until the time shown on it. After that the run ends or moves on, as its author decided.
If the question was addressed to someone else — a role, or an admin — you’ll see Waiting for someone else to answer.

Some runs are deliberately slower. If your administrator turned on batch processing for an app, it costs the business about half as much and takes noticeably longer to come back. That’s expected, not a fault.

5. Apps that can change data

Most Apps only read from your company’s systems. A few are set up to change data — create an invoice, update a record. Those are deliberately harder to run by accident:

Before it starts you get a confirmation step, and you choose Confirm and run. Where the app takes inputs, your values are listed for you to check first.
The warning is blunt on purpose: there is no preview and no undo. A value you got wrong will be written as given.

If you’re unsure what an app will change, ask your administrator before confirming. Every change it makes is recorded in your workspace’s audit log.

6. Viewing and downloading the result

When a run is Ready, click View. Depending on the app you’ll see:

A spreadsheet, with one tab per sheet. Search the whole sheet, sort any column by clicking its heading, or open Filters to narrow one column at a time — the filters combine, and the row count above the table tells you how many matched. Drag a column edge to widen it, or double-click that edge to fit it to what’s on screen. Large sheets stay smooth because only the rows you can see are drawn; use the search box rather than your browser’s find, which only sees those rows.

Filtering by amount or date. A filter box matches text anywhere in the column, but it also understands comparisons:

Type this	To find
`> 1200`	more than 1,200
`>= 1200`, `< 1200`, `<= 1200`	the rest of the comparisons
`= 0`, `!= 0`	exactly, or anything but
`1200..5000`	between, both ends included
`2026-01-01..2026-03-31`	dates work the same way
`(blank)`	the cell is empty
`(not blank)`	the cell has something in it

Three things worth knowing. Comparisons only look at cells that really are a number or a date — text like N/A, and an ID like 007, is neither, so it matches none of them, != included. A date means the whole day, so = 2026-01-01 finds a cell reading 2026-01-01 09:30:00. And anything that isn’t one of the shapes above is plain text: > abc looks for those characters, and the note under the box tells you how your filter was read. That note is also the answer when a filter you expected to work returns nothing.

One collision to know about: (blank) finds empty cells. If a report prints the word “(Blank)” in a cell — some spreadsheet exports do — searching for that text will find the empty cells instead.

Saved views. Once a report is filtered and sorted the way you want it, open Views above the table and save it under a name — “Overdue over 90 days”, say, which you can now write as > 90 in the days column. Pick it again any time to put the report back that way, including after the app is re-run with fresh data. Views are yours alone; nobody else in the workspace sees them. Running an app never happens by picking or saving a view. If an app is retired, or your access to it changes, its views disappear along with it — they are not deleted, and they come back exactly as you left them if the app returns.
Formatted spreadsheets. Some apps format their results: amounts as currency, dates, coloured cells, and a totals row. The totals row stays at the bottom when you sort or filter, and isn’t counted as a row. It always covers every row — while a filter hides some, the count above the table says “totals are for all rows”. Sorting and filters use the value rather than how it’s shown, so > 12000 finds a cell reading $12,500.00.
When you share a report you have filtered, you can start the recipient on the same view. They can change the filters from there — it is where the report opens, not a limit on what they can see, and the page says so.
A formatted document or a PDF.
A chart or image.
Text or structured data.
A Word document or PowerPoint deck, which download rather than preview.

Where the app allows it, IDs and links in tables are clickable and take you straight to the record in the source system — a Salesforce record, a Xero invoice.

Download saves the result to your computer. For a formatted document the button is Save as PDF.

Some apps are dashboards: one page of cards, each showing the latest result of another app. Run one card with its own Run, or every card with Run all — which skips any card that asks for inputs or can change data, so you run those yourself.

History lists your most recent 100 runs, newest first, with the inputs each one carried, when it ran, and how it ended. Open or download any past result from there. For fresh data, run the app again from Apps — you can change the inputs on the way. Every run is just another Run; there’s no separate “re-run”.

If a report looks wrong, check the inputs recorded against it first. A mistyped date or the wrong account code explains most surprising results.

Sharing. From a finished report, click Share and enter someone’s email address. They get a link, but it isn’t a raw file: they must sign in as that exact address, and it opens a protected viewer. Your data stays controlled even after you’ve shared it.

Your administrator decides who you may share with. By default it is only colleagues who could already see that app; a workspace can widen that to anyone in the workspace, or to any email address. A share outside the rule is refused, and the message says why.

If your workspace is managed by a service provider, the same dialog can share the report with your provider, which puts it in their list without an email.

You can share a dashboard the same way — one link, every card. What they see is frozen at the moment you share: the recipient gets the results you were looking at, not whatever runs next week. Share it again to send newer numbers.

If someone shares a report or dashboard with you, the link asks you to sign in as the address it was sent to. If you’re already signed in as someone else, use Sign in with a different account. On a shared dashboard, a card marked unavailable is one whose App isn’t shared with your role — the same as it would look inside the portal.

8. Your profile and security

Open the top-right menu and click your name. Your profile has a tab for each of these:

Details — the name admins see for you across workspaces.
Email — your sign-in identity. Changing it sends confirmation links to both the old and new addresses; the change takes effect only when both are confirmed. Reports shared to your old address won’t open under the new one.
Password — subject to the same rules as §1.
Two-step verification — scan the QR code with any authenticator app and enter the code it shows. Once set up, you’ll be asked for a code each time you sign in.

If your workspace requires two-step verification, setting one up isn’t optional — you can’t reach the workspace until you have. There are no recovery codes: if you lose your authenticator, ask your administrator to reset it, then set it up again.

9. Scheduled runs and email

Your administrator can set an app to run automatically — daily, weekly, or monthly. A scheduled run belongs to whoever set up the schedule, and appears in their History with a Scheduled badge. If one pauses with a question for your role, it arrives in your Inbox.

If your workspace has notifications on, you’ll get an email when a run you started finishes or fails. Your administrator chooses the policy: never, only for runs nobody is watching (scheduled and batch), or every run. Failure emails are separate and are usually on even when success emails are off. A run you cancel never emails you.

Links in those emails point at the in-app result, so you’ll still sign in to view it.

10. When something goes wrong

What you see	What it usually means
A run failed with a message about a limit	The app hit a ceiling your admin set on its cost, its running time, or the number of changes it may make. Tell them — it may need raising, or the app may need narrowing.
A run failed and mentions credentials or a 401	A connection to one of your company’s systems needs re-authorizing. That’s an admin job.
The report shows test or sample data	A data source is connected in Sandbox mode rather than Production. Ask your administrator to switch it — that means disconnecting and connecting it again.
A run was refused before it started	Your workspace has reached a monthly budget, or the app needs a setting it doesn’t have. Your administrator will know.
Everything is visible but nothing can be clicked	You’re in a demo workspace. Demos are see-everything, change-nothing by design.
The table is empty and a filter has an amber note under it	The filter was read as plain text rather than as a comparison — usually a stray character, or an amount the column doesn’t hold as a number. The note says how it was read; the i beside Filters lists the shapes that work.

If a result simply looks wrong, run it again first — then tell your administrator, with the report open. They maintain the apps and the connections.

11. Frequently asked

Can I edit what an app does? No. Apps are built and maintained by your admins or consultants. Ask them for a change, or for a new one.

Why can’t I see something a colleague has? Access is granted per role. Ask your administrator to grant it.

Why does the same app give slightly different results each run? Many apps let the AI decide how to approach the task, so wording and layout can vary between runs even when the underlying numbers don’t. If a report needs to look identical every time, tell your administrator — that’s a choice they can make when building it.

Where did my old report go? In History, which keeps your most recent 100 runs.

Can I see the prompt or code behind an app? No — that’s the point of the builder/runner split. You get a button, a short form, and a result.

Is my data safe? Each workspace is isolated at the database level, connector credentials are encrypted, results are only reachable by signed-in authorized users, and every run and every change is recorded in an audit log.