Outlook Calendar Delegate Permissions Explained

A calendar delegate in Outlook is someone who can act on your calendar without being handed your credentials. The feature is decades old, but it remains the standard mechanism for the executive-assistant workflow: the assistant books meetings, accepts invitations, and manages scheduling conflicts while the executive stays out of the logistics entirely.

The configuration is simple in principle and easy to get wrong in practice. Outlook offers three named permission levels — Reviewer, Author, and Editor — and each controls a different combination of what the delegate can read, create, and modify. Get the level right and the workflow is invisible. Get it wrong and the assistant either lacks the access they need or has more latitude than intended.

This guide explains what each permission level allows, how delegation differs from calendar sharing, where private appointments fit in, and what happens to meeting invitations once a delegate is added. The goal is to give you a precise enough picture that you can choose the right configuration the first time.

What is a calendar delegate in Outlook?#

An Outlook calendar delegate is a person — typically an executive assistant or chief of staff — who has been explicitly authorised to view, create, or modify calendar items on behalf of the calendar owner. Delegation is different from basic calendar sharing: a shared calendar lets someone see your schedule, while a delegate can take actions for you, including accepting or declining meeting invitations sent in your name.

When you add a delegate, Outlook also lets you configure how meeting requests are routed. By default, invitations go to both you and the delegate. You can instead send them to the delegate only, so the calendar owner is not interrupted by scheduling logistics at all. This routing decision is separate from the permission level and is where most misconfigurations happen.

One note for organisations moving to new Outlook: calendar delegation already works there. You do not need to stay in classic Outlook to configure or use calendar delegation. Mail-folder delegation — the ability to send from or manage someone's inbox — still requires classic Outlook as of 2026, but the calendar side works in both clients. If your organisation's guides say to use classic Outlook for all delegation, the calendar portion of those instructions is outdated.

The three permission levels: Reviewer, Author, and Editor#

Outlook names three permission levels for calendar delegates. Each grants a different combination of read, write, and delete access, and choosing the wrong one is the most common setup mistake.

Reviewer is read-only. A Reviewer can see all calendar items except private ones. They cannot create meetings or modify anything on the calendar. This level suits an assistant who needs visibility to help coordinate your time but should not be making changes themselves — for example, a PA who checks your availability before suggesting times to a third party.

Author adds the ability to create. An Author can read all non-private items and create new calendar items on your behalf — meetings, appointments, events. They cannot edit or delete items that the calendar owner created, only items they themselves created as a delegate. This is the right level for an assistant who books new meetings on your behalf but should not be modifying your existing commitments.

Editor is full access. An Editor can read, create, modify, and delete any calendar item, including ones you created yourself. This is appropriate for a chief of staff or executive assistant who genuinely manages the calendar end-to-end and needs to reschedule, cancel, or adjust any appointment without coming back to the owner for authorisation.

How meeting invitations work with a delegate#

Adding a delegate does not automatically redirect your meeting invitations. You configure invitation routing explicitly when you set up the delegate in Outlook's delegate settings. The options are: send invitations to both the calendar owner and the delegate, or send them to the delegate only.

The delegate-only option is what enables the full executive-assistant workflow. The executive sets it once and stops receiving scheduling logistics in their inbox. The assistant handles all meeting requests, accepts or declines on the executive's behalf, and manages the calendar without the executive seeing each invitation.

When a delegate responds to an invitation on the calendar owner's behalf, the formal response — the accept or decline — appears to come from the calendar owner, not the delegate. If the delegate adds a message when responding (to explain a conflict, for instance), that accompanying note is sent from the delegate's address. The distinction matters when organisers are trying to confirm attendance: the RSVP is from the executive, but any explanatory note comes from the assistant.

One edge case worth knowing: if a meeting invitation is sent directly to the delegate rather than to the calendar owner, it lands in the delegate's own calendar, not the owner's. Delegation only works when the invitation is addressed to the calendar owner's address.

What breaks without the right permission level#

