Implementation Guide

NetSuite Activity Monitor — Setup

Self-hosted and config-driven. You run this on your own server, against your own NetSuite account. Nothing here is shared with anyone else's deployment.

1 NetSuite side

Upload Retrieves System Notes Log.js (included in your download) as a new Script File in your account.
Create a Script record (type RESTlet) pointing at it, then a Deployment, status Released. Note the Script ID and Deploy ID — you'll need both for step 2.
Setup > Users/Roles > Access Tokens: create an Integration record + Access Token for the role that will run this. Note the Consumer Key/Secret and Token ID/Secret.

Role permissions

The role needs, View only — this app never writes anything to your NetSuite account:

Setup tab → REST Web Services — required to execute the RESTlet at all.
Transactions tab, View, for every transaction type you want to track: Sales Order, Invoice, Credit Memo, Purchase Order, Vendor Bill, Vendor Payment, Customer Payment, Work Order, Work Order Issue, Work Order Completion, Item Fulfillment, Item Receipt, Inventory Adjustment, Inventory Transfer, Check. The RESTlet's SuiteQL joins SystemNote to the transaction table, so this permission gates that join as well as the transaction lookup — not just cosmetic.
Lists tab → Subsidiaries, View, for every subsidiary you want activity from.
Least privilege: View, not Full/Edit/Create — this role only reads.

Not fully isolated in testing: whether System Notes visibility needs anything beyond the Transactions access above, or follows from it automatically. Verify against your own role rather than assuming.

Look up each subsidiary's internal ID (Setup > Company > Subsidiaries, or check the URL when viewing one) — you'll need these for config.json.

2 Server side

# create a directory and copy in the downloaded files:
# dashboard-server.js, dashboard.html, config.json, package.json,
# .env.example, and the lib/ folder
mkdir -p activity-monitor
cd activity-monitor
npm install

cp .env.example .env
# edit .env: fill in NS_ACCOUNT_ID, NS_CONSUMER_KEY, NS_CONSUMER_SECRET,
# NS_TOKEN_ID, NS_TOKEN_SECRET, NS_NETSUITE_GATEWAY_ID from step 1

nano config.json
# replace "REPLACE_WITH_YOUR_ACCOUNT_ID" in accountDomain
# replace each "REPLACE" subsidiary key with your subsidiary's
# internal ID, and update the labels to match your own subsidiaries

Run it:

node dashboard-server.js
# should log: [dashboard] serving on http://localhost:<DASHBOARD_PORT>

Optional — keep it running across reboots with a process manager such as pm2:

pm2 start dashboard-server.js --name activity-monitor
pm2 save

3 Verify

Console output should show a clean startup: N subsidiaries loaded from config.json.
Open http://<your-server>:<DASHBOARD_PORT> (or put it behind your own domain / reverse proxy).
Click Check. If it fails, the error message and server console will show the actual NetSuite error — almost always a missing role permission from step 1.