What's Kelly's recommendations for orgs that can't afford a separate license for each of their integrations? What if they have to dedicate one license to all of their integrations?
Great question! For me, security always comes first. You need to know what is touching your data, when it's making updates and also have the ability to disable access if something goes wrong (API Limits are hit, Integration credentials are compromised and you didn't have enable API Only checked - what would you do in that case?)
If I absolutely had to make a decision under a budget constraint, I would actually say to remove users that are not active in the Org from a pure license count and have each integration on their own license. If the Org is really lean and everyone needs to have their license (and adding isn't an option) then I would pursue getting creative with your options. Review the functionality your users have and determine if you can purchase a different license type that may give them what they need but not have all the bells and whistles of a full license. Can you discuss contract terms and bulk buys with your AE? Analyze the tools that are running in the business and look for overlap, see if you can free up available dollars for those licenses in other areas. It's a really tough challenge, but it's even worse if something goes wrong with your integrations, you can't tell where the issue is coming from and you can't turn it off because everything is hinging on that one license. #CutTheClutter