Granting too little access is the more common error, and it creates a hidden bottleneck. An assistant given Reviewer access who needs to reschedule a meeting has no way to do so inside Outlook — they must ask the calendar owner to make the change, which means the owner is back in the scheduling loop they were trying to leave. An assistant given Author access runs into the same wall when they need to modify a recurring meeting the owner originally created: Author delegates can only edit items they themselves created.

Granting too much access carries the reverse risk. An Editor can delete any item on the calendar, including ones the owner created, and Outlook does not prompt for confirmation. Starting a new assistant at Reviewer or Author access with a deliberate upgrade to Editor once the working relationship is established is a reasonable approach to managing that risk.

Private appointments deserve their own mention. By default, a delegate at any permission level sees private items only as 'Private Appointment' — no subject, no attendees, no location. This is correct behaviour and it is by design. If the assistant needs to see the details of private appointments — because they involve medical appointments that affect scheduling, for example — there is a separate 'delegate can see my private items' checkbox in the Add Delegates dialog. It must be explicitly enabled; it does not follow from the permission level.

Calendar delegation vs calendar sharing: what is the difference?#

Calendar sharing and calendar delegation are often used interchangeably, but they are different features with different capabilities. The core distinction is whether the other person can act on your behalf or only observe your schedule.

Calendar sharing is visibility. You share your calendar with a colleague, and they can see your appointments in their own calendar view. Depending on the permission you choose, they may see only free/busy blocks, full event details, or be able to edit items. But they cannot accept meeting invitations on your behalf, and meeting requests sent to your address do not route to them.

Calendar delegation is action authorisation. A delegate can do things in your name: accept meetings, decline, create events, and — with Editor access — modify or cancel any appointment. Meeting invitations can be routed to the delegate. The delegate acts as a proxy, not just an observer.

Common misconceptions about Outlook calendar delegation#

Several assumptions about Outlook calendar delegation turn out to be wrong in practice.

First: delegates can see private appointments. They cannot by default. Private items appear only as 'Private Appointment' regardless of permission level. The delegate sees that a slot is blocked but none of the details. The exception is when the calendar owner has explicitly enabled the 'delegate can see my private items' option in the Add Delegates settings.

Second: Author permission means the assistant can edit any meeting. Author-level delegates can create new items, but they can only edit or delete items they themselves created as a delegate. To modify an appointment the calendar owner created, Editor access is required.

Third: adding a delegate automatically redirects meeting invitations. Meeting invitation routing is a separate configuration step. Adding someone as a delegate with any permission level does not automatically redirect your meeting invites. You must choose the routing option — send to delegate only, or send to both — at the time of setup.

Fourth: calendar delegation requires classic Outlook. For calendar specifically, this has not been true since new Outlook introduced calendar delegation support. The confusion comes from the fact that mail-folder delegation — managing someone's inbox, sending on their behalf — still requires classic Outlook. Calendar and mail delegation are configured separately, and calendar works in both clients.

How AI Emaily fits alongside calendar delegation#

Calendar delegation solves access at the Outlook layer — it defines who can act on your calendar inside Microsoft's interface. The adjacent problem is inbox volume: the executive whose assistant manages the calendar typically also has an inbox producing dozens of threads a day, many tied to the same meetings the delegate is handling on the calendar side.

We build AI Emaily, an AI-native email client designed for exactly that inbox problem. AI Emaily connects to your existing Outlook account and handles the email layer alongside the calendar delegation you already have configured: triaging incoming mail, drafting replies in your voice from a user-set Personal Context brain and client profiles, and surfacing the threads that require your attention rather than routing them to the delegate. The two layers are complementary — Outlook delegation is the right tool for calendar access control; an AI email client is the right tool for the inbox load that surrounds it. If you want to see how AI Emaily handles the inbox side of the delegation workflow, you can start a 7-day free trial at [aiemaily.com](/pricing) — no permanent free tier, card required, cancel before day 7 and you pay nothing.