Sharing calendars, setting permissions

%3CLINGO-SUB%20id%3D%22lingo-sub-136833%22%20slang%3D%22en-US%22%3ESharing%20calendars%2C%20setting%20permissions%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-136833%22%20slang%3D%22en-US%22%3E%3CP%3EI%20got%20this%20question%20from%20a%20client%20about%20sharing%20calendars%20between%2055%20coworkers%2C%20managers%20and%20assistants.%20I'm%20asking%20their%20question%20here%2C%20because%20they%20ask%20me%20this%20%22because%20we%20can't%20seem%20to%20set%20this%20with%20the%20Exchange%20options%22.%20I'm%20yet%20to%20find%20out%20if%20this%20is%20a%20knowledge%20issue%20or%20that%20they%20have%20in%20fact%20tried%20the%20exchange%20options%20and%20this%20is%20a%20limitation%20of%20Exchange.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EQuestion%201%3A%3C%2FP%3E%0A%3CP%3EThe%20default%20setting%20in%20Outlook%20is%20Free%2FBusy%2C%20so%20if%20you%20open%20a%20coworkers%20calendar%20you%20only%20see%20Busy%20and%20no%20details%20of%20the%20appointment.%26nbsp%3BMy%20client%20wants%20people%20to%20see%20more%20details%20of%20the%20appointment%3A%26nbsp%3Bsubject%20and%20location.%20But%20not%20top%20open%20it%20(*%20I%20guess%20see%20body%20and%20attachments%3F%20*).%20And%20not%20create%20appointments.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EI%20think%20this%20is%20done%20by%20setting%20the%20level%20for%20%22Default%22%20in%20a%20calendar%20to%20%22Free%2FBusy%20time%2C%20subject%2C%20location%22%3F%20Does%20every%20user%20need%20to%20do%20it%20for%20their%20own%20calendar%20or%20can%20this%20be%20done%20remote%20by%20an%20administrator%3F%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EQuestion%202%3C%2FP%3E%0A%3CP%3EThere%20are%205%20assistants%20who%20are%20allowed%20to%20create%20appointments%20at%20other%20users%20(*%20I%20guess%20all%2055)%20calendar%2C%20but%20rather%20not%20open%20(*%20I%20guess%20see%20body%20and%20attachments%20*)%20of%20existing%20ones.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EThen%202%20assistants%20need%20to%20have%20permission%20to%20create%2C%20change%2C%20move%20and%20open%20calendar%20items%20of%20specific%20persons%20(managers)%2C%20except%20for%20private%20items.%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EIs%20this%20possible%20within%20Exchange%3F%20Does%20everyone%20need%20to%20add%20the%205%20assistants%20to%20their%20calendar%20as%20contributors%3F%20And%20the%20managers%2C%20do%20they%20add%20the%20assistants%20as%20Editor%3F%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3EQuestion%203%3C%2FP%3E%0A%3CP%3EDo%20all%2055%20people%20need%20to%20do%20this%20on%20their%20own%3F%20Do%20I%20need%20to%20write%20instructions%3F%20Or%20can%20this%20be%20managed%20and%20set%20centrally%3F%3CBR%20%2F%3E%3CBR%20%2F%3E%3C%2FP%3E%0A%3CP%3EThanks!%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-136833%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EExchange%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EOutlook%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-138205%22%20slang%3D%22en-US%22%3ERe%3A%20Sharing%20calendars%2C%20setting%20permissions%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-138205%22%20slang%3D%22en-US%22%3EWe%20haven't%20started%20or%20planned%20any%20work%20for%20this%20yet%2C%20but%20it's%20in%20our%20list!%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-137930%22%20slang%3D%22en-US%22%3ERe%3A%20Sharing%20calendars%2C%20setting%20permissions%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-137930%22%20slang%3D%22en-US%22%3E%3CP%3EFor%20now%2C%20we%20only%20have%20the%20option%20to%20set%20it%20per%20mailbox.%20We%20discussed%20this%20recently%20with%20Julia%20though%2C%20and%20she%20mentioned%20that%20they%20will%20explore%20the%20options%20available%20to%20make%20this%20(pre-)configurable%20across%20all%20mailboxes.%20Not%20sure%20if%20she%20can%20share%20any%20news%20on%20this%20yet%20%3A)%3C%2Fimg%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-137900%22%20slang%3D%22en-US%22%3ERe%3A%20Sharing%20calendars%2C%20setting%20permissions%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-137900%22%20slang%3D%22en-US%22%3EThank%20you.%20Do%20I%20set%20these%20permissions%20for%20each%20mailbox%20(and%20again%20when%20a%20new%20user%2Fmailbox%20is%20created)%2C%20or%20do%20I%20change%20a%20central%20setting%20on%20which%20new%20mailboxes%20are%20created%3F%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-137122%22%20slang%3D%22en-US%22%3ERe%3A%20Sharing%20calendars%2C%20setting%20permissions%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-137122%22%20slang%3D%22en-US%22%3ETo%20add%20on%20a%20few%20more%20notes%3A%3CBR%20%2F%3E*%20I%20agree%20with%20Vasil%20that%20setting%20Default%20to%20LimitedDetails%20is%20best%20option%20for%20the%20reading%20scenario.%3CBR%20%2F%3E*%20You%20can%20set%20these%20permissions%20programmatically%20using%20the%20Add%2FSet-MailboxFolderPermission%20cmdlet.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-136935%22%20slang%3D%22en-US%22%3ERe%3A%20Sharing%20calendars%2C%20setting%20permissions%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-136935%22%20slang%3D%22en-US%22%3E%3CP%3E1)%20You%20as%20the%20admin%20can%20do%20it%20-%20set%20the%20Default%20level%20to%20LimitedDetails%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E2)%20Don't%20think%20so%2C%20unless%20you%20want%20to%20mark%20all%20existing%20ones%20as%20Private.%20The%20permissions%20you%20grant%20will%20apply%20to%20all%20items%2C%20expect%20for%20private%2C%20and%20while%20you%20have%20the%20%22edit%20only%20own%20events%22%20level%20of%20permissions%2C%20there%20is%20no%20%22view%20only%20own%20events%22%20level%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E3)%20You%20as%20the%20admin%20should%20be%20able%20to%20grant%20the%20necessary%20permissions%3C%2FP%3E%0A%3CP%3E%26nbsp%3B%3C%2FP%3E%0A%3CP%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F25112%22%20target%3D%22_blank%22%3E%40Julia%20Foran%3C%2FA%3E%26nbsp%3Bmight%20want%20to%20hear%20more%20on%20your%20specific%20scenario.%3C%2FP%3E%3C%2FLINGO-BODY%3E
Highlighted
Frequent Contributor

