![]() ![]() Items that are extrememly sensitive should probably not be stored in Exchange in the first place, or you should take off all delegate / view rights to your mailbox. The end result is that people should realize that just because they mark an appointment or other item private in Outlook, it doesn’t mean that no one else will be able to see it. This architecture is common to all versions of Outlook and Exchange, through 2010, and is not really a bug, so much as an architectural decision by Microsoft to keep item-level permissions in the client-tier. The client applications look at that field to determine whether to display the item. ![]() Exchange itself does not support any kind of item-level security or privacy, and only has a field called “sensitivity” which is used by Outlook and OWA. However, you should keep in mind that this privacy is only a feature of the client application–Outlook or OWA–and is not inherent to Exchange. In Outlook or OWA, other users will see a placeholder for the private items, but won’t be able to view any of the details. In these situations, people may rely on marking sensitive items private to hide them from other users. Users may also delegate rights to other users to view their messages, tasks, and contacts. A common situation in organizations is to make calendars public, so that employees can see other employee’s availability, and collaborate better. ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
January 2023
Categories |