NetSuite administrator setup guide
Connect NetSuite with a certificate
Start in your sandbox. An administrator sets up the NetSuite role, user and integration; a Carbon Ink workspace admin saves the Client ID and activates the certificate. Keep this guide open alongside both applications. You can share this guide with your NetSuite administrator.
Certificate setup does not need a Client Secret, redirect URI or browser authorization. If you already have a working connection, use the same integration record and Client ID.
1. Enable the NetSuite features
Open Setup → Company → Enable Features. Under SuiteCloud, enable REST Web Services and OAuth 2.0. Under Analytics, enable SuiteAnalytics Workbook. Save your changes. Token-Based Authentication is not required.
2. Create the integration role and user
Open Setup → Users/Roles → Manage Roles → New. Use Classic Center and this suggested name:
Add the permissions below. Keep subsidiary, employee and location restrictions aligned with the data your team should access. Do not assign the Administrator role to the integration user.
Starting permissions for catalog sync and the invoice pilot Tab / permission Level Used for Setup → REST Web Services Full Connection and REST access Setup → Log in using OAuth 2.0 Access Tokens Full OAuth 2.0 access for the integration user Reports → SuiteAnalytics Workbook Edit SuiteQL reads Lists → Customers View Customer sync and activation check Lists → Items View Catalog sync Lists → Employees View Sales rep mapping Lists → Price Levels View Pricing Lists → Currency View Currency data, when enabled Lists → Locations View Inventory locations, when enabled Lists → Subsidiaries View OneWorld accounts, when enabled Lists → Units View Multiple Units of Measure, when enabled Transactions → Find Transaction View Invoice setup and transaction evidence Transactions → Invoice Create When using the direct Invoice workflow Transactions → Cash Sale Create Only when using the Cash Sale workflow Grant only the transaction type you will test. Returns, credits, load orders and custom workflows may need additional permissions agreed during their setup. Custom fields and account restrictions can also affect access.
Create or select a dedicated, active integration employee/user under Lists → Employees → Employees. Enable access as required by your account and assign the role above. Suggested name:
Use an internal email address you control. Carbon Ink does not need this user’s password.
3. Create the integration and save its Client ID
Open Setup → Integration → Manage Integrations → New. Name it Carbon Ink and set State to Enabled.
- Check Client Credentials (Machine to Machine) Grant.
- Select the REST Web Services scope.
- Leave Authorization Code Grant, Public Client and Token-Based Authentication unchecked for a new certificate-only integration.
- No redirect URI is needed for this path. Preserve existing settings if this integration already has a working browser connection.
Save and copy the Client ID from the confirmation page. NetSuite may also display a Client Secret; Carbon Ink does not need it for certificate setup. Never send credentials by email or paste them into support chat.
In Carbon Ink, enter this account’s ID (for example
1234567_SB1), then save the Client ID in the connection form.4. Download and map the certificate
In Carbon Ink, choose Generate certificate and download the .pem file. Only the public certificate is downloaded; its private key stays on Carbon Ink servers.
In the same NetSuite account, open:
Choose Create New. Select the integration user, role and Carbon Ink application from the previous steps. Upload the downloaded certificate and save. Copy NetSuite’s Certificate ID.
If the application is missing, check that its Machine to Machine grant is enabled. Creating this mapping requires an administrator or a user with OAuth 2.0 Authorized Applications Management permission; this is a setup permission for the person configuring NetSuite.
5. Activate and check the result
Paste the Certificate ID into Carbon Ink, choose Save ID, then Activate. Carbon Ink verifies the certificate and performs a read-only customer query before marking the connection active. Failed verification preserves any previous connection.
A successful activation proves authentication and that customer read check. It does not prove every permission or authorize invoice writes. Continue with catalog sync, field mapping and the guided sandbox invoice test. Review the actual accounting and inventory effects before approving the pilot.
If the certificate is rejected, confirm the account, Client ID, certificate mapping, user and role all belong to the same environment. If the customer read fails, review the features, permissions and restrictions above. Retry temporary outages; contactsupport@carbonink.app if you remain blocked.
Going live and keeping access working
Use the same process in Carbon Ink’s production setup panel with the production account’s own integration and certificate mapping. Sandbox mappings do not transfer to production. Sandbox refreshes clear certificate mappings, so repeat setup after a refresh. Certificates expire; generate and activate a replacement before the expiry shown in Carbon Ink. Activating a connection does not switch tablets to production.
Browser authorization fallback
If certificate setup is blocked, open Use browser authorization instead in Carbon Ink. On the same NetSuite integration, enable Authorization Code Grant, keep REST Web Services selected, leave Public Client unchecked, and add this exact redirect URI:
The signing-in user’s role needs Log in using OAuth 2.0 Access Tokens in addition to the applicable data permissions. Save the Client ID and Client Secret directly in Carbon Ink’s fallback form, then authorize through NetSuite.
NetSuite shows the Client Secret only when generated. If you no longer have it, involve your administrator before resetting credentials: resetting can interrupt existing connections. Browser authorization normally needs renewing after about seven days. Certificate setup remains available later.
NetSuite references: integration records, certificate mapping, REST prerequisites.
Return to connection setup