Pretty soon you can use Jigsaw (now Data.com) to keep your Contact data up-to-date, but there is a nice little and commonly overlooked native feature in Salesforce.com to keep the information on your Contacts current – it’s by sending a “Stay-in Touch Request.” First things first, you’ll need to check your settings for the feature under Setup…
How do you know who can see what records if your Organizational Wide Defaults are set to “Private for an Object? If the Object’s OWDs are set to “Private” then records for that object will have a “Sharing” button at the top of the record. If you click on that button you’ll see who can…
Enabling Sales Teams allows the Salespeople to quickly grant access to other who help them sell. In this example we have an Inside Sales Team comprised of a few Users. We don’t want to create a share based on a Role or a Public Group, but rather we’d like the ability for each Salesperson to…
Continuing on setting up security with for our example sales organization, let’s say that you have support staff in the role of Sales Engineer that report directly to the VP, North America Sales. Sales Engineers lend technical assistance on Opportunities, and thus need to see Accounts and Opportunities owned by the salespeople under the VP,…
Being the Record Owner gives you some special privileges, even if your OWDs are set to “Private.” The User that is the Record Owner typically should be able to Edit, View, Delete and Transfer ownership of the record. What might limit the aforementioned is the security for that object based on the Profile assigned to…
Folder security is an exception to your OWDs. Access to folders, whether in Documents, Reports or Dashboards are folder specific, or “explicit” – ignoring the Role Hierarchy. You set access every time you create or edit a folder. Let’s say that you have six folders in the Reports tab to organize all your company’s reports….
Let’s say that the Director, Direct Sales does want to allow her team to have access not only to her records but also access to records owned by the Eastern Sales Team and the Western Sales Team. First you would create a Public Group from Setup >Administration Setup > Manage Users > Public Groups and…
Organization-Wide Defaults, or OWDs, are the baseline security you for your Salesforce instance. Organizational Wide Defaults are used to restrict access. You grant access through other means we will talk about later (sharing rules, Role Hierarchy, Sales Teams and Account teams, manual sharing, etc). There are four levels of access that can be set: Public…
Salesforce.com security seems to be a topic that trips up a lot of administrators. There are a lot of ways to restrict and grant access in Salesforce: Organizational Wide Defaults (OWDs), Role Hierarchy, Sharing Rules, sharing records using Groups, Sales Teams and Account Teams, and of course those special privileges you have as a Record…
Chatter is finally here – general release came on June 22, 2010 for the majority of Salesforce.com Users not participating in a beta program. Did Benioff’s “Facebook for the Enterprise” meet the hype? That hype has been building for an eternity in Salesforce.com time – it was first announced way back in November 2009 and…