Netridium — User Guide

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

A Service Item 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 items 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 two parts.

• Pinned items at the top, grouped into their folders. Pinning is per-person, so this list is yours alone — see §3.
• Service Items and History at the bottom. (Admins see more links here; if you don't have them, you're not an admin.)

Service Items is your catalog and your viewer in one page. History is the record of runs.

3. Finding and running a Service Item

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

To run one:

1. Click Run.
2. 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.
3. 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.
4. If it has neither, it starts right away.

Pin an item (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:

You can move around the app — open another item, 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.

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

5. Items that can change data

Most Service Items 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. Where the item 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 exactly as you typed it.

If you're unsure what an item 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 item you'll see:

• A spreadsheet, with one tab per sheet and a search box that filters the sheet you're looking at.
• 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 item 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.

7. History, re-running, and sharing

History lists the runs you've made, newest first, with the inputs each one carried, when it ran, and how it ended. Open any past result, or run the item again for fresh data — 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 (or sign up) as that exact address, and it opens a protected viewer. Your data stays controlled even after you've shared it.

If someone shares a report 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.

8. Your profile and security

Open Profile from the top-right menu.

• Your details — the name admins see for you across workspaces.
• Email address — 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.
• Change 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. If you lose your authenticator, your administrator can't read your codes; ask them to help you re-enrol.

9. Scheduled runs and email

Some items run automatically — daily, weekly, or monthly. Those appear in History with a Scheduled badge.

If your workspace has notifications on, you'll get an email when a run 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

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

11. Frequently asked

Can I edit what an item does? No. Items 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 item give slightly different results each run? Most types 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. Search or scroll to find it.

Can I see the prompt or code behind an item? 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.