Completing Account Setup for SuiteSignOn

After you have finished Installing a SuiteSignOn Bundle in your account, you must complete a few additional setup tasks in NetSuite.

The bundle documentation file should include instructions for these tasks. If you have not yet reviewed this file, go to Customization > SuiteBundler > Search & Install Bundles > List, and on the Installed Bundles page, click Documentation.

You should follow the instructions in this file. The following list describes tasks that are likely to be included in this file:

  1. Go to Customization > SuiteBundler > SuiteSignOn, click the link for the newly installed SuiteSignOn integration, and verify that the SuiteSignOn page looks correct. The bundle documentation should include a checklist or a screenshot for you to use for this purpose.

  2. Make changes to the SuiteSignOn page as necessary. You must have the SuiteSignOn permission to edit SuiteSignOn records.

    • If your account ID for the application provider is required for identification, enter it in the Partner Account field. This value is not necessary if the integrated application does not use it for identification. The bundle documentation should indicate whether this value is required.

    • If you want to control the level of NetSuite access for SOAP web services callbacks from integrated applications, change the Web Services Access option. The following options are available:

      • Same as UI Role - the default, which allows SOAP web services callbacks from integrated applications with the same level of permissions as in the user interface integration.

      • No Access - prevents integrated applications from accessing NetSuite through SOAP web services callbacks.

      • Additional options for any SOAP web services only roles in the account - selecting one of these roles allows SOAP web services callbacks from integrated applications, but limits access to the permissions levels assigned to the selected role.

      As a security best practice, you should provide the minimum level of access required for SuiteSignOn integrated applications. For example, if an application only requires user interface integration, it is best to set the Web Services Access option to No Access.

      You can view and edit this field on the SuiteSignOn list page at Setup > Integration > SuiteSignOn.

      Important:

      Be aware that changing the Web Services Access option could possibly break an integration, because it may depend on existing user permissions.

    • If the bundle includes custom fields to be used as user identification, ensure that they appear on the User Identification subtab and are checked. The bundle documentation should indicate whether these fields are included.

      Be aware that the names of bundled custom fields may be changed slightly from those listed in the bundle documentation, if any of their IDs conflict with preexisting custom fields in your account. If a conflict is detected, the bundled custom field ID is appended with “_#”. For example, if a bundle installs a custom field with an ID of custentitybanana and a preexisting custom field has the same ID, the bundled field ID is changed to custentitybanana_2. This field ID also is changed where it is referenced in SuiteSignOn setup information, either in the Integration Variables field, or on the User Identification subtab.

    Warning:

    Integrations may require access to some data in your NetSuite account. Make sure you review the data requirements and understand what information is accessed, retrieved, modified, or deleted by the third-party system. NetSuite has no control, responsibility, or liability regarding any third-party applications, even if NetSuite offers resale and integration options for customers' convenience. You use and integrate with third-party applications at your sole risk.

  3. You may need to populate values for custom fields used for user identification, through manual entry, mass update, CSV import, or another import process. Follow the bundle documentation instructions for this task.

  4. If any portlet connection points are included, you must:

    • add one or more custom portlets that display the specified scripts to your dashboard and publish it to other users,

      or:

    • provide instructions to users for adding custom portlets to their own dashboards.

    See Adding Custom Portlets for SuiteSignOn.

  5. If you do not want a subtab connection point to be available to all users with access to the specified record type, you can create a custom form that hides the subtab, define this custom form as preferred for some users, and restrict their access to other forms for that record type. See Creating Custom Entry and Transaction Forms and Defining Preferred Entry and Transaction Forms for Roles.

Related Topics

Outbound Single Sign-on (SuiteSignOn)
Making SuiteSignOn Integrations Available to Users
Mass Changes or Updates
Importing CSV Files with the Import Assistant
Working with Saved CSV Imports
Additional Import and Export Options
Installing a SuiteSignOn Bundle
Troubleshooting SuiteSignOn (Outbound SSO)

General Notices