I know how to create basic SharePoint lists to track information, but I would like create a dynamic workflow application for submitting and tracking helpdesk requests.

I know how to create basic SharePoint lists to track information, but I would like create a dynamic workflow application for submitting and tracking helpdesk requests.

I know how to create basic SharePoint lists to track information, but I would like create a dynamic workflow application for submitting and tracking helpdesk requests.

This tip shows how you can create a special library to host Web Part Pages and how you can use these to show filtered content for different functions. Using this method, you can consolidate your content onto centralized lists, while offering filtered views of the content for different functions, teams or projects, etc.

Being new to SharePoint, the combinations of possibilities seem endless. There are site collections, sites, web parts, libraries, lists, content editor web pages, calendars, tasks, discussion boards, wikis...the list goes on and on. How does one put it all together in a way that makes sense?

We are starting to use SharePoint calendars to manage projects, however we are running into conflicts with both unrelated project calendars and individual user calendar items in Outlook. Is there a way users can coordinate information between all these silos of information?

Users in my organization are confused about whether to continue using file servers or to begin using SharePoint document libraries. Some users continue using file servers, while others enjoy the visual aspect of using a web browser to accessing files. I am new at administering SharePoint technologies and I am not sure what the right answer is.

How to use the check out feature in SharePoint document libraries.

When creating business solutions with SharePoint lists, one of the field types is the 'choice' column. This is handy to offer users a static list of values. This can be important to help users not have to lookup categorical or other frequently used information. It can also help when building custom views to have consistently chosen (and correctly spelled) data. However, I continually get requests to modify the list of choices. Can I give a few select users the power to maintain their own choices without giving them control over the rest of the list structure?

There are many users collaborating on document creation with MOSS 2007 or WSS3. It is critical that some level of control or 'gatekeeping' exists. Is there are way to manage this so that everyone knows when a document has been finalized and approved?