Company Manager Guide

For MSPs, accounting firms, and consultancies who use the Company Manager to build, deliver, and govern Apps across many companies from one place.

The model in one line: your firm builds a capability once and delivers it to every company you manage — each one a fully isolated workspace, all run from a single console. Your staff have full admin access to every company you manage, so you can set up and operate a company’s AI assets on their behalf.

This guide covers the provider role. For what you do inside a company’s workspace — building apps, connectors, roles, limits, budgets — see the Admin Guide; that document is the reference for everything a company’s own admin can do, and as provider staff you can do all of it.

1. How the tiers fit together

Tier	Who	What they do
System Manager	Netridium, the platform operator	Runs the platform — the OAuth apps behind each connector, the products (plans) and what each one entitles, model pricing, and platform safeguards. You request these; you don’t set them.
Company Manager	Your firm’s provider workspace	Create and manage the companies you serve, publish your catalog to them, manage your staff, and operate each company’s AI assets. This is the console this guide covers.
Client — your console calls them Companies	Each company you manage	An isolated workspace with its own connectors, Apps, users, roles, results, and settings.

You work inside each company’s workspace. Your firm’s console is for managing them. The actual AI assets live in each company’s workspace, and you build and manage them by opening that company. Your own provider workspace has no Apps of its own — with one exception: the Catalog (§6), which is a library of apps, not a place they run.

2. Your console

Signing in to your firm’s workspace shows a header reading “Company Manager” — or whatever you renamed it to (see below) — and these nav apps:

Nav app	Purpose
Companies	The companies your firm manages. Your home screen.
Shared	Reports and dashboards those companies have shared with you, newest first.
Catalog	Your library of Apps and where each one stands across your companies. (plan-gated)
Users	Your firm’s own staff.
Audit Log	Meaningful actions taken in your firm’s workspace.
Settings	Your firm’s company profile, and what this console is called.

Call it what your firm calls it. “Company Manager” is our name for this console, and it is not the word every firm uses — a private equity firm manages a portfolio, and an MSP manages clients. Settings → General → Console Name changes it: type “Portfolio Manager” and that is what the header and the browser tab say, for everyone in your firm. Clear the field to go back to the default.

It renames your console and nothing else. Your companies’ own workspaces are untouched — they keep the neutral wording about their service provider, so nobody has to learn your firm’s internal vocabulary to read their own settings.

Bookmark /clientmanager. Signing in lands you on your console, but the page’s own address contains your firm’s workspace ID, which isn’t memorable. /clientmanager always resolves to your Companies list. It asks you to sign in first if you aren’t.

Shared

Shared is the list of reports and dashboards your companies have pointed you at. Someone at a company opens a finished report or a dashboard, clicks Share, and picks their provider; it appears here with the company’s name, who shared it and when. Open takes you straight to it in their workspace.

It is a shortcut, not an inbox you depend on. You can already open any of your companies and read every report in it — sharing just saves you hunting for the one they meant. So an empty Shared list never means there is nothing to see.

Two things move rows out of it. A company that switches Settings → Security → Service Provider Access off disappears from this list entirely, along with your access to its workspace — and reappears, shares intact, if it turns access back on. And anyone who shared a report can Unshare it, which removes the row without changing what you can see.

3. Onboarding a new company

Companies → New company:

Field	Notes
Name	Required. The company name shown inside its own workspace.
Admin email	Required. An invitation is emailed here — the company’s first admin.
Product	The plan assigned to the company. This is what decides their entitlements — see §7.
Mode	Prod, Sandbox, Demo, or Trial.
Address, phone, notes	Optional profile details.

On save, Netridium creates an isolated workspace linked to your firm, creates its built-in Admin and User roles, and emails the admin invite.

You don’t have to wait for the company to accept — your staff already have admin access and can start setting it up immediately.

Modes. Prod is a normal live workspace. Sandbox is an internal label with no distinct behaviour the company sees. Trial carries a countdown badge and drives the in-product upgrade prompt. Demo puts the company’s non-admin users into a see-everything, change-nothing experience — every page opens, every save, add, delete and run control is inert, and the Users and Audit Log pages are blocked outright because demo signups share one workspace. Demo and Trial workspaces can’t buy usage credits.

