10.07.2015 Views

SuiteTalk (Web Services) Platform Guide - NetSuite

SuiteTalk (Web Services) Platform Guide - NetSuite

SuiteTalk (Web Services) Platform Guide - NetSuite

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Chapter 4Roles and Permissions in <strong>Web</strong><strong>Services</strong><strong>NetSuite</strong> provides many standard roles with predefined permissions. A role is a set ofpermissions that allows customers, vendors, partners and employees access to specific aspectsof your data. Each role grants access at a certain level for each permission.When logging in using <strong>Web</strong> services you may provide a role id along with your credentials.The role id that you provide must have <strong>Web</strong> services permissions, otherwise anINSUFFICIENT_PERMISSION error is returned. If no role id is provided, then the user’sdefault role is used. If the default role does NOT have <strong>Web</strong> services permissions, then aROLE_REQUIRED fault is returned.The following topics are provided in this section. They do not need to be read in order.However if you are new to <strong>NetSuite</strong> <strong>Web</strong> services, it is recommended that you read each topicto understand how <strong>NetSuite</strong> roles and permissions apply in a <strong>Web</strong> services context.• Role and Permission Considerations When Developing in <strong>SuiteTalk</strong>• Assigning the <strong>Web</strong> <strong>Services</strong> Permission to a Role• Setting a Default Role for a <strong>Web</strong> <strong>Services</strong> User• Setting a <strong>Web</strong> <strong>Services</strong> Only Role for a User• Customer Center, Vendor Center, and Partner Center Roles• Internal IDs Associated with RolesRole and Permission Considerations When Developingin <strong>SuiteTalk</strong>Due to <strong>SuiteTalk</strong>’s reliance on <strong>NetSuite</strong>’s role-based permissions, it is important for <strong>SuiteTalk</strong>developers to put that into considerations during the design phase to ensure smoothdeployments.It is common for developers to use the administrator role during development time because itgives them full permissions and access to all the records and operations. However, the targetend users are likely to have less powerful roles, which may not have access to the data the<strong>SuiteTalk</strong> application requires.Another role-related consideration is the preferred custom forms of some roles may not haveaccess to certain fields or sublists that a <strong>SuiteTalk</strong> application requires. Hence the application’sattempts to set those fields will result in permission errors.<strong>SuiteTalk</strong> <strong>Platform</strong> <strong>Guide</strong>

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!