{"id":1715,"date":"2023-03-29T14:21:12","date_gmt":"2023-03-29T01:21:12","guid":{"rendered":"https:\/\/gravitylab.nz\/?p=1715"},"modified":"2023-03-29T14:26:24","modified_gmt":"2023-03-29T01:26:24","slug":"salesforce-integration-licenses-how-to-implement","status":"publish","type":"post","link":"https:\/\/gravitylab.nz\/salesforce-integration-licenses-how-to-implement\/","title":{"rendered":"Salesforce integration licenses – how to implement"},"content":{"rendered":"\n
Written by our lead architect David Smith<\/p>\n\n\n\n
Salesforce has recently release their new Integration licenses, which allows you to connect to external sites without taking up a standard (expensive) license. All accounts on enterprise and up will get 5 licenses, and it sounds like getting extra licenses is an inexpensive process (to confirm, but it sounds like $10 per license per month).<\/p>\n\n\n\n
Why is this an important offering?<\/h3>\n\n\n\n
\n
Increased security – instead of attaching external systems to a real user, you’re able to set up a specific account that only connects to Salesforce via API.<\/li>\n\n\n\n
Decreased cost – previously, following best practice meant that you lost a license, which was a large price to pay for doing things the right way. Now there’s minimal to no cost in doing so.<\/li>\n<\/ul>\n\n\n\n
How do you implement these licenses?<\/h3>\n\n\n\n\n
Create a new user.<\/li>\n<\/ol>\n\n\n\n
Create a new user, using the Salesforce Integration license type, and the Salesforce API Only System Integration profile. If you need to adjust anything about the profile, you can clone it, but we’re going to be opening up access to objects via permission sets, so it’s not a major issue.<\/p>\n\n\n\n