We know about the Salesforce release schedule... updates come out three times each year and are automatically applied to their multi-tenant environment. And for those of us trying to keep up, each release comes with literally hundreds of pages of release notes and, hopefully, at least a couple of features that we're genuinely excited to share with our users. The Spring '19 release includes a change that *could* lower the total cost of your subscription! Storage in Salesforce comes in two flavors, data storage and file storage. I'm focused here on data storage, because  that's where I've seen orgs push (or exceed) the standard limits the standard data storage limits are changing  additional  data storage on the platform is EXPENSIVE!  One additional GB of data storage can run $3,000 per year ! I worked with one small org whose incremental storage charges were a pretty hefty percent of their base license costs! (Archived Tasks were the culprit, but that's

As GDPR came into view, I took a closer look at the security settings in our Salesforce org. Probably nothing novel about that statement, but I'll share a few of the changes that resulted. First, I ran the Health Check. It's under Setup | Security. It provides an immediate view of some big-picture security issues. I'll confess that I knowingly have not taken all the recommended actions. In some cases, that's for my own convenience (I do want to be able to log in as any of my users, and I don't want to log in under my own credentials after I log out under a user's id). But some of the isues identified are no-brainers and do leave you in a better security posture. But that's primarily about ensuring that the a user should indeed be logged in to your org. What about the permissions that those legit users have? I've taken a number of steps to further limit access to company data. First, I inherited an org with roughly a hundred users and nearly a d