I got this question from a client about sharing calendars between 55 coworkers, managers and assistants. I'm asking their question here, because they ask me this "because we can't seem to set this with the Exchange options". I'm yet to find out if this is a knowledge issue or that they have in fact tried the exchange options and this is a limitation of Exchange.

 

Question 1:

The default setting in Outlook is Free/Busy, so if you open a coworkers calendar you only see Busy and no details of the appointment. My client wants people to see more details of the appointment: subject and location. But not top open it (* I guess see body and attachments? *). And not create appointments.

 

I think this is done by setting the level for "Default" in a calendar to "Free/Busy time, subject, location"? Does every user need to do it for their own calendar or can this be done remote by an administrator?

 

Question 2

There are 5 assistants who are allowed to create appointments at other users (* I guess all 55) calendar, but rather not open (* I guess see body and attachments *) of existing ones.

 

Then 2 assistants need to have permission to create, change, move and open calendar items of specific persons (managers), except for private items.

 

 

 

Is this possible within Exchange? Does everyone need to add the 5 assistants to their calendar as contributors? And the managers, do they add the assistants as Editor?

 

Question 3

Do all 55 people need to do this on their own? Do I need to write instructions? Or can this be managed and set centrally?

Thanks!

5 Replies
Highlighted

1) You as the admin can do it - set the Default level to LimitedDetails

 

2) Don't think so, unless you want to mark all existing ones as Private. The permissions you grant will apply to all items, expect for private, and while you have the "edit only own events" level of permissions, there is no "view only own events" level

 

3) You as the admin should be able to grant the necessary permissions

 

@Julia Foran might want to hear more on your specific scenario.

Highlighted
To add on a few more notes:
* I agree with Vasil that setting Default to LimitedDetails is best option for the reading scenario.
* You can set these permissions programmatically using the Add/Set-MailboxFolderPermission cmdlet.
Highlighted
Thank you. Do I set these permissions for each mailbox (and again when a new user/mailbox is created), or do I change a central setting on which new mailboxes are created?
Highlighted

For now, we only have the option to set it per mailbox. We discussed this recently with Julia though, and she mentioned that they will explore the options available to make this (pre-)configurable across all mailboxes. Not sure if she can share any news on this yet :)

Highlighted
We haven't started or planned any work for this yet, but it's in our list!