4. Working inside a company

Each row on Companies shows its name, its primary admin’s name and email, its mode, and its status, with these actions:

Open — enters the company’s workspace in a new tab. You land with full admin access and can do anything its own admin can.
Edit — the company’s profile (name, product, mode, address, phone, notes), plus Delete. The admin email is shown but fixed once the company is created.
Suspend / Activate — pause or resume a company without deleting anything.
Reopen — for a workspace that has been closed. Use this rather than Activate: activating alone would leave the company’s closure request standing.

Inside an opened company you get the full workspace sidebar: Inbox, Apps, History, Usage, Audit Log, Users, Roles, and Settings. The Inbox there holds that company’s paused runs; as an admin you can answer any of them.

The Companies list can be searched and sorted by any column.

View as. While inside a company, the header carries a View as switcher that renders the workspace as one of its roles, or as if it were in Demo mode. Both reduce your privileges, so it’s a safe way to check what a company’s users actually see before you hand something over. Your full access clears it.

Privacy. A company can deny your access from its own Settings → Security, or grant it for a set number of hours. Its own team’s access is never affected. If a company’s workspace stops opening for you, that’s the first thing to check.

5. Connecting a company’s systems

Every company connects its own accounts; credentials are encrypted and never shared across workspaces. Open the company → Settings → Connectors.

Connection cards — one-click OAuth for Xero, QuickBooks Online, and Salesforce. QuickBooks and Salesforce require an explicit Production or Sandbox choice per connection, with no default.
Add connector — Maxio, NetSuite, and HubSpot.
Which types are offered depends on that company’s product. Connectors they already have keep working even if the plan later narrows.

Some connectors need a one-time platform OAuth-app setup by the System Manager. If Connect errors with “… OAuth isn’t configured”, that’s what’s missing — ask Netridium.

Step-by-step setup for each provider is in the Admin Guide.

6. Build once, deliver to many

This is the heart of the Company Manager model, and there are two ways to do it.

6.1 The Catalog (plan-gated — the recommended route)

The Catalog is your firm’s library of Apps and a live picture of where each one stands across your companies.

Getting an app into the catalog. Open a company, build and test the App there, then click Add to catalog in the editor toolbar. Your catalog starts empty by design — apps are authored in a real workspace against real connectors, not in the abstract.

Versions. A catalog item carries a version. A new entry sits at Draft until you click New version, which freezes it as v1. Companies receive versions, never the draft — the Publish button stays disabled while an app is still a draft. To cut the next version, edit the source app, click Add to catalog on it again to refresh the catalog’s draft, then click New version. The catalog recognises the app by its folder and title, so keep those the same; a renamed app arrives as a second catalog item.

Publishing. Click Publish, tick the companies that should have it, and either Check (what would happen, changing nothing) or publish for real. The dialog tells you where each company stands: currently on v2, not published here yet, withdrawn, detached, or last skipped with the reason. Only active company workspaces are listed — publishing into a suspended or closed one would silently change nothing.

The catalog table shows, per app: its type, the connector types it Needs, its version, and the rollout — e.g. “7 on v3, 2 behind”. That count is companies that have the app installed. A company that was skipped is exactly the one you need to see: open Publish, where it is listed with the reason. Delete removes an app from the catalog.

What the company sees. A published app appears in their workspace with a Managed badge and can’t be edited there — the lock is enforced in the database, not just the UI. The banner in its editor names your firm and the version.

On a plan with LogicScript versions and approval, a published LogicScript is not live until it is approved. In a company whose plan has that option, a LogicScript arrives in the company’s workspace as a draft. An admin of that workspace — or you, working in it — reviews it and clicks Approve on the app’s edit page. Until then the company keeps running the version it last approved, and a LogicScript published there for the first time cannot be run at all. The publish result says so beside each company. Other app types are live as soon as they are published.

Detach and Withdraw. A company can Detach a managed app: they keep it exactly as it is and can then edit it freely, but it stops receiving your updates. You can Withdraw a publication from your side. Neither destroys the company’s data.

