The Re-Leased Integration Role in Oracle NetSuite controls what records the integration can access. If your NetSuite environment uses custom records, custom fields, or has been modified since initial setup, the integration role may need additional permissions to sync successfully.
How to Identify a Permission Error
Permission-related sync errors appear on the Sync Results page in Re-Leased. The error message identifies which permission is missing — such as a custom record name, transaction type, or field. Read the error details carefully before making changes.
Step 1: Navigate to Manage Roles
In NetSuite, go to Setup > Users/Roles > Manage Roles.
Step 2: Edit the Re-Leased Integration Role
Locate Re-Leased Integration Role in the list and click Edit.
Step 3: Add the Missing Permission
Click the Permissions tab and select the appropriate sub-tab:
Transactions — invoices, payments, credit notes.
Reports — report access.
Lists — customers, vendors, items.
Setup — configuration permissions.
Custom Record — custom record type permissions.
To add a custom record permission: click the Custom Record sub-tab, select the record type from the dropdown, set the Level (typically Full for read/write or View for read-only), and click Add.
Step 4: Save and Re-Sync
Click Save to apply the changes.
Return to Re-Leased and run a sync — navigate to the Sync icon and click Start Sync.
Clearing Remaining Errors After Syncing
Some errors may remain on the Sync Results page after adding permissions. If a record no longer needs to sync, select it and click Unlink Records to remove it from future sync attempts.
Common Permission Types
Custom Records — when NetSuite uses custom record types for invoices, contacts, or synced entities.
Custom Segments — when custom segments are used for tracking on transactions.
Subsidiaries — ensure all relevant subsidiaries are accessible if restrictions are set.
Transaction Types — explicit permission needed for custom transaction types.
Still Having Issues?
Verify the permission was saved with the correct access level.
Confirm the permission matches what the error message specified.
Check that the Re-Leased Integration Role is still assigned to your integration user under Setup > Users/Roles > Manage Users.
If the issue persists, contact our Customer Support team.