Last Minute Simple Dreamforce Tips

So you’ve landed in San Francisco and you are extremely excited about Dreamforce.  Hopefully you’ve followed some good advice up to this point:

I won’t rehash all of the basics here, but hopefully you’ve at least come in with a plan, and have somewhat of an agenda for yourself.  Whether you have over prepared or underprepared, here are a few simple last minute tips that don’t require a lot of effort, but can really make the Dreamforce experience a little bit better for you:

  1. Know that Marc’s Keynote Session Always Goes Long:  because it is is packed with such good information about the future of the platform (…errm Lightning!),  as well as success stories for different clouds, annnnd Marc’s penchant for scintillating conversation –  this session always goes long.  You will see a sea of people leaving early, scrambling to get to their next session.  So either don’t plan anything for directly after the keynote, or plan to leave a bit early.  But do not plan to miss it, because it is one of the more important sessions at Dreamforce.  Which leads me to the second tip…
  2. Bring Something to Munch on and Drink at Keynotes: when you are sitting there with extreme dry mouth and about to pass out, you will thank me.  I always carry around a Kind bar just incase.  To a larger conversation point – don’t forget to eat.  Take care of yourself.  Which leads me to the third tip…
  3. Don’t Go Too Hard The First Night: Dreamforce is a marathon, not a sprint.  Although there will be temptation at every turn, do yourself a favor and get some sleep early on.  Have a drink limit.  Eat properly.  It will drastically increase your chances of not getting sick at the end of the week.  When they aren’t looking, swap the shot of tequila your co-workers are shoving in your face with a shot of water – people will be amazed as your resiliency to hangovers, and you will be hydrating at the same time!
  4. If You Forgot To Bring Comfy Shoes: or you think you look too darn good in your somewhat uncomfortable shoes and didn’t bring your comfy ones…you’ve made a grave mistake.  But that is okay, there is still time for you.  Hop over to the Target on Mission St and buy some Dr. Scholl’s.  You’l’ be gellin like a felon…and your feet will thank you.
  5. If You are Second Guessing Whether to Bring Something With You: don’t bring it.  It will only weigh you down, you need to be light as a feather.

