Outlook mobile & OWA apps treat folder sharing permissions differently from Outlook for Windows

%3CLINGO-SUB%20id%3D%22lingo-sub-2701061%22%20slang%3D%22en-US%22%3EOutlook%20mobile%20%26amp%3B%20OWA%20apps%20treat%20folder%20sharing%20permissions%20differently%20from%20Outlook%20for%20Windows%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2701061%22%20slang%3D%22en-US%22%3E%3CP%3EUsing%20Outlook%20for%20Windows%20with%20Exchange%20Online%2C%20if%20I%20grant%20a%20colleague%20'Reviewer'%20(i.e.%20read-only)%20permission%20to%20my%20Inbox%20then%20they%20can%20open%20and%20read%20my%20emails%20but%20this%20will%20not%20change%20the%20status%20of%20those%20messages%20from%20'unread'%20to%20'read'.%20However%2C%20if%20my%20colleague%20instead%20uses%20Outlook%20mobile%20or%20OWA%20to%20read%20those%20same%20messages%2C%20the%20message%20status%20%3CU%3Edoes%20change%3C%2FU%3E%20from%20'unread'%20to%20'read'.%26nbsp%3B%20Consequently%2C%20I%20can%20no%20longer%20easily%20see%20which%20of%20my%20messages%20I%20have%20and%20haven't%20read%20yet%3A%20my%20colleague's%20actions%20are%20altering%20the%20read%2Funread%20status%20of%20my%20messages%20in%20my%20Inbox%26nbsp%3B%20while%20he%20only%20has%20'read'%20permission.%20By%20design%2C%20it%20appears%2C%20Outlook%20mobile%20and%20OWA%20break%20this%20fundamental%20convention%20of%20email%20processing.%26nbsp%3B%20If%20I%20did%20want%20the%20status%20of%20my%20message%20to%20change%20from%20'unread'%20to%20'read'%20when%20someone%20else%20reads%20it%20first%20then%20-%20under%20Outlook%20for%20Windows%20-%20I%20simply%20given%20them%20''read%20%2F%20write'%20permission.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ESo%2C%20is%20this%20really%20a%20problem%20-%20surely%20there%20must%20be%20workarounds%3F%26nbsp%3B%20Well%2C%20in%20the%20context%20of%20our%20business%26nbsp%3B%20-%20Yes%20-%20it%20actually%20is%20a%20real%20problem%20for%20which%20I%20cannot%20yet%20identify%20a%20solution%20short%20of%20getting%20Outlook%20mobile%20%26amp%3B%20OWA%20changed%20to%20become%20consistent%20with%20Outlook%20client.%20-%20as%20they%20should%20be.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI'd%20be%20grateful%20for%20any%20comments%20or%20suggestions.%20For%20anyone%20else%20who%20sees%20this%20as%20a%20problem%20I%20provide%20the%20following%20elaboration%20which%20puts%20the%20problem%20into%20a%20business%20context%20and%20discusses%20some%20possible%20workarounds.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSTRONG%3EOutlook%20behaviour%3C%2FSTRONG%3E%3C%2FP%3E%3CP%3EUsing%20Outlook%20client%20for%20Windows%2C%20if%20I%20open%20an%20unread%20message%20in%20a%20shared%20folder%20to%20which%20I%20have%20been%20granted%20%E2%80%98Reviewer%E2%80%99%20(i.e.%20read-only)%20permission%2C%20the%20message%20is%20not%20marked%20as%20%E2%80%98read%E2%80%99%20for%20either%20me%20or%20the%20folder%20owner.%20However%2C%20if%20I%20use%20Outlook%20for%20Android%20or%20OWA%20to%20open%20the%20same%20message%2C%20that%20message%20is%20automatically%20marked%20as%20read%20%E2%80%93%20which%20the%20folder%20owner%20does%20not%20want.%20Also%2C%20I%20am%20permitted%20to%20manually%20mark%20it%20as%20read%2Funread%20whereas%20I%20get%20a%20permissions%20error%20trying%20to%20do%20this%20under%20Outlook%20for%20Windows.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSTRONG%3EWhy%20is%20this%20a%20problem%3F%3C%2FSTRONG%3E%3C%2FP%3E%3CP%3EAs%20an%20example%2C%20our%20construction%20company%20employs%20a%20number%20of%20project%20managers%20and%20one%20part-time%20bookkeeper.%20Environment%20is%20Microsoft%20365%20Business.%20The%20bookkeeper%20receives%20and%20sends%20all%20their%20correspondence%20via%20the%20MS365%20user-id%20%26amp%3B%20email%20account%20%3CA%20href%3D%22mailto%3Aaccounts%40company.com%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%22%3E%3CEM%3Eaccounts%40company.com%3C%2FEM%3E%3C%2FA%3E.%20When%20dealing%20with%20clients%2C%20suppliers%20and%20subcontractors%26nbsp%3B%20our%20project%20managers%20need%20on-demand%2C%20read-only%20visibility%20of%20%3CA%20href%3D%22mailto%3Aaccounts%40company.com%E2%80%99s%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%22%3E%3CEM%3Eaccounts%40company.com%E2%80%99s%3C%2FEM%3E%3C%2FA%3E%20email%20messages.%20To%20achieve%20this%20the%20bookkeeper%20%2F%20folder%20owner%20has%20granted%20them%20%E2%80%98Reviewer%E2%80%99%20permission%20to%20the%20Inbox%20and%20Sent%20Mail%20folders%20of%20%3CA%20href%3D%22mailto%3Aaccounts%40company.com%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%22%3E%3CEM%3Eaccounts%40company.com%3C%2FEM%3E%3C%2FA%3E.%20When%20everyone%20was%20using%20just%20Outlook%20for%20Windows%20this%20arrangement%20worked%20very%20well.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EHowever%2C%20our%20project%20managers%20increasingly%20want%20the%20flexibility%20of%20also%20using%20Outlook%20mobile%20and%20OWA%20depending%20whether%20they%20are%20in%20or%20out%20of%20the%20office.%20These%20apps%20work%20very%20well%20except%20for%20one%20key%20issue%3A%26nbsp%3B%20the%20%E2%80%98Reviewer%E2%80%99%20permission%20works%20differently%20from%20the%20way%20it%20does%20with%20Outlook%20for%20Windows.%20When%20the%20bookkeeper%20uses%20Outlook%20for%20Windows%20to%20open%20a%20message%20in%20the%20Inbox%20of%20their%20mail%20account%20%3CA%20href%3D%22mailto%3Aaccounts%40company.com%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%22%3E%3CEM%3Eaccounts%40company.com%3C%2FEM%3E%3C%2FA%3E%20then%20the%20status%20of%20the%20message%20visibly%20changes%20from%20%E2%80%98unread%E2%80%99%20to%20%E2%80%98read%E2%80%99%3A%20this%20is%20the%20standard%20and%20expected%20behaviour%20of%20all%20email%20applications%20including%20Outlook.%20%26nbsp%3BIf%20a%20project%20manager%20using%20Outlook%20Windows%20client%20opens%20that%20same%20message%20before%20the%20bookkeeper%20does%20then%20the%20message%20status%20is%20not%20changed%20to%20%E2%80%98read%E2%80%99%20because%20their%20%E2%80%98Reviewer%E2%80%99%20permission%20prevents%20any%20changes%20%E2%80%93%20including%20alteration%20of%20%E2%80%98read%2Funread%E2%80%99%20status%20-%20from%20being%20made%20to%20a%20message.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EHowever%2C%20if%20the%20same%20project%20manager%20uses%20Outlook%20mobile%20or%20OWA%20to%20open%20that%20same%20message%20then%20message%20status%20changes%20from%20%E2%80%98unread%E2%80%99%20to%20%E2%80%98read%E2%80%99%20for%20all%20to%20see%20%E2%80%93%20including%20the%20bookkeeper.%26nbsp%3B%20Problem!%26nbsp%3B%20Why%3F%20Because%20the%20bookkeeper%20owns%20that%20Inbox%20and%20is%20responsible%20for%20seeing%20that%20all%20accounts%20communications%20are%20processed%20properly.%26nbsp%3B%20The%20bookkeeper%20uses%20the%20read%2Funread%20status%20of%20messages%20in%20the%20conventional%20way%20%E2%80%93%20i.e.%20to%20alert%20them%20to%20the%20arrival%20of%20a%20new%20%E2%80%98to%20do%E2%80%99%20item%20and%20to%20distinguish%20between%20what%20they%20have%20processed%20and%20have%20still%20to%20process.%20Having%20one%20or%20more%20other%20co-workers%20altering%20the%20status%20of%20%E2%80%98their%E2%80%99%20messages%20is%20a%20real%20problem.%20It%E2%80%99s%20the%20same%20as%20the%20bookkeeper%20arriving%20at%20their%20work%20desk%20in%20the%20morning%20and%20finding%20someone%20has%20gone%20through%20their%20in-tray%20and%20opened%20some%20of%20their%20mail.%26nbsp%3B%20The%20sense%20of%20a%20loss%20of%20personal%20control%20of%20the%20workflow%20is%20at%20the%20heart%20of%20it.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EBeing%20able%20to%20see%20at%20a%20glance%20whether%20there%20are%20any%20unread%20messages%20in%20your%20Inbox%20is%20the%20most%20basic%20of%20email%20features.%20If%20someone%20to%20whom%20you%20gave%20read-only%20access%20to%20your%20inbox%20might%20have%20marked%20some%20or%20all%20of%20your%20messages%20as%20%E2%80%98read%E2%80%99%20then%20that%E2%80%99s%20a%20problem.%26nbsp%3B%20Which%20ones%3F%26nbsp%3B%20It%E2%80%99s%20worrying%20to%20always%20have%20this%20possibility%20to%20deal%20with.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSTRONG%3ECan%20the%20problem%20be%20avoided%3F%3C%2FSTRONG%3E%3C%2FP%3E%3CP%3EGiven%20the%20current%20behaviour%20of%20the%20Outlook%20mobile%20and%20OWA%20apps%20we%20have%20looked%20at%20these%20alternatives%20and%20workarounds-%3C%2FP%3E%3CP%3E%3CSTRONG%3ERecreate%20%3C%2FSTRONG%3E%3CA%20href%3D%22mailto%3Aaccounts%40company.com%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%22%3E%3CSTRONG%3Eaccounts%40company.com%3C%2FSTRONG%3E%3C%2FA%3E%3CSTRONG%3E%20as%20a%20mail%20enabled%20public%20folder%3C%2FSTRONG%3E%20%E2%80%93%20this%20would%20offer%20read%20%2F%20unread%20status%20on%20a%20per-user%20basis.%20Public%20folders%20are%20supported%20on%20OWA%20but%20not%20on%20mobile.%20Also%2C%20project%20managers%20do%20not%20need%20or%20want%20per-user%20read%20status.%20Bookkeeper%20also%20loses%20convenience%20of%20having%20only%20one%20folder%20in%20their%20profile%20to%20manage%2C%20search%20etc.%3C%2FP%3E%3CP%3E%3CSTRONG%3EManually%20%E2%80%98mark%20as%20unread%E2%80%99%3C%2FSTRONG%3E%20-%26nbsp%3B%20appeal%20to%20project%20managers%20if%20they%20open%20a%20message%20in%20%3CA%20href%3D%22mailto%3Aaccounts%40company.com%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%22%3Eaccounts%40company.com%3C%2FA%3E%20that%20is%20marked%20as%20unread%20when%20using%20Outlook%20mobile%20or%20OWA%20that%20they%20manually%20mark%20it%20as%20%E2%80%98unread%E2%80%99%20after%20reading%20it.%26nbsp%3B%20This%20will%20not%20be%20successful%20in%20our%20organisation.%3C%2FP%3E%3CP%3E%3CSTRONG%3ECategorise%3C%2FSTRONG%3E%20%E2%80%93%20use%20Outlook%E2%80%99s%20message%20categories%20to%20indicate%20a%20separate%20%E2%80%98read%E2%80%99%20or%20%E2%80%98unread%E2%80%99%20status.%20Again%2C%20we%20consider%20an%20unworkable%20expectation%20of%20the%20average%20worker.%3C%2FP%3E%3CP%3E%3CSTRONG%3ERecreate%20%3C%2FSTRONG%3E%3CA%20href%3D%22mailto%3Aaccounts%40company.com%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%22%3E%3CSTRONG%3Eaccounts%40company.com%3C%2FSTRONG%3E%3C%2FA%3E%3CSTRONG%3E%20as%20an%20Exchange%20SharedMailbox%20rather%20than%20a%20UserMailbox%3C%2FSTRONG%3E%20%E2%80%93%20a%20SharedMailbox%20behaves%20the%20same%20as%20an%20Exchange%20UserMailbox%20on%20OWA%20and%20mobile%20so%20the%20problem%20is%20not%20solved.%3C%2FP%3E%3CP%3E%3CSTRONG%3ECreate%20new%20%3C%2FSTRONG%3E%3CA%20href%3D%22mailto%3Aaccounts2%40company.com%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%22%3E%3CSTRONG%3Eaccounts2%40company.com%3C%2FSTRONG%3E%3C%2FA%3E%20%3CSTRONG%3ESharedMailbox%3C%2FSTRONG%3E%20%E2%80%93%20and%20automatically%20forward%20duplicates%20of%20all%20messages%20being%20received%20into%20or%20sent%20from%20%3CA%20href%3D%22mailto%3Aaccounts%40company.com%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%22%3Eaccounts%40company.com%3C%2FA%3E%20to%20this%20mailbox.%20Give%20project%20managers%20access%20to%20the%20Inbox%20and%20Sent%20Items%20of%20this%20mailbox%20which%20is%20not%20used%20by%20bookkeeper.%20This%20will%20solve%20the%20problem%20but%20at%20the%20cost%20of%20duplicating%20all%20%3CA%20href%3D%22mailto%3Aaccounts%40company.com%22%20target%3D%22_blank%22%20rel%3D%22nofollow%20noopener%20noreferrer%22%3Eaccounts%40company.com%3C%2FA%3E%20emails.%20Probably%20the%20best%20solution%20until%20the%20core%20problem%20with%20Outlook%20is%20fixed.%3C%2FP%3E%3CP%3E%26nbsp%3B%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSTRONG%3EWhat%20is%20a%20good%20resolution%20for%20this%20problem%3F%3C%2FSTRONG%3E%3C%2FP%3E%3CP%3EBest%20resolution%20would%20be%20for%20Outlook%20mobile%20and%20OWA%20to%20be%20modified%20to%20properly%20and%20fully%20honor%20the%20permissions%20held%20by%20Exchange%20for%20accessing%20a%20shared%20folder.%20This%20would%20mean%20that%20if%20anyone%20opened%20a%20unread%20message%20in%20a%20folder%20for%20which%20they%20had%20only%20%E2%80%98Reviewer%E2%80%99%20permission%20then%20the%20read%2Funread%20status%20of%20that%20message%20would%20not%20be%20altered%20%E2%80%93%20just%20as%20Outlook%20for%20Windows%20has%20always%20done.%20Outlook%20mobile%20and%20OWA%20should%20handle%20read%20%2F%20unread%20status%20exactly%20the%20same%20way%20they%20currently%20handle%20the%20%E2%80%98flag%E2%80%99%20and%20%E2%80%98categorise%E2%80%99%20functions%2C%20which%20both%20require%20%E2%80%98edit%E2%80%99%20permission%20to%20the%20folder.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EA%20user%E2%80%99s%20email%20experience%20across%20the%20basic%20functions%20of%20Outlook%20for%20Windows%2C%20Outlook%20mobile%20and%20OWA%20should%20be%20as%20simple%20and%20consistent%20as%20possible%2C%20and%20this%20is%20largely%20the%20case%20already.%20But%20it%E2%80%99s%20ironic%20that%20while%20the%20UI%20for%20managing%20permissions%20for%20shared%20folders%20is%20identical%20in%20both%20Outlook%20for%20Windows%20and%20OWA%20(%E2%80%98permissions%20panel%E2%80%99%20function%20not%20yet%20available%20in%20mobile)%20how%20those%20permissions%20affect%20the%20setting%20of%20the%20read%20%2F%20unread%20status%20of%20a%20message%20is%20different%20for%20each%20app.%20%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSTRONG%3Eend.%3C%2FSTRONG%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-2701061%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EExchange%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EOffice%20365%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EOutlook%20for%20Android%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EOutlook%20for%20Windows%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EOutlook%20on%20the%20web%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
Senior Member

