In order to sync data between two systems, a user login is required for both of your connecting applications. Our recommendation is that you have dedicated licenses on both systems, as opposed to sharing a license with another user. (Please note, another option to connect with NetSuite will be to use Token Based Authentication. See here.) However, it is not necessary to have a dedicated license.
During implementation, a dedicated license is preferred. If the license you are utilizing is shared with another user, they may conflict. For example, in NetSuite, user licenses are set up to only allow one login at a time. So, if a second person logs in is using the same user ID, it will log out the person who is already logged in. For example, this could happen if you’re using your NetSuite user login for testing, and the Celigo Technical Implementation Consultant (TIC) is using the NetSuite login used by the Connector to follow up on a question you’ve asked regarding a testing result.
After go-live, the Connector will continue to need a user login in both systems. Please note that the user id on both systems is required not only for the person who is testing the Connector; but also for the Connector API itself. Although many systems may kick out the first user when two users share a login, when sharing the NetSuite user with the Connector itself, there is no risk of a forced log out because the NetSuite user interface (UI) and application programming interface (API) do not log each other out.
A dedicated license also provides better visibility. Most reports and monitoring tools won’t be able to differentiate between data that the connector created and data that the person who shares that license created.
Ultimately, it is your choice whether you want the Celigo connector to share a user login or have its own user login. Please be advised that each user login requires a separate license.