client, customer or company you support could be held financially responsible if your SharePoint farm is compromised
Sharon Richardson of JoiningDots.net delivered a lively EUSP Live Online session this morning on Managing SharePoint 2007 Site Permissions. If you weren’t able to attend the session, we are making it available for download as a live meeting presentation. Download the package and expand it on your local harddrive for viewing.
Sharon and I have been talking about working together for a while now, so this seemed like a perfect opportunity to get started. EndUserSharePoint.com will sponsor a free, half hour live online talk, as Sharon walks through her slidedeck on SharePoint permissions, taking Q&A in the process.
I could not get the admin to enable Anonymous Read Access, as believed to be the problem with not being able to access authenticated feeds. I discovered a work around, using SharePoint Designer.
As per the requirements listed in the introductory part, we need to create a back-end where we will store the subscribers’ contacts and information. Since everything in SharePoint is stored in lists or in libraries, we will use a Contacts List to hold our users’ information. We need anonymous users to be able to contribute to this list by adding their contacts without giving them any sort of access to the list views. In addition, we need to set in motion the content approval feature provided by SharePoint to stop subscribers from receiving e-mails unless they are permitted.
With the exception of the forms based authentication module and a handful of InfoPath forms, this project is using nearly all out of the box SharePoint functionality. Before I wrap up this min-case study, I want to point out something very important – no on involved with this project (aside from my company of course) has any idea that a thing called “SharePoint” is playing such a fundamental technical role. Nearly all of my end users view this as “the web site.” Our client values us because we’re solving their business problem. SharePoint is a great technical blob of goodness, but done right, that’s irrelevant to end users. They need a problem solved, not a wonderful blob of technology.
Applications, computers, file shares all utilize AD for permissions for starters. AD when it comes to SharePoint it can be looked at in two parts. The user and the security group.
Still hunting for the holy grail of a solution that ONLY allows users to view or edit documents they have created themselves.
From Mark Miller:
This case study is in response to an article where I asked the question "40+ clients, many documents… what are my options?". You can read Mike’s reply to that article. It is #4 in the comments. I asked him to send me a case study outlining his thinking process for managing [...]
Here’s a question that comes up quite a bit. This time, it was on Stump the Panel:
Does anyone know how I can use one SharePoint List but have different site users only access specific views (kinda like security trimming views) The scenario is I am working with some lawyers who should only access data on [...]
