How to keep just one (or a few) Accounts Private in Salesforce

Salesforce’s security model is pretty flexible, but it’ll take a little (but not too much) work if you want to set it up so all of your accounts are publicly available except for a few.

First, create a new check box field called ‘Private’.  If an account should be private then we’ll check this button.  You may want to control field level security (FLS) so only admins can read and/or update the field.

Private 1

Next, we’ll set the Organization-Wide Default for Account Security to private.  This is done under Setup | Security Controls | Sharing Settings.

Finally, create an Account Sharing Rule that makes non-private accounts available for Read/Write, then the appropriate access for Contracts & Cases.

Private 2

3 Fields Every Sales Organization Needs

Whether you’re dealing with Leads, Accounts or Opportunities keeping in touch with the folks associated with each is key to a successful sales organization.  Salesforce provides a rather odd field called ‘Last Activity’ for leads, accounts, and opportunities that is the last date an activity was conducted with the entity.

It’s odd because, while it’s available for user in list views and reports it isn’t available to place on the entity’s screen.

Last Activity 1

So this is a great field, but by using it in a formula field to calculate Days Since Last Activity is more useful as it can be used everywhere in Salesforce and lets you easily create reports and views such as Open Opportunities with No Activity in 30 Days.

So, for opportunities, here’s what the formula field for Days Since Last Activity would look like:

Last Activity 2

That formula would be the same for leads and accounts as well, you’d just need to create formula fields for those objects.

You can place it anywhere on the page layout but here you can see it as it would be displayed within the System Information section.

Last Activity 3

For a report, you can set the filter criteria so that you’re seeing all opportunities that have a Days Since Last Activity as greater than 30 or blank so you pick up  both.

Last Activity 4

Why you should never click the ‘Log a Call’ button in Salesforce

This seems counter-intuitive, right? The CRM mantra is, “If it isn’t in Salesforce it didn’t happen.”

Well, you should still log your calls in Salesforce, but instead of using the Log a Call button in the history related list, we should be using the Quick Action in Chatter.

Quick Action
That is accessed from the Chatter Feed, then More and Log A Call.  Easy, enough, but why?  If you use the Log a Call, the activity certainly gets tracked, but unless someone views the record or runs a report they’re probably  not going to know that it happened.  If we use the Chatter Quick Action then it’ll also be in the chatter feed so anyone that follows that record will see it in their chatter feed and part of their daily digest.

The call will show in the chatter feed and in the activity history related list.

Quick Action 2a>