In an Exchange environment, you can use folder-level permissions to enable a delegator to control a delegate’s access to specific folders. A delegator, also known as a principal, can assign folder-level permissions to delegates to allow delegates to perform actions on the principal’s behalf. You can set individual permissions on a folder, or you can set a permission level on a folder. The following are the individual permissions that you can set:
Can Create Subfolders
Is Folder Owner
Is Folder Contact
Is Folder Visible
The permissions are predefined by Microsoft but are customizable. See the table below, for Permissions Levels (definitions) that are available:
Allows full rights to the mailbox’s (Calendar or Folder) , including assigning permissions; it is recommended not to assign this role to anyone
Create, read, edit, and delete all items; create subfolders
Create, read, edit, and delete all items
Create and read items; create subfolders; edit and delete items created by the user.
Create and read items; edit and delete items they’ve created.
Create and read items; delete items created by the user.
No permissions are set for the selected user on the specified calendar or folder.
Folder Permisions with respect to Team Helpdesk: So now you have Team Helpdesk up and running for your support team. By default, the permission on each subfolder for all users is set to ‘Author’. Only the user (manager) who had performed the installation has got ‘Owner’ permission. Hence, it is this user (manager) who would need to grant permission to the folders for all members of the helpdesk team. Without a proper permission structure defined, technicians accessing the Team Helpdesk folders would not be able to perform most of the helpdesk tasks such as creating new support cases, working on their assigned cases etc.
The following table summarizes the ideal permission levels recommended on Team Helpdesk sub-folder:
|History Ongoing||At least ‘Editor‘ permission to all helpdesk technicians|
|History Resolved||At least ‘Editor‘ permission to all helpdesk technicians|
|KB||At least ‘Author‘ permission to all helpdesk technicians|
|Ongoing Cases||At least ‘Editor‘ permission to all helpdesk technicians|
|Resolved Cases||At least ‘Editor‘ permission to all helpdesk technicians|
|Schedules||At least ‘Editor‘ permission to all helpdesk technicians|
‘Publishing Editor‘ permission to technicians with admin-access*
|Settings||At least ‘Editor‘ permission to all helpdesk technicians|
*Technicians with admin access may be required to create new calendars in this folder when the ‘Maintain technicians due date schedule’ is enabled in Automation options.
We recommend that a users group consisting of all technicians of the helpdesk be created such that helpdesk manager (owner) can easily assign permission to the group as a whole, instead of undergoing multiple steps of selecting and granting the same permission to each technician. In the example below, a group ‘ServiceDesk’ comprising of all helpdesk users is granted editor permission over the ‘Ongoing Cases’ folder
Remark: Setting up a correct set of permission levels on the Team Helpdesk folders is very important, because, sometime someone could inadvertently move or delete the subfolder and doing that would break the functionality of Team Helpdesk for all users.