The rest is up to you.  If you forgot to bring an extra battery charger for your device, go down to the expo…there will be a Partner giving them away.  If you forgot to not carry your laptop, it is okay, there is a coat/bag check where you can stow it.  If you forgot to bring your inquisitive mind, then wake up you are at Dreamforce!! Have fun!

 

    Case, a Simple Object, is Not.

    In the previous post, “What the Hell is the Service Cloud Anyway?” we talked about what the Service Cloud actually is, as it relates to the Sales Cloud and specific Salesforce functionality.  That post was really to frame the rest of the series; dissecting the award winning Service Cloud into its core components.  And at the nougaty core of the Service Cloud is the simple case object.

    What Makes the Case Object so Special?

    If I were able to teach a course in Salesforce, it would be Existential Salesforce Philosophy or maybe Salesforce Buddhism.  We would study Salesforce koans, like “what is the meaning of a queue with only one person in it?”  Or maybe, “in a flat organization, what does an escalation rule really mean?”  My guest speaker would be Salesforce Yoda and the focus area of the class would be – what makes a Standard Object so different from a Custom Object?  YodaThey both contain the same basic properties:  security controls, fields, validation rules, record types etc.  The list goes on and on.  A young grasshopper may think to themselves, “Why couldn’t I just re-create the Standard Objects using Custom Objects?”  However, the more one uses Salesforce, the more they see that Standard Objects have useful innate features which make them unlike any basic Custom Object.  They also have a spider web effect; their functionality is generally pervasive throughout the platform – so much so that if you were to try to create the objects on your own, you’d keep finding little Easter eggs that make your once clever idea seem like a terrible nightmare.  So what makes the Case object special?

    1. Assignment Rules – Assignment rules allow you to automatically assign cases to users or queues based on criteria you define. The special thing about assignment rules (also seen with leads) is that you can order the rules in the sequence you would like them to run.  This is important because it means not all assignment rule entries are created equal.  Generally, with Salesforce, it is very hard to order the sequence of rules processing without using Apex (although the Process Builder is a huge leap forward in this arena.)  Workflow rules, a separate category of automated business logic within Salesforce, do not allow you to determine which workflow rule should fire first, or second.  They just fire.  And you just pray.  Case Assignment Rules also allow for an email template to be chosen per rule entry, as well as predefined case teams that can be assigned to the case upon assignment.  Do you want to create an admin friendly, easily customizable weighted rules engine?  I don’t.

     

    1. Escalation Rules – automatically determine when cases should escalate and what actions to take. Hmm, why couldn’t I just use workflow rule to change a field on the case to “Escalated” for a similar effect? Are you allowed to put your workflows in a weighted sort order?  Does your workflow rule allow you to incorporate the business hours specified on the case?  Meaning, fire 3 hours after the last modification time of the case, but only if those 3 hours fall into the case’s specified business hours.  Workflow rules don’t care about business hours.  In fact, escalation rules are one of the few areas within Salesforce where business hours are natively built into the functionality.  While it should be more pervasive, any time you can use out of the box functionality in conjunction with business hours you should jump on the opportunity.  Second, escalation rules actually allow an administrator to set business hours on a case.  In fact, (and please correct me if I am wrong here) but to the best of my knowledge escalation rules are the only way to declaratively update business hours on a case based on certain criteria without using code.  It cannot be done with workflow.  It may be able to be done with Flow or Process Builder.  But if you aren’t using escalation rules for escalation purposes, you can always use them as a sneaky way to set business hours (even though it feels kind of hacky.)

     

    1. Support Processes – much like the Opportunity Sales Processes, Support Processes allow you to “use the status field to identify a case within the support lifecycle.” Why it is nice – you can have multiple case types, and multiple statuses, and still use only one field for all of your reporting.  Second, if you spin your own custom field, you will missing out on some native Case Lifecycle reporting, as well as features that allow you to limit case close statuses, or basically any integration/feature that depends on case status.  Basically don’t do it.

     

    1. Auto-response Rules – Auto response rules allow you to fire an e-mail when a case is created. What makes these different from workflow is again, the ability to have a weighted sort order for rule execution.  Now in theory you can create a bunch of workflow rules to mimic this functionality, but if a case matches two workflow rules, you won’t be sure which one will fire.  Here you do.  The one with the higher sort order.   Second, auto response rules allow you to easily specify the name and email address of the sending email, as well as a reply-to address.  You can select a template for your email, as well as decide whether or not all recipients on the original email should get a response, or just the initial sender.

     

     

    1. Email-to-Case (E2C) – This feature is so powerful it might require its own post. In fact, it does – so more on this soon.  But the long story short, emails can turn into cases very easily.  Not only that, you can set up filter criteria on the EmailMessage object to automatically route incoming case e-mails.  Very powerful stuff.

     

    1. Web-to-Case (W2C) – Just what it sounds like. Salesforce will let you pick your desired case fields, and it will generate some basic HTML so that you can put a form on your website, that when clicked, will create a case in Salesforce.  This is very much starter code – you will want to sexy up the form to fit your branding guidelines.  Also, standard W2C does not allow file attachments.  You can vote for that idea here.  Other use cases where W2C might need to be enhanced are for multi-page forms, forms that interact with Salesforce before committing data, and forms that write to multiple objects.  You can spin your own Force.com Site to do a lot of these things, but there are a couple of nice AppExchange applications like ClickTools and FormAssembly which have similar functionality.

     

    1. Case Teams – allow for multiple users to be involved on case at the same time. This can be for purely informational reasons, but it can also be used to grant security access to the case.  This is another area where if you create your own custom object to mimic case teams, you will have to do a lot more than you thought if you want to have the built in security sharing functionality that case teams provides.  We’ve already seen that case teams can be assigned during the assignment rule process, which is yet another link between native features of the Service Cloud.

     

     

    1. Case Feed – this is one of those game changers that Salesforce created a few years back. The sad part is that there are a ton of companies out there that use the Service Cloud, that haven’t yet introduced the Case Feed.  The Case Feed is a newish way to see all of the information of a case in a Chatter-like feed.  It brings more relevant information to the agent more quickly, and it allows for an easier comprehension of the story and timeline of a case.  If you venture away from the case object, you lose the ability to use the case feed, which doubles down on native SFDC features like Chatter, Actions, and Quick Text.  I have previously written a blog post on the Case Feed called Case Feed Me, I’m Hungry!

     

    1. Quick Text & Macros – Quick text works in conjunction with the Case Feed (as well as Live Agent) and allows a user to quickly recall a snippet of text to send to a customer. This is helpful for agent speed and efficiency, as well as consistency in messaging.   Macros allow for the repetition of common tasks (send an email; update a status in a single click.)  It is a new feature, but don’t sleep on it as it can easily drive efficiency in your customer support organization.  Both of these features only work with the native case object.

     

    1. Case Comments – Case comments allow your reps to create a public or private comment on a case. Case comments integrate with communities, making it wise to stick with this feature if you use a community, or intend to in the future.  Just a note, case comments have a 4k character limit, but you can vote to increase that limit here.

     

    There you have it.  I’m sure you are a bit exhausted from reading this post, but remember, this is just core case functionality.  The next few posts will dive ever deeper on Email-to-Case, Knowledge, Live Agent, CTI, the Service Cloud Console, and Entitlements/Service Contracts/Assets.  We will also touch on Business Hours and Case Time Logging, as well as Communities.   So as Salesforce Yoda might say; “Case, a simple object, is not.”

     

     

      What the Hell is the Service Cloud Anyway?

      When describing the benefits of Salesforce to customers and prospects, I’ve realized that sometimes branding can get in the way of insight.  Salesforce has one of the top marketing departments in the entire world.  From Salesforce.com to the Force.com platform to Salesforce1, they have done a wonderful job segmenting the different Salesforce features and functionality into bite sized pieces.  service_cloud_logo_285SMALLThat being said, sometimes the language can be a bit confusing to someone who is not already familiar with the Salesforce ecosystem.  Over a recent discussion with a prospect, I realized I had to go back to basics to portray what the “Service Cloud” actually is.  The next couple of blog posts will detail that discussion, to deliver what Salesforce means by the “Service Cloud,” and describe the features that has led Gartner to recognize Salesforce as the leader in the Customer Engagement Center Magic Quadrant, Forester to recognize Salesforce as the top platform for CRM Customer Service, and me to recognize the Salesforce and the Service Cloud as freaking awesome.

      Back In the Day

      Before Salesforce had separated its offering into different clouds (Marketing Cloud, Sales Cloud, Service Cloud) there was just Salesforce.  And core Salesforce (or out-of-the-box Salesforce, or vanilla Salesforce) at its crux has a few Standard Objects – objects that currently span across all three clouds.  Core Salesforce includes Accounts, Contacts, Leads, Opportunities and Cases amongst other standard features.  When talking about collaboration between departments, it makes sense that a Marketing Department might be interested in existing Opportunities or open Cases associated to the people they are marketing to.  Sales should also be interested in the customer support cases that their prospects and customers have submitted.  Customer Care should not only be able to answer questions and help customers with issues, but they should also be able to pass off hot leads to Marketing or Sales.  This was the vision of Salesforce, and still is; yet the ecosystem has become so robust that over time, the different functionality has warranted different licensing structures.  That being said, whether purchasing Sales Cloud or Service Cloud, the core functionality listed above is included with both.  Can you create Cases with a Sales Cloud license?  Yes.  Can you create an Opportunity with a Service Cloud license?  Of course.

      So what’s the Difference?

      When talking about full Salesforce User Licenses, the Service Cloud has a few features that do not exist in the Sales Cloud:

      • Service Cloud Console
      • Entitlements
      • Service Contracts
      • Live Agent (requires additional feature license)

      As far as I can tell, that is about it.  But let’s not get hung up on licensing; rather, let’s explore the rich features and functionality of Salesforce as it relates to customer support.  The next series of blog posts will detail all the features of the Service Cloud (whether part of the Sales or Service Cloud licensing) that make Salesforce the industry leader when it comes to Customer Service technology.  The above called out features will also be explained.

      We are in the age of the Mobile and Social revolutions, where customers hold the power and expect companies to be able to provide support anywhere, anytime.   ForbesAre your customers able to connect with you when and how they want to?  Do your agents have the right tools to respond quickly?  Do your managers have access to the right data to make decisions?  Let’s explore the Service Cloud and see why Salesforce has been awarded Forbes most innovative company for four years running.

       

       

        The Future of Salesforce is Not What You Think

        I’m going to make a bold prediction. I mean, it better be bold with a blog title like that. The future of Salesforce is not Business to Business (B:B) or even Business to Consumer (B:C). It is consumer to themselves (C:ME).

        We’ve seen a proliferation of connected devices with the Internet of Things (IoT) phenomenon, where our devices are now tapped into the connectivity of the internet. BenioffMr. Marc Benioff, the CEO of Salesforce, is quick to point out that our toothbrushes can now talk to our dentists to make sure we are not slacking on our brushing. We’ve also seen the likes of Fitbit and Jawbone keep track of our steps and even our sleep patterns. We can now control the temperature and lights in our houses from afar.

        However, what this phenomenon has shown is that information relevant to ME is lacking a home. Information is in disparate places connected to disparate systems. I’ve seen this story line before; every day in my job consulting with some of the world’s top companies, there is a desire to bring information from different back office systems to one single place. CRM and Salesforce specifically has led the charge in connecting these different areas of information with their API first philosophy. This is good for companies. Customer service agents are now empowered with a plethora of information to make the next best action for their customers, providing a more effortless experience. Sales people, with the help of predictive insights across data sets can focus on providing tailored solutions for their customers.

        Yet the individual has no similar consolidation.

        Enter the concept of the personal CRM. Individuals need a single place to track their lives; a place where information from many different data sources can be captured and consolidated.  We need a home base to keep track of information relevant to ourselves. In addition, there is also a need to track information against our network of friends and contacts. Facebook is excellent for keeping in touch, yet it lacks the ability to capture notes and activities against a friend’s record. Different tools available to consumers like the Jawbones and Fitbits of the world are great, but they are creating information silos. As a result, insights about the individual are buried within disparate data sets.

        Enter Salesforce. Salesforce, with its flexible platform, is prime to serve as the database of the individual for the C:ME revolution.  The C:ME revolution pivots around mobility, with on the fly access to these personal databases.  Salesforce is especially optimal because of the advent of Salesforce1, Salesforce’s mobile offering.  All that is left is for Salesforce to offer the ME version.  A price point like Spotify’s at $9.99/month seems fair for consumers to access their own personal databases.

        Over the next couple of blog posts, I will be introducing the C:ME concept by building a “PersonalForce” demo which will allow us as individuals, using Salesforce as a platform, to capture information about ourselves and our connections. Via the use of Salesforce’s existing data model, with a couple of additional custom objects, we will have the ability to capture information, provide reminders, and start to provide insight into the personal.

        Here is a skeleton for 1.0 functionality of PersonalForce:

        Gifts:
        – What gives did I give to my contacts? What gifts did they give me?
        – What was the date and the occasion?

        Bills
        – Company, Date, Amount

        Food
        – Meals, when, what

        Feelings
        – Sentiments

        Car
        – Last oil change, inspection, tire rotation etc.

        Medical
        – Appointments
        – Personal health notes, medications etc

        Tax Write offs
        -Gift type, counts

        Warranty Expirations

        Soon we will be able to add information on the fly, run reports and see personal life dashboards.  We as humans have a desire to track information about ourselves, and to date, there just flat out is no good, flexible place to do it.  The above is just a preliminary list to get the brain juices flowing. I’d love to hear some feedback as to what else would make sense to be tracked.

        Our lives are fragmented. Our data sources are even more fragmented. PersonalForce is the 1.0 for bringing it all together. Personal databases are the future, and Salesforce.com is the platform of the future for the individual in the C:ME revolution.

          Second Annual Salesforce MVP Summit!

          I’m currently heading to New York from San Francisco heading SE at 31,005 feet in the air, traveling 588 MPH with a 51MPH tailwind.  I’ve traveled 2,420 miles with 232 remaining, and I know my exact longitude and latitude.  I’m connected to the internet and checking the car traffic on the ground that is being consistently reported real time via Waze users to Google’s traffic service.  I know exactly what time I will get home so that I can pre-order some delivery food after a long flight.  Needless to say, we are in a connected world; we are connected customers, connected employees and we are interacting with connected devices.  No one knows this better than Salesforce, and no one is more engaged with the Salesforce community than their MVPs.  Salesforce’s second annual MVP Summit just wrapped up, and all I can say is: WOW!  Literally, that is all I can say; part of the MVP program is that each MVP gets access to road-map features and product management in return for their sworn silence in public arenas. (We each sign an NDA.) At the summit however, we collaborate with product management to provide valuable feedback which hopefully impacts the direction of the product with the voice of the customer.

          The MVP program is a valuable part of the Salesforce ecosystem.  MVPs are the creme of the crop in terms of community involvement.  We engage in different channels, we mentor potential MVP candidates, and we grow the MVP program.  We give back to the Salesforce world – whether it be via a user group, a podcast, through the Answers Boards, Stack Exchange, Twitter one one of any number of various channels.  We answer people’s questions.  We push the limits of the platform.  We share what we learn, and we have fun doing it.  We write books, we write blogs, and we are passionate.  We come from all over the world.  We collaborate and we all push each other to become better at what we do.


          What I can say about the summit is that there was representation from all areas of Salesforce – from Sales Cloud to Service Cloud and a bit of Pardot, from product management all the way up to a live session with Parker Harris.
          Parker Harris at the MVP Summit
          We started with a little giving back to the community, by creating blankets and stuffing gifts for Project Night Night, a program which “donates over 25,000 Night Night Packages each year, free of charge, to homeless children who need our childhood essentials to feel secure, cozy, ready to learn, and significant.”
          MVPs at with Project Night Night
          Many of the MVP group comes from the Non-profit world, and we all appreciate giving back and spreading the message of community.
          Next we learned a bit about the other MVPs as the program has grown to over 100 people from around the world.  We broke into different groups and learned about things we share in common, then reported back to the larger group.  Then the SFDC blitz began.  Without getting too specific, there is a large focus on Mobile and User Interface, Integration, Business process automation, Compliance monitoring and more.  We heard from the ISV group and about Salesforce1.  We then broke into smaller round tables where we had “speed dating” rounds with different Project Managers – and I can honestly say that the conversations were two sided and that we all learned from  each other.  We learned about the future of Service Cloud, of Chatter, of “Trust”, analytics, files, the Microsoft partnership and more.  It was an overwhelming amount of information, and everyone agreed that great things are in store for Salesforce customers and the community alike.  By the end of the two days, my brain felt like an over-saturated sponge of Salesforce awesomeness.


          Now it is time to reflect on the last two days an the amazing place Salesforce has had in my life.  I work for an amazing company with these guys
          Bluewolf MVPs
          (also fellow MVPs) at Bluewolf where I get to consult with different companies around the world on Salesforce best practices.  I get to work in a community with these people,mvp group at summit
          who are the most vibrant, intelligent, and caring people out there, lead by our fearless leaders Matt Brown, Erika Kuhl and April Nassi.  Sometimes it feels like work, but most of the time it feels like family.  Thanks Salesforce!!


          Last photo credit of the ever present CTO of Customer Connection Charlie Isaacs @charlieisaacs.


            Salesforce + Excel = <3

            Back in good old 2012, the year of Gangnam Style, when a guy jumped from space 127,000 feet back down to Earth, and the announcement of a new particle by CERN – we at ForceCollective were writing about how to update data in Salesforce en masse.

            Since that time, a few new tools have come to light which are worth mentioning.  People seem to have an affinity for dataloader.io which is a web-based toos that people like because of its simplicity.  There is a new game in town, however, that would make good old Ron Hess (the creator of the original Excel Connector) proud.  This tool is called “Enabler for Excel” which takes the Excel Connector to the next level:

            Save queries? Check

            Pull in report data? Check

            Convert 15 to 18 digit Ids? Check

            enabler

            But wait, there is more?  Sure why not.  Let’s add in Field Trip like functionality to see the % usage of different fields.  Let’s add in a tool which shows which fields are on different page layouts for an object.  Why not add in a feature which will convert a standard page layout into a Visualforce page as a starting point.

            If you are an Excel fanatic, then downloading data straight into Excel rather than uploading and downloading CSVs is a present from above.  I used the Excel Connector extensively, but then had some issues with it as I upgraded my machine.  This newer plug-in seems to have a lot of fanfare about it, and for just cause.

            Link: Enabler for Excel

             

             

              Admin Quick Win: Field Level Security by Object

              Sometimes Salesforce is downright sexy.  More and more, the things that can be done with the platform are only limited by what can be imagined.  However, even in a world of flexible platforms and limitless potential, there are still a few admin-centric activities that are a bore.

              Field Level Security

              You might find yourself in a scenario where you have to update field level security for different fields on an object.  If approaching this from a field perspective, you are in luck because there is the option to select all boxes in a column natively.  However, if you are looking at updating an entire object’s fields for a specific profile, you might run into a problem.  There is no native way to select all of the checkboxes at once, which can mean a lot of clicking. Here is a quick admin tip to update field level security en masse for a profile:

              1. Download CheckFox (For Firefox).  If using Chrome, it appears as though there are similar extensions.

              2.  Visit your target profile.  Go to the field level security section, and select your desired object.

              3.  Highlight the column of checkboxes you are interested in.  To do this, you can simply press the control key, and drag with your mouse:

              AccountFLS1

              4.  Right click, and select the “check” button.

              AccountFLS2

              5.  Rejoice as all fields are now checked.

              AccountFLS3

              This is one of those quick wins where it won’t be a game changer for your company, but it might save you a little bit of time, and keep your blood pressure down!

                Salesforce Security: 7 Reminders for the Security Savvy

                My colleague and Solution Architect Jon Tresko recently published an AMAZING four part series called “The Definitive Guide to Salesforce Security.”  If you were interested in really getting a good grasp of Salesforce Security from all of its dimensions without reading through the entire Salesforce user guide, it is an excellent resource.  Here are the four installments:

                1. http://www.bluewolf.com/blog/definitive-guide-salesforce-security-101 – data security
                2. http://www.bluewolf.com/blog/definitive-guide-salesforce-security-201 – data security part 2
                3. http://www.bluewolf.com/blog/definitive-guide-salesforce-security-102 – app security
                4. http://www.bluewolf.com/blog/definitive-guide-salesforce-security-202 – app security part 2

                Jon’s blog posts inspired me to write some tricks and tips for those of you who have dealt with the security game before.  Call them reminders if you will; below are those bits of knowledge that are often buried deep within the user guide that it really helps to keep top of mind.

                With no further ado:

                1.  Sharing Rules to X – When writing sharing rules, you can only reference certain entities to share with.  These include the role hierarchy and groups.  Individual users are not an option, but it is possible to create a group with a single member in it.

                2. Criteria Based Sharing Rule Limits – Criteria based sharing rules are an awesome tool to have in an administrators tool belt.  There are some important caveats to know when considering them.

                • Criteria based sharing rules can be created for Accounts, Opportunities, Cases, Contacts, Leads, Campaigns and Custom Objects.   Any standard object you don’t see here (Products, Price Books, Assets etc.) are not candidates for criteria based sharing rules.
                • You can have a maximum of 50 criteria based sharing rules per object.
                • Crtieria based sharing rules on text fields are CaSe SeNsiTiVe.
                • Certain field types cannot be referenced in a criteria based sharing rule, such as formulas and multi-select picklists.  You can potentially get around this with a workflow rule which posts the data to another field like a text field, or in more difficult situations with a trigger posting to a text field.  Here are the field types you CAN use
                  • ◊ Auto Number
                    ◊ Checkbox
                    ◊ Date
                    ◊ Date/Time
                    ◊ Email
                    ◊ Number
                    ◊ Percent
                    ◊ Phone
                    ◊ Picklist
                    ◊ Text
                    ◊ Text Area
                    ◊ URL
                    ◊ Lookup Relationship (to user ID or queue ID)

                3.  Record Types on Profiles Affect Creation – I see this one all the time.  Giving a profile a record type means that users can now create new records with that record type for that object.  It does NOT mean that a user cannot see records of that record type if they do not have that record type assigned to their profile.  This is purely something that affects creation.

                4.  Permission Sets Have Limits – namely they cannot grant access to page layouts, login hours, login ip ranges or desktop client access.  Page layouts make a lot of sense here because page layout assignment is really a matrix of profile, layout and record type.  Adding permissions sets to the mix would make assignment infinitely more complex.

                5.  View All/Modify All Per Object – for you old schoolers out there who always think sharing rules first, this feature at the profile level is another way to grant users access across all records of an object without the use of a sharing rule.  I often think sharing rule first because sharing rules pre-existed this feature, but it can be a nice hidden trick in your bag.

                6. Accounts Behave Differently – Accounts are automatically shared if a user has access to a related Opportunity, Case or Contact.  If you are trying to lock down Account access, but have open Case/Opportunity/Contact access, you will need to start to think about locking those down as well.

                7.  Changing the “Share With” field on Sharing Rules – Once a sharing rule is created, you can modify most things about it, except who it is shared with.  If this needs to change, you need to create a brand new spanking rule, and get rid of the old one.

                I hope this list was helpful.  Again if you are looking for more comprehensive stuff, visit Jon Tresko’s blog posts on security, then come back here for the small reminders that you will probably run into.  And last and definitely not least, the general rule of thumb with security that I like to follow is to create the fewest number of profiles that are the most common denominator of access and rights for the broadest user population reach.  Then you can layer on additional access with permission sets.  Happy securitying!