Weekly Newsletter Signup



• Upcoming
  Live Online Workshops

  • SharePoint Charts and Graphs: Part 01 (Google and Yahoo APIs)
  • SharePoint Charts and Graphs: Part 02 (Sparklines)
  • SharePoint Charts and Graphs: Part 03 (Gantt Charts)
  • Create a Master Calendar in SharePoint
  • jQuery Animations in SharePoint
  • SharePoint WSS Dashboards: No Code Required
  • Become Your Company's SharePoint SuperStar!

• Ongoing Series

  • Article Archives (1000+)
    All Authors
  • This Week in SharePoint with Joel
    Joel Oleson
  • jQuery for Everyone
    Paul Grenier
  • The Calculated Column
    Dessie Lunsford
  • The Data View Web Part
    Laura Rogers
  • Stump the Panel: Q&A
  • Subscribe to the Weekly Newsletter
  • SPC09 - Live Media Streams

• Authors

  • Dessie Lunsford
  • Laura Rogers
  • Lee Reed
  • Mark Miller
  • Jim Bob Howard
  • Paul Galvin
  • Paul Grenier
  • Toni Frankola
  • Woody Windischman

• SharePoint Resources

  • Bits of SharePoint
  • Codeless Solutions for SharePoint
  • Get the Point
  • Innovation Matters
  • Laura Rogers
  • Path to SharePoint
  • Paul Galvin
  • SharePoint 911
  • SharePoint Blank
  • SharePoint Blogs at SharePointU
  • SharePoint Forums at SharePointU
  • SharePoint Screencasts
  • SharePoint Use Cases
  • Social Media Talk Tweets
  • The Sanity Point
  • The Weekly Newsletter  

At the Microsoft SharePoint Conference 2009, I had the distinct pleasure to present the Introduction to SharePoint Designer 2010 session. The early estimates are that over 1000 people attended that session. I personally had a real good time talking about SharePoint Designer since, aside from the facts that it’s my favorite tool to customize SharePoint and that I co-authored the book on SharePoint Designer 2007, so many enhancements have been made to this product that I didn’t have to use the “maybe this feature will be included in the next version” answer even once in the session Q&A! Awesome!

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 [...]