By ‘public folder’, I mean any of the objects you see in your folder list in Outlook underneath “All Public Folders”.  It can be a calendar, contact list, task list, among others.

The best, easiest way to manage permissions on public folders in Exchange is through Outlook.  However, getting it set up so you can do that is not the most intuitive process.

To be able to set permissions on a public folder, you must be the owner of it.  Even if you are a domain/enterprise/schema admin, if you don’t own the public folder, you will not be able to modify the permissions of the folder via Outlook.  You must give your account ownership of the public folder first.  The way to do that is through the Exchange Management Shell.

Here is the command you will need to run:

Add-PublicFolderClientPermission -Identity <PublicFolder> -User “Username” -AccessRights <Right>

And for example, let’s say you have a calendar called “Company Calendar” directly under ‘All Public Folders’, and you want to give ownership of it to John Doe (username ‘jdoe’).  The command would be:

Add-PublicFolderClientPermission -Identity “\Company Calendar” -User “jdoe” -AccessRights Owner

and if, underneath All Public Folders, the company calendar is in another folder called Calendars, you would run the following instead:

Add-PublicFolderClientPermission -Identity “\Calendars\Company Calendar” -User “jdoe” -AccessRights Owner

There are other permissions you can set besides ‘Owner’, such as ‘Publishing Editor’, etc., with this command.  However, if your goal is to be able to manage the PF permissions from Outlook, just give ownership with this command then go to Outlook to set the remaining permissions.

Here is an article on Technet for more information on configuring public folder permissions:

2 Replies to “Setting Client Permissions on Exchange 2007 Public Folders”

  1. This was the easiest, no-nonsense explanation of how this process works that I was able to find online, anywhere. Thank you.

Leave a Reply to Noel Cancel reply

Your email address will not be published. Required fields are marked *