Your own staff never see a Detach button on an app they maintain — offering it would invite quietly severing a company’s app from the library it lives in. Use Withdraw from the Catalog console instead.

6.2 Export / import

The older, manual route, still useful for bulk moves and for companies on a plan without the Catalog. Inside a company’s Apps page, tick rows and Export to a portable JSON file, then Import it into another workspace.

Connectors are referenced by name and type, not internal IDs, so they re-link in any workspace. Anything missing is reported rather than failing the import — set it up, or rename the connector to match.
Each app carries a stable id, so a workspace recognises an app it already has. Import shows you what it would do before writing anything: new apps are created, and an app already present is only overwritten when you choose Replace. Replacing updates in place, so its schedules, role grants, favourites and run history survive.
A raised run limit, or a change to Allow Updates, is shown and must be confirmed. A file cannot quietly arm writes or lift a ceiling. A LogicScript that updates another system but arrives with Allow Updates off is skipped, with the line that updates named.
An app of a type the destination’s plan doesn’t include is skipped, as is one managed by a provider catalog — ask them to publish an update, or Detach it first.
An app with no id — an older export, or a file authored by hand — is always imported as a new app. Re-importing an older file therefore creates copies rather than skipping them; the preview lists exactly what would be created, so you can stop before it happens.

Keep a template company. Because apps are authored inside company workspaces, many firms keep one Sandbox or Demo company as a build-and-stage library, then publish or export from it.

7. Governance: who sets what

Most of a company’s configuration happens inside its workspace, where you act as an admin. A few things are decided by the product you assign, and a few are Netridium’s alone.

Setting	Where	Set by
Build / edit Apps, import & export	Company → Apps	You, or the company’s own admins
Connectors and per-connector Allow Updates	Company → Settings → Connectors	You, or the company’s admins
Roles and per-app View / Run	Company → Roles	You, or the company’s admins
Users, invitations, approval	Company → Users	You, or the company’s admins
Notifications	Company → Settings → General	You, or the company’s admins
Run limits (every plan), Budgets, Cost centers	Company → Settings	You, or the company’s admins
Two-step for every member (a company’s admins always use it)	Company → Settings → Security	You, or the company’s admins
The company’s own Anthropic key	Company → Settings → Billing	The company, or you on their behalf
Which product a company is on	Your console → Companies → Edit	You
What a product entitles — roles, LogicScript (and its versions and approval, parameters, and Flow view), Dashboards, scheduling, Skills, SSO, budgets, cost centers, catalog, BYOK requirement, allowed connector types	System Manager → Products	Netridium
Platform OAuth apps, model pricing, platform safeguards	System Manager	Netridium

The product is the lever

Nearly every capability question — “can this company use LogicScript?”, “can they use Skills?”, “can they set budgets?”, “must they bring their own AI key?” — is answered by the product assigned to that company. You choose the product; Netridium defines what each product includes.

Two consequences worth internalising:

BYOK is a property of the plan, not the company. There used to be a per-company “Require BYOK” checkbox on the Edit screen. It was removed: having the same policy settable in two places by two roles, with neither able to waive the other, was a trap. To change a company’s BYOK status, move them to a product that requires it. They still enter their own key in their Settings → Billing.
A plan that requires BYOK holds the company at the door. Until one of their admins saves a key, everyone in that company lands on an Add your Anthropic API key page and nothing runs. You and Netridium can still open the workspace to set it up. Turning the requirement on for a product applies at once to every company on it that has no key.
Skills follow from it; updates do not. A company can attach an Agent Skill only if their plan requires their own Anthropic key. Allow updates is available on every plan: a company on Netridium’s key runs updating Apps on its usage credits.

Run limits and the two-step requirement are on every plan. Entitlements that gate configuration only — budgets, cost centers, the catalog — never stop enforcement. Moving a company to a plan without budgets strands their existing budget; it doesn’t uncap their month.

8. Publishing apps to a company’s users

End users should see only what’s meant for them. Inside a company:

