Ask a questionAsk a question
 

AnswerDisable Connect to Outlook

  • Thursday, March 19, 2009 6:26 PMKumara guru Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    How do we disable "Connect to Oulook" option on the menu items available on a list. It is extremely imperative that we have it disabled for our security to work. Please help.

    We have setup views on sharepoint libraries and tasks lists that allows users to see only items they create or items they can edit. But when the user connects to outlook and imports the list into outlook it opens up the entire library or the task list to the user.

Answers

  • Tuesday, March 24, 2009 1:40 PMDavid Gorbet [MSFT]ModeratorUsers MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     Answer
    You should be able to achieve the result you're looking for using item-level permissions. Under List Settings, choose Advanced Settings, and then pick your policy under Item-level Permissions.

    For document libraries, you should be able to achieve similar results using "Draft Item Security" or by creating folders and applying item-level permissions to the folders. Draft Item Security is in Versioning Settings, and folder-level permissions are created by dropping down the context menu on the folder itself.

    These methods have the benefit that items that users should not be able to see will not show up in search results as well (using just views does not guarantee this).

    Let me know how that works for you.

    -- David
    David Gorbet, Principal Program Manager, SharePoint Online

All Replies

  • Monday, March 23, 2009 2:36 PMDavid Gorbet [MSFT]ModeratorUsers MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     Proposed Answer
    Hi Kumara. I confirmed with the Windows SharePoint Services team that if you use item-level security on a list or document library, or if you use the built-in security trimming in document libraries where folks can only see their own items, then this should be reflected in Outlook.

    Is it possible that you're building these fiews via view filters intead of using security trimming? If so, then this would not be secure in the browser or in Outlook.
    David Gorbet, Principal Program Manager, SharePoint Online
  • Monday, March 23, 2009 7:58 PMKumara guru Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Thanks David. This was helpful information. I'm afraid in our case we use views to restrict users from seeing only those items they are allowed to review, approve and also those that they create. In the library you can setup security at each item level as well but when users create items they do not have authority to assign permissions for them. So it ends up being viewable by pretty much everyone.

    (We have a CER application where users can come in and create CER's in the library)

    For now, I have a workaround. I setup the webpart with no toolbars and so the "Connect to outlook" option does not show up (Actually none do). Then I found another way people can bypass the "view" security--- by using "web folders". If a user can take the url to the library and create a webfolder. He can come in through windows explorer and see everything. I'm still thinking of a workaround for this.
  • Tuesday, March 24, 2009 1:40 PMDavid Gorbet [MSFT]ModeratorUsers MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     Answer
    You should be able to achieve the result you're looking for using item-level permissions. Under List Settings, choose Advanced Settings, and then pick your policy under Item-level Permissions.

    For document libraries, you should be able to achieve similar results using "Draft Item Security" or by creating folders and applying item-level permissions to the folders. Draft Item Security is in Versioning Settings, and folder-level permissions are created by dropping down the context menu on the folder itself.

    These methods have the benefit that items that users should not be able to see will not show up in search results as well (using just views does not guarantee this).

    Let me know how that works for you.

    -- David
    David Gorbet, Principal Program Manager, SharePoint Online