Connecting your NetSuite account
For the NetSuite administrator who has to approve what gets deployed.
Last updated August 22, 2026
What the connection is
Frontier runs inside your own NetSuite. A chat panel sits on the record you are looking at, with a subtab beneath it. It is installed as a SuiteApp bundle and authenticates as that user, against that account. There is no second application to switch to.
There is no self-serve install. The bundle is not something you find and add yourself — deployment into your account is arranged with Frontier. What that involves for your account is a question to ask before you agree to it.
So this page is not a set of steps to run. It is what the deployment adds, what access it needs, and what to have ready — so you can review it before you agree to it. The step before this one is an invite code: see getting access.
What the deployment adds
- A read-only integration role, for API access.
- A record-level script that adds the chat panel and the subtabs to record pages, plus the browser-side script that draws them.
- A full-page dashboard view, built as a Suitelet.
- A home-page portlet.
- A setup wizard, also a Suitelet, which creates the connection credentials.
- An installation script that assigns the integration role on deploy.
Which record types get the panel, and which subtabs appear, is per-record-type configuration.
What the integration role can read
The role is read-only throughout. It is the narrowest access that does the job, and it is what ships:
| area | access |
|---|---|
| API | REST web services, SOAP web services |
| Lists | customers, vendors, items, employees, accounts, locations, departments, classes, subsidiaries, currencies |
| Transactions | sales orders, invoices, purchase orders, bills, journal entries, inventory transactions |
| Reports | financial statements, balance sheet, P&L, cash flow, trial balance, GL, A/P, A/R |
| Login | Web Services Only — no UI login |
| Payroll | excluded |
How the connection authenticates
The connection uses NetSuite's token-based authentication. Two things are created in your account:
- an integration record, which yields a consumer key and a consumer secret
- an access token, which yields a token id and a token secret
The setup wizard creates both automatically. If anything fails, it falls back to a manual path of three steps — create the integration record, create the access token, connect.
Two different things authenticate, and it is worth keeping them apart. The panel on the record identifies you as the NetSuite user you are already signed in as. The token-based credentials above are how Frontier reads the account.
Setup and configuration require the NetSuite Administrator role. Anyone in another role sees the wizard read-only, with the authentication secrets redacted.
The wizard also carries a health check and a view of what the role can reach.
What to have ready
- Someone holding the NetSuite Administrator role, in the session. No other role can complete setup.
- The record types you want the panel and subtabs on.
- Your invite code.
Whose responsibility this is
You are responsible for the credentials you connect and for the level of access you grant them. Grant the narrowest access that does the job — the read-only, Web Services Only, no-payroll role above is that access, already built.
Your ERP is your system. Frontier does not control it and does not guarantee its availability. This is stated in full in the terms, and how data is handled is in the privacy policy.