Roles (where the company’s plan includes roles; without them every user is an admin) — create roles (“Finance”, “Sales”) and, per role, choose which Apps its members can see (View) and run (Run). Run requires View. The built-in Admin role runs everything.
Users — invite by email and assign a role. New members can be required to be approved before they gain access, and can be disabled later without losing their history.

A company’s admins sign in differently from its other users, on every plan:

Every admin uses two-step verification. A new admin is asked to set up an authenticator the first time they sign in. If one loses it, you or another of the company’s admins can reset it under Company → Settings → Security; a company with a single admin and no provider on hand asks Netridium support.
Admins always sign in with a password, even where the company requires single sign-on, and an account that signs in through the company’s identity provider can’t be made an admin. Removing an admin from the identity provider does not remove them here: untick Active under Company → Users.

Change or revoke a role and it updates for everyone in it at once. Users never see the prompt or the code behind an app.

Test before you hand over. Run the app yourself — for a LogicScript that updates another system, use Dry run first — use View as to confirm what the target role sees, then grant Run.

9. Managing your firm’s staff

Users manages your own team.

Invite a teammate by email; they set a password and join. Pending invitations can be resent or revoked.
Everyone on this list is an admin of your firm and of every company you manage. There are no per-app roles for staff — firm-wide access is what makes “open any company and manage it” work. Add staff deliberately.
Active — untick it to cut a teammate off from your firm and from every company you manage, without removing them; tick it to let them back in. You can’t untick yourself, or the last active user.
The list shows who has set up two-step verification. Because your staff hold admin over every company, this is the column worth keeping all ticks.

Note that your staff’s access can be bound by two separate two-step mandates — Netridium’s operator mandate over provider staff, and the requirement any company you manage sets in its own Settings → Security, which applies to your staff when they open that company. Either is enough to compel it.

10. Monitoring, cost, and audit

Per-company Usage. Open a company → Usage for runs, tokens, and cost over a date range, broken down by folder, App, cost center, and user. The amounts are what appear on that company’s invoice.
Per-company History. The most recent 100 runs with their inputs, result, and outcome; exportable to CSV.
Cost control. Set Run limits (per run) and Budgets (per calendar month) inside each company. Both are the company’s own controls too — agree who owns them.
Audit. Your firm’s console and every company workspace each keep their own audit trail, with CSV export.
Netridium’s own safeguards sit behind all of this: a per-workspace daily spend ceiling that warns and then auto-pauses, and a platform-wide circuit breaker. You don’t configure these, but a company that has been auto-paused is a case to raise with Netridium rather than debug as a broken connector.

11. Company lifecycle

Suspend / Activate — pause a company (non-payment, an offboarding in progress) and resume later without losing anything.
Delete — permanently remove a company and all of its data, from its Edit screen. This cannot be undone; suspend instead if you only need to pause access.
Closure by the company. A company’s own admins can close their workspace from Settings → Account. You can’t do it for them, and you can’t undo it — but you can Reopen a closed workspace from the Companies list.

12. What to ask Netridium for

Need	Why it’s operator-level
A product that includes LogicScript, Dashboards, scheduling, Skills, SSO, budgets, cost centers, or the Catalog	Products define what a plan entitles; you assign them, Netridium defines them.
A product that requires BYOK	It’s the precondition for Skills, it holds a company until its key is saved, and it’s a plan property.
OAuth app setup for a connector (Xero, QuickBooks, Salesforce)	The platform’s connection apps are registered once by the operator; companies then authorize their own accounts through them.
Adding a connector host to the approved list	MCP hosts are staff-managed for SSRF protection.
Notification sender address and email templates	A platform setting.
Model pricing and tier mapping	Platform-level, so a tier can move to a newer model without touching anyone’s apps.
Investigating an auto-paused workspace	Reset of a daily spend cap is deliberately manual.
A copy of a demo or trial company	Duplicating a workspace is done by Netridium, and only for Demo and Trial workspaces.

Admin Guide — everything you do inside a company’s workspace. The main reference for building and governing Apps.
User Guide — for the end users who run what you build.
LogicScript — the language reference.