The Digital Commerce package comes with basic permission set for providing the necessary access to users. The permission set is named 'Apttus Ecommerce' and should be assigned to users to access the digital commerce storefront. If you would like to make any changes to the permissions, you may clone the permission set and make any changes necessary.
Using the managed permission set may prevent a portal user from logging in to Digital Commerce. This occurs because the managed permission set does not have API Enabled Permission by default. You must create an unmanaged permission set and enable API permission.
To enable API permission
- Clone Apttus Ecommerce permission set and name it Apttus Ecommerce Custom.
- Go to Setup > Administration Setup > Manage Users > Permission Sets and select the permission set. In this case, Apttus Ecommerce and Apttus Ecommerce Custom.
- Go to System Permissions and select to check API Enabled.
- Click Save.
Every time you assign Apttus Ecommerce permission set to a user, you MUST assign Apttus Ecommerce Custom permission set as well.
You must provide CRUD permission to the API Cache object.
For Proposal and Checkout APIs to work seamlessly, you must assign appropriate user permissions to custom fields that you may have added to an object.
Guest User Access
In newly spun orgs, due to Salesforce upgrade, site guest users do not have access to some user fields like Alias. This is fixed by using userType on a user record to generate a token. For new orgs, you must add the following permissions on the storefront object to site guest user at profile level (E-Commerce Profile).
Object level access : Read
Read access on the following fields:
- Cache Size
- Enable API Filters
- Guest Username
- Guest Password2