Follow Us:
In addition to email, another oft-used feature of Outlook is storing contacts. You can access them from your mobile device, the web, etc. But what if you wanted to make those contacts available to be viewed by other coworkers? For example, you’re a member of a sales team, and you need the ability for your sales peers and managers on your team to be able to see your contacts (and you see their contacts as well). Let’s also assume that you’re not using a xRM system to track these contacts like Microsoft Dynamics CRM or Salesforce.com, but instead you want to use SharePoint. How can we use SharePoint to store and share our contacts? Easy!
This simple endeavor does not require any add-ons or custom functionality or code. SharePoint can provide this functionality in 2 main parts:
The great news is that you don't have to open the SharePoint interface just to add or update a contact. To complete this procedure, the first part requires a power user / site owner or some user with at least design privilege (preferably full control to set permissions as needed).
This will be done in 3 steps:
Since SharePoint is the repository we want to use to primarily store our contacts, we need to create a list or lists to store them. First thing we need to do is determine how many lists we will need, and that will depend on our requirement. Hopefully before you configure anything in SharePoint, you have a need or requirement. In this case, the business came to you and said “we need to store out contact lists from our sales team in SharePoint”. Ok no problem. The main driver here is who can see the contact records.
Let’s say that the business tells you that in SharePoint, the contact lists need to be restricted. Each user can only see their own contacts, but there will be a group of other managers who can see everyone’s contacts. If that is the case, you will need a contact list in SharePoint PER sales person. That is because if this was one list with contacts from all sales members, when sync’d down to Outlook you can’t control with permissions and all items would be populated even though we can in the SharePoint UI. That may be fine, and in that case you can create one list, and create a column for “salesperson” as a person/group column, and go to town. In our case, we needed the former with permission restrictions.
Done! At this point, set permissions as needed per your requirements. For our quick little demo we’ll everything as default. Now let’s sync the list to Outlook.
This is identical between SharePoint 2010 and 2013. Steps 2-3 might vary slightly depending on your version of Office.
The sync’d list(s) will show in Outlook like this, in Other Contacts. The name will show the name of the subsite – the name of the contacts list. Repeat this for as many contact lists as you have.
Now that we have everything wired, all we have to do is move the contacts from local Outlook to the new and shiny SharePoint contacts list. Luckily the users should be able to do this for themselves. All is needed is to drag and drop the contacts from one list to the other from within Outlook.
Once that is done, we click on the SharePoint contacts list and we see our contacts:
And they show up in the browser after a refresh as well:
Now the users can delete their contacts listed in Outlook, and they only exist in SharePoint, but still can be managed by Outlook. Remember this is a 2-way sync, meaning that any changes in SharePoint will show in Outlook, and any changes made in Outlook will show in the SharePoint interface.
For more information about C5 Insight or this blog entry, please Contact Us.
The complementary paper includes over 12 years of research, recent survey results, and CRM turnaround success stories.
Request Download
This 60-second assessment is designed to evaluate your organization's collaboration readiness.
Learn how you rank compared to organizations typically in years 1 to 5 of implementation - and which areas to focus on to improve.
This is a sandbox solution which can be activated per site collection to allow you to easily collect feedback from users into a custom Feedback list.
Whether you are upgrading to SharePoint Online, 2010, 2013 or the latest 2016, this checklist contains everything you need to know for a successful transition.