Using Outlook for Windows with Exchange Online, if I grant a colleague 'Reviewer' (i.e. read-only) permission to my Inbox then they can open and read my emails but this will not change the status of those messages from 'unread' to 'read'. However, if my colleague instead uses Outlook mobile or OWA to read those same messages, the message status does change from 'unread' to 'read'.  Consequently, I can no longer easily see which of my messages I have and haven't read yet: my colleague's actions are altering the read/unread status of my messages in my Inbox  while he only has 'read' permission. By design, it appears, Outlook mobile and OWA break this fundamental convention of email processing.  If I did want the status of my message to change from 'unread' to 'read' when someone else reads it first then - under Outlook for Windows - I simply given them ''read / write' permission.

 

So, is this really a problem - surely there must be workarounds?  Well, in the context of our business  - Yes - it actually is a real problem for which I cannot yet identify a solution short of getting Outlook mobile & OWA changed to become consistent with Outlook client. - as they should be.

 

I'd be grateful for any comments or suggestions. For anyone else who sees this as a problem I provide the following elaboration which puts the problem into a business context and discusses some possible workarounds. 

 

Outlook behaviour

Using Outlook client for Windows, if I open an unread message in a shared folder to which I have been granted ‘Reviewer’ (i.e. read-only) permission, the message is not marked as ‘read’ for either me or the folder owner. However, if I use Outlook for Android or OWA to open the same message, that message is automatically marked as read – which the folder owner does not want. Also, I am permitted to manually mark it as read/unread whereas I get a permissions error trying to do this under Outlook for Windows.

 

