Guest Author: Asif Rehmani – SharePoint Server MVP, MCT
SharePoint eLearning

In the last article, I described the screens and interfaces that users would interact with in SharePoint Designer 2010 (SPD). This article will dig into working with specifically the settings and customizations you can make at the SharePoint site level using SPD. So let’s dive in!

As far as site creation is concerned, SPD can be used to create subsites using any of the available site templates. However, SharePoint Designer cannot be used to create a top level site or a site collection itself. You would need to perform these actions using any of the following options:

• Central Administration
• PowerShell
• Programmatically using the object model
• Stsadm.exe (this utility was heavily used in administering SharePoint 2007. However, PowerShell is recommended for SharePoint 2010 administration)

SharePoint Designer can open any existing SharePoint 2010 sites (SharePoint 2007 is not supported). The image below shows the Summary Page of a site. Each area on the summary page is marked with a number. Right below the image, each of the areas is discussed in detail.

Site Information

1.  The summary page is broken up into multiple sections. These sections show you a variety of information about the site. The sections themselves are not customizable. More cannot be added and the existing ones cannot be deleted. You can minimize these sectional panels by clicking on them, but that’s about it.

2.  Title and Description of site are completely configurable. Just click on the existing wording and start typing to change it. Once done, don’t forget to press the Save button at the top left to commit your changes.

3.  The Web Address link takes you directly to the site’s home page in the browser.

4.  SharePoint Version – The build number of the SharePoint deployment

Server Version – Just shows you that SharePoint is running on Internet Information Services

5.  Total Storage Used – This number is deceiving. Upon first look, it seems like this is site focused. It’s not. This number shows you the current storage used by the site collection.

% Available Storage Used – Quota templates can be created through Central Administration and assigned to a site collection. If the quota is set, this value would show the % of quota already used up.

Customization

6.  Edit site home page – The first thing a site admin would usually do is to edit the home page and modify its content. That’s why this link is available here in the customization section. Clicking this link will open up the home page (Home.aspx) of the site in safe editing mode. The safe editing mode makes sure that none of the edits in the page will cause it to become customized (or unghosted). This also means that the Master Page, which provides the chrome of the site, cannot be customized in this mode. There is another mode (Advanced) available if needed. You can get to Advanced mode by going to the Home.aspx page through the Site Pages library section in SPD.

7.  Change site theme – Changing a site’s theme is not supported within SPD. When you click on this link, it takes you to the page in the browser where you can apply any one of the available themes to the site.

Settings

8. Display Quick Launch – Shows/hides the Quick Launch of the site

Enable Tree View – Shows/hides the Tree View of the site

Notes:

1. It’s a good idea to use one and not both. Otherwise, you will end up with links to the same resources in two different places thus confusing your users.
2. Both show links which are security trimmed.
3. Quick Launch is configurable so you can hide or show links to site components as needed to not clutter up the navigation too much.
4. Tree View shows all of the site components that the end user has permission to see.

Recommendation:
Use Quick Launch for a nicely grouped organization of your site components.

9.  Enable Site RSS Feeds – Enables/disables the RSS feed for the site. This is a good way for end users to keep abreast of changes happening to their site by subscribing to the site’s RSS feed.

Subsites

10.  The list of subsites directly under this site appears here. This view is also security trimmed so that if a user does not have access to a site, he won’t see that site in this list.

Permissions

11.  This view shows the SharePoint groups who currently have permissions on the site. It also shows what permission level each group has. Using this section, you can also configure user permissions for the site. Security configuration options within SPD are a deep topic and will be covered in another article.

Hopefully, this post gave you a good perspective on the type of site level setting and customization options available within SharePoint Designer 2010. Future articles will attempt to detail other areas of this application.

Guest Author: Asif Rehmani – SharePoint Server MVP, MCT
SharePoint eLearning

Asif has over 10 years of training and consulting experience in the IT industry. He has been training and consulting on primarily SharePoint technologies for over 4 years. He is a SharePoint Server MVP and MCT.

Asif is the co-author of the book “Professional SharePoint Designer 2007“ by Wrox publications. He has also been a speaker on SharePoint topics at several conferences over the years including Microsoft’s SharePoint Conference, SharePoint Connections, Advisor Live, and Information Workers Conference.

Asif runs a SharePoint eLearning website (http://www.sharepoint-elearning.com) which provides dozens of SharePoint Video Tutorials. He was the co-founder and is currently one of the active leaders of the Chicago SharePoint User Group.

Every once in a while your customer might ask you to customize permissions for a document library in such a way that authors can only change their own documents. There was no such feature for document libraries in SharePoint 2007, and the “problem” is still present in v2010. (Both versions support automatic item-level permissions OOTB for other lists like Tasks).

In Part 1 of this article I tried to solve the problem for SharePoint 2007 with Workflows, but never found the time to complete it and create custom workflow activities for SharePoint Designer. In 2010, SharePoint Designer comes to the rescue, as it has similar workflow activities OOTB!

In this article we will examine how you can create a workflow that will customize item permissions for each document submitted to a document library (only the Author will have contribute permissions). These SharePoint Designer 2010 workflow activities can also be used in various workflow scenarios where permissions need to be revoked after an item is submitted (e.g. Annual Leave Requests, various approvals etc.).

Here is what you need to do:

• Create a new Document Library (e.g. Top Secret Documents)
• Go to Document Library Settings > Permissions for this document library
• Click on the Stop Inheriting Permissions command from the ribbon


• Revoke permissions for all but a few important groups (e.g. Portal Owners and Portal Members).
  Please note: Steps 2. – 4- are optional but the workflow is going to be much simpler if there are fewer permissions to manage
• Open your site in SharePoint Designer, and select theWorkflows option and your list from the ribbon


• Type the name for the new workflow (e.g. Customize Permissions)
• Insert a new Impersonation Step. This special step runs each activity as workflow author.
  Make sure the workflow author (you) has proper privileges to manage permissions for this list.


• From the list of workflow actions choose “Replace Item Permissions
• Click Replace these permissions


• In the dialog click Add
• In the Choose permission to grant dialog click Contribute, and then click the Choose… button
• Add User who created current item to the Selected users list
• Click the workflow name (e.g. “Customize Permissions”) to manage workflow settings


• Make sure you have selected the correct Start options


• Publish your workflow

Once a user adds a document to a document library this workflow will revoke permission from other users and grant contribute permissions to the document author.

You can also customize this workflow and add permissions for other users as well.

Guest Author: Toni Frankola
SharePoint Use Cases

Toni started his Web adventure in late 90’s and has been working with various web technologies ever since. These days his main focus is SharePoint technology. He is active in the SharePoint community via his SharePoint blog at http://www.sharepointusecases.com/ and Twitter http://twitter.com/tonifrankola, and also speaks about SharePoint at various SharePoint conferences. Toni runs his own company Acceleratio Ltd., that specializes in SharePoint consulting and developing software products, and leads the Croatian SharePoint User Group.