Capabilities
The NetSuite connector supports automatic account provisioning.
This connector does not support account deprovisioning. You must deprovision accounts directly in NetSuite.
Account provisioning
The NetSuite connector supports creating new employee accounts directly from C1. When configuring an account provisioning policy, you can map the following fields.Required fields
Optional fields
Custom fields in account creation
UsecustomFields to set custom employee fields (fields whose script ID starts with custentity) when the employee is created. The value is a JSON object keyed by the field’s script ID, which you can find under Customization > Lists, Records, & Fields > Entity Fields in NetSuite:
YYYY-MM-DD), true or false for checkbox fields, and {"id": "<internal ID>"} for list or record fields. Empty values are skipped. Multi-select fields aren’t supported yet.
Any mapping whose name is itself a custom field script ID (for example, a mapping named custentity_payroll_id) is also sent as a custom field. Script IDs are matched case-insensitively. If the same field is set both ways, the individual mapping takes precedence, unless its value is empty, in which case the customFields value is used.
The connector tells NetSuite to warn about unknown field names instead of rejecting them, so those fields are silently not set. Badly formatted values, such as the wrong type or format for a custom field or date, cause account creation to fail with NetSuite’s error, and references to internal IDs that don’t exist are rejected. If a custom field isn’t populated on the new employee, check that the script ID is spelled correctly, that the field is applied to employee records, that the value uses the right type, and that the connector’s role has Edit access to the field (see Permissions for custom fields).
Setting
department requires the connector’s role to have the Lists - Departments (View) permission, even when you provide an internal ID, because the value is always looked up by name first. Department names and supervisor emails only match active records. Supervisor internal IDs are used directly, without a lookup.Role assignment and login access
giveAccess controls whether the employee can log into NetSuite. skipDefaultRole controls whether the connector assigns the Employee Center role when no roleID is provided.
If roleID is provided, the specified role is always assigned. skipDefaultRole is ignored. Login access is determined by giveAccess.
If roleID is not provided, skipDefaultRole is false (default), and giveAccess is true (default), the connector assigns the Employee Center role automatically. This requires the Employee Center role to exist and be assignable in your NetSuite tenant.
If roleID is not provided and skipDefaultRole is true, no role is included in the create request.
If roleID is not provided and giveAccess is false, no role is included in the create request regardless of skipDefaultRole.
To add
giveAccess, skipDefaultRole, or any of the other optional fields to your mapping, click Add mapping in the Optional mappings section of the provisioning policy configuration.Login Access
The connector surfaces whether an employee can sign in to NetSuite as a dedicated Login Access entitlement. Employees who have login access receive a grant on this entitlement.Login Access only controls whether an employee can sign in. It does not assign or remove roles. Use role grants to control what an employee can do once they can log in.
Revoking the last role
NetSuite does not allow removing the last role from an employee whilegiveAccess is true. If you attempt to do so, the API returns an error.
By default, the connector does not override this restriction. To allow the connector to automatically set giveAccess = false before revoking an employee’s last role, enable the revoke-access-with-last-role flag.
Role permissions
The connector can optionally sync the granular permissions that NetSuite roles confer, with their access level (View, Create, Edit, Full), read from NetSuite’srolepermissions data. This lets reviewers see exactly what a role grants — not just the role name — during a user access review.
When enabled, each distinct NetSuite permission (for example Sales Order or Custom Lists) is synced once as a Permission resource, with one entitlement per access level: View, Create, Edit, and Full. Every role that confers a permission is granted the entitlement matching its access level, and users who hold the role show derived access to that permission level, attributed to the role that confers it. A user holding two roles that confer the same permission at different levels shows both, each attributed to its role.
Because a NetSuite permission cannot be granted or revoked on its own, this derived access is revocable only at the role — reviewing and revoking happens at the role level, exactly as NetSuite enforces it.
The connector syncs access levels only. NetSuite role-level restrictions (employee, subsidiary, and department/class/location restrictions) are not represented — a permission whose scope is limited by a role restriction displays at its base access level.
Permission syncing is off by default. Enable the Permissions resource type when configuring the connector’s sync or an access review campaign. The connector syncs every permission assigned to at least one role (typically a few hundred resources), so enable it when reviewers need permission-level visibility.
Gather NetSuite credentials
Configuring the connector requires you to pass in credentials generated in NetSuite. Gather these credentials before you move on. The connector supports two authentication methods:- Token-Based Authentication (TBA): a consumer key and secret plus a token key and secret.
- OAuth 2.0 client credentials (machine to machine): a client ID, a certificate ID, and a private key. Use this method if your organization requires OAuth 2.0.
Locate your NetSuite Account ID
1
In NetSuite, navigate to Setup > Company > Company Information.
2
Find the ACCOUNT ID field on the page. Make a note of your account ID. We’ll use it in Step 5.
Generate a consumer key and consumer secret
1
In NetSuite, navigate to Setup > Integrations > Manage Integrations. Click New to create a new integration.
2
Give the new integration a name, such as “C1”.
3
On the Authentication tab, select the authentication method:
- For TBA, check the box for TOKEN-BASED AUTHENTICATION.
- For OAuth 2.0 client credentials, check the box for CLIENT CREDENTIALS (MACHINE TO MACHINE) GRANT and, under Scope, check REST WEB SERVICES.
4
Click Save. The new integration is created, and its credentials are shown: the consumer key and consumer secret for TBA, or the client ID and client secret for OAuth 2.0 client credentials.
5
Make a careful note of these credentials (they won’t be shown again). The OAuth 2.0 client credentials method only needs the client ID.
Create a NetSuite role and add it to a user
1
Still in NetSuite, navigate to Setup > Users/Roles > Manage Roles. Click New to create a new role.
2
Give the new role a name, such as “C1 integration”.
3
Assign the following permissions to the role:
- Setup - REST Web Services
- Setup - Log in using Access Tokens (TBA only)
- Setup - Log in using OAuth 2.0 Access Tokens (OAuth 2.0 client credentials only)
- Setup - Bulk Manage Roles
- Reports- Suite Analytics Workbook
- Lists - Employee Record
- Lists - Employees
- Lists - Departments (only if you use the
departmentaccount creation field)
4
Click Save.
5
Next, assign the new role to a user. You might want to create a new user for this purpose rather than assigning the role to an existing user. Navigate to Lists > Employees > Employees, then search for the employee by email.
6
Click Edit next to the name of the employee you want to assign a role to.
7
Click the Access subtab.
8
In the Role field, select a role for this employee.
9
Click Add.
10
Click Save.
Generate a token key and token secret
1
In NetSuite, navigate to Setup > Users/Roles > Access Tokens. Click New to create a new token.
2
Select the application (integration), role, and user you created in the previous steps, and give the token a name.
3
Click Save. The new token is created, and its key and secret are shown.
4
Make a careful note of these credentials (they won’t be shown again).
Set up OAuth 2.0 client credentials
Skip this section if you’re using TBA.1
On your computer, generate a certificate and private key. NetSuite accepts RSA keys of 3072 or 4096 bits, or EC keys on P-256, P-384, or P-521, and certificates valid for up to two years. For example:Keep
private.pem secret. You’ll paste its full contents into C1.2
In NetSuite, navigate to Setup > Integration > Manage Authentication > OAuth 2.0 Client Credentials (M2M) Setup. Click Create New. This page requires the OAuth 2.0 Authorized Applications Management permission, which the Administrator role has.
3
Select the user (entity), the C1 integration role, and the application (integration) you created in the previous steps, and upload
public.pem.4
Click Save. Make a note of the Certificate ID shown for the new mapping.
Sandbox refreshes clear the setup. NetSuite doesn’t copy the OAuth 2.0 client credentials setup to sandbox or Release Preview accounts, and a sandbox refresh removes it. Repeat this section in each account you connect.
Configure the NetSuite connector
- Cloud-hosted
- Self-hosted
Follow these instructions to use a built-in, no-code connector hosted by C1.Done. Your NetSuite connector is now pulling access data into C1.
1
In C1, navigate to Apps > Connectors and click Add connector.
2
Search for NetSuite and click Add.
3
Choose where to add the connector: Create a new app, or Add to an existing app (then select the app).If you’re creating a new app, choose whether to link it to an application discovered from your identity provider: select Yes and pick the IdP application, or No to continue with just the connector.
4
Set the connector’s Name and, optionally, a Description.
5
Click the pencil icon next to Owners to choose who can configure and manage this connector.
6
Click Add. The connector is created and its configuration page opens.
7
Find the Settings area of the page and click Edit.
8
In the Account ID field, enter your NetSuite account ID as shown under Setup > Company > Company Information (for example,
1234567, or 1234567_SB1 for a sandbox). Don’t enter the domain (1234567-sb1.suitetalk.api.netsuite.com): the connector rejects account IDs that contain dashes.9
Select the authentication method you set up and enter its credentials:
- Token-Based Authentication: enter the Consumer key, Consumer secret, Token key, and Token secret you generated.
- OAuth 2.0 Client Credentials: enter the integration’s client ID in OAuth 2.0 Client ID, the OAuth 2.0 Certificate ID, and the full contents of
private.pemin OAuth 2.0 Private Key.
10
(Optional) In the Custom Employee Fields field, enter a comma-separated list of custom employee field IDs to include in the sync (e.g.
custentity_zone,custentity_cost_center). See Custom Fields for details.11
Click Save.
12
The connector’s label changes to Syncing, followed by Connected. You can view the logs to ensure that information is syncing.
Custom Fields
The NetSuite connector supports syncing custom employee fields. Custom field values are added to the user profile attributes in C1, making them available for access reviews and reporting.Finding custom field IDs
Custom field IDs can be found in NetSuite under Customization > Lists, Records, & Fields > Entity Fields. The field ID is shown in the ID column (e.g.custentity_zone).
Permissions for custom fields
Each custom field in NetSuite has its own field-level access controls, separate from the base employee record permissions. The connector’s role must have at least View-level access to each custom field being synced. Field access is configured per-field in NetSuite:- Navigate to Customization > Lists, Records, & Fields > Entity Fields.
- Click on the custom field.
- Go to the Access subtab.
- Ensure the connector’s role has View, Run, or Edit access. To set the field when creating accounts (see Custom fields in account creation), the role needs Edit access.