Why is this a problem?

As an example, our construction company employs a number of project managers and one part-time bookkeeper. Environment is Microsoft 365 Business. The bookkeeper receives and sends all their correspondence via the MS365 user-id & email account accounts@company.com. When dealing with clients, suppliers and subcontractors  our project managers need on-demand, read-only visibility of accounts@company.com’s email messages. To achieve this the bookkeeper / folder owner has granted them ‘Reviewer’ permission to the Inbox and Sent Mail folders of accounts@company.com. When everyone was using just Outlook for Windows this arrangement worked very well.

 

However, our project managers increasingly want the flexibility of also using Outlook mobile and OWA depending whether they are in or out of the office. These apps work very well except for one key issue:  the ‘Reviewer’ permission works differently from the way it does with Outlook for Windows. When the bookkeeper uses Outlook for Windows to open a message in the Inbox of their mail account accounts@company.com then the status of the message visibly changes from ‘unread’ to ‘read’: this is the standard and expected behaviour of all email applications including Outlook.  If a project manager using Outlook Windows client opens that same message before the bookkeeper does then the message status is not changed to ‘read’ because their ‘Reviewer’ permission prevents any changes – including alteration of ‘read/unread’ status - from being made to a message.

 

However, if the same project manager uses Outlook mobile or OWA to open that same message then message status changes from ‘unread’ to ‘read’ for all to see – including the bookkeeper.  Problem!  Why? Because the bookkeeper owns that Inbox and is responsible for seeing that all accounts communications are processed properly.  The bookkeeper uses the read/unread status of messages in the conventional way – i.e. to alert them to the arrival of a new ‘to do’ item and to distinguish between what they have processed and have still to process. Having one or more other co-workers altering the status of ‘their’ messages is a real problem. It’s the same as the bookkeeper arriving at their work desk in the morning and finding someone has gone through their in-tray and opened some of their mail.  The sense of a loss of personal control of the workflow is at the heart of it.

 

Being able to see at a glance whether there are any unread messages in your Inbox is the most basic of email features. If someone to whom you gave read-only access to your inbox might have marked some or all of your messages as ‘read’ then that’s a problem.  Which ones?  It’s worrying to always have this possibility to deal with.

 

Can the problem be avoided?

Given the current behaviour of the Outlook mobile and OWA apps we have looked at these alternatives and workarounds-

Recreate accounts@company.com as a mail enabled public folder – this would offer read / unread status on a per-user basis. Public folders are supported on OWA but not on mobile. Also, project managers do not need or want per-user read status. Bookkeeper also loses convenience of having only one folder in their profile to manage, search etc.

Manually ‘mark as unread’ -  appeal to project managers if they open a message in accounts@company.com that is marked as unread when using Outlook mobile or OWA that they manually mark it as ‘unread’ after reading it.  This will not be successful in our organisation.

Categorise – use Outlook’s message categories to indicate a separate ‘read’ or ‘unread’ status. Again, we consider an unworkable expectation of the average worker.

Recreate accounts@company.com as an Exchange SharedMailbox rather than a UserMailbox – a SharedMailbox behaves the same as an Exchange UserMailbox on OWA and mobile so the problem is not solved.

Create new accounts2@company.com SharedMailbox – and automatically forward duplicates of all messages being received into or sent from accounts@company.com to this mailbox. Give project managers access to the Inbox and Sent Items of this mailbox which is not used by bookkeeper. This will solve the problem but at the cost of duplicating all accounts@company.com emails. Probably the best solution until the core problem with Outlook is fixed.

  

What is a good resolution for this problem?

Best resolution would be for Outlook mobile and OWA to be modified to properly and fully honor the permissions held by Exchange for accessing a shared folder. This would mean that if anyone opened a unread message in a folder for which they had only ‘Reviewer’ permission then the read/unread status of that message would not be altered – just as Outlook for Windows has always done. Outlook mobile and OWA should handle read / unread status exactly the same way they currently handle the ‘flag’ and ‘categorise’ functions, which both require ‘edit’ permission to the folder. 

 

A user’s email experience across the basic functions of Outlook for Windows, Outlook mobile and OWA should be as simple and consistent as possible, and this is largely the case already. But it’s ironic that while the UI for managing permissions for shared folders is identical in both Outlook for Windows and OWA (‘permissions panel’ function not yet available in mobile) how those permissions affect the setting of the read / unread status of a message is different for each app.  

 

end.

0 Replies