NetSuite Account Presence

NetSuite Account Presence - Stop colliding with your team on shared NetSuite logins. NetSuite Account Presence is the ultimate tool for consulting teams to manage shared access seamlessly. See exactly who is active in an account—and from which IP address—before you even sign in. Built for Multi-Client Teams If you support several NetSuite customers, you can create one client profile per customer. Simply switch clients in the popup to keep claims isolated and organized. Connect each profile securely to that specific customer’s sync target (such as a NetSuite RESTlet using OAuth 2.0, or JSONBin). Flexible Sync Options - NetSuite RESTlet (OAuth 2.0): Recommended for secure, customer-specific environments. - JSONBin.io: The fastest and easiest shared setup for small, agile teams. Getting Started & Support - Setup Instructions: https://www.canariawerx.com/netsuite-presence-setup <========= - Need help? If you run into any trouble during setup, the developer is highly responsive and ready to help you get started: https://www.canariawerx.com/#contact Key Features - Claim & Release: Easily claim or free up a shared NetSuite account directly from the extension popup. - Real-Time Visibility: See exactly who holds each account, along with their public IP address. - Smart Auto-Claim: Optionally set the extension to automatically claim an account the moment you open a NetSuite URL. - Client Profiles: Support multiple customers seamlessly by creating distinct profiles, each with its own account list and sync target. - Automated Maintenance: A built-in heartbeat refreshes active claims, while stale claims are automatically cleared roughly 10 minutes after Chrome is closed. Changelog [1.3.4] — 2026-08-20 Added - **Auto-release on leave** — when no open tab matches your claimed account, the claim is released automatically (tab close, navigate away from NetSuite, or heartbeat). Toggle in Settings: *Auto-release when I leave NetSuite or close the tab* (default on). [1.3.3] — 2026-08-19 Fixed - **All claims pinned** — every known claimed account (yours and teammates) appears above the search box so they stay visible with large account lists. - **Unknown NetSuite IDs are not tracked** — auto-claim, heartbeat, and presence sync ignore unlisted hosts and listed rows with no account ID; leftover unknown presence keys are dropped. [1.3.2] — 2026-08-19 Changed - **Release in context** — the Release button moved from the header into the pinned **Currently active** / **Currently claimed** cards. - **Pinned current tab** — when the active tab matches a known listed account, it appears above the search box as **Currently active** (with claim / take-over / release as appropriate). - **No box for unknown IDs** — unlisted NetSuite tabs or claims without a known account ID no longer show a pinned card. [1.3.1] — 2026-08-12 Fixed Accounts no longer wiped by heartbeats — claim/release/heartbeat sync now preserves the account list when a remote read returns empty (race during Restlet rewrite, transient file miss, or parse failure). Empty remote pull does not clobber local accounts — unless the shared state has an intentional accountsClearedAt marker from an explicit empty Save. Settings empty-save guard — clearing all accounts requires confirmation after a fresh sync check. Changed Companion Restlet 1.2.8: refuses empty account overwrites while a state file exists; keeps existing accounts on presence-only saves; supports clearAccounts + accountsClearedAt for intentional clears. Re-upload cw_presence_sync_restlet.js on each customer NetSuite. [1.3.0] — 2026-08-08 Added Silent OAuth refresh on browser startup — when Chrome starts (or the extension is installed/updated), NetSuite RESTlet (OAuth 2) profiles that already have stored tokens are refreshed in the background with no UI. Reconnect notification — if silent refresh fails (expired/revoked refresh token or other OAuth error), a Chrome notification titled “Reconnect to NetSuite” is shown. Clicking it opens Settings so you can Connect again. Notes Profiles that were never connected (no stored access/refresh token) are skipped — no notification spam. Presence claim expiry (~10 minutes without heartbeat) is unchanged and separate from OAuth token refresh. [1.2.9] — prior Previous Web Store / local release baseline before startup OAuth ensure.