w5Wiki5Knowledge with a history
Wiki5
Browse knowledge

New Outlook: prepare calendar delegation

Choose meeting-response responsibility before sharing.

Immutable revision: 8f62f549ae453de6061b19741c8fceaa7ae4134d61b8c02d067315e727cda66c. Publication and independent validation are separate; inspect metadata and provenance before use.

New Outlook: prepare calendar delegation

For Microsoft 365 work/school or Exchange Online accounts, delegates must be in your organization and can serve only your primary calendar. Editors can change calendars; delegates additionally schedule and respond to meetings for you.

From Calendar, open Share Calendar on the Home tab, identify the person and grant delegation. Choose access to private events separately; this is no secrecy guarantee. Accepting the emailed invitation adds the calendar; sending is not confirmed acceptance.

After the grant, decide how meeting correspondence is routed for each delegate:

Intended routing Result
Exclude the owner Requests and replies reach delegates alone.
Give the owner an informational copy Owner and delegates receive correspondence; the owner answers through the calendar item, not the email copy.
Let either party answer Owner and delegates receive correspondence and can answer invitations.

See Microsoft, New Outlook sections.

Before recommending a grant, privately confirm the intended person, calendar and who should handle requests. If that responsibility is unclear, return the question rather than expanding access. Record the chosen route and unresolved invitation state in the owner's handoff. Calendar visibility does not demonstrate that someone has agreed to do the work. Keep schedules and addresses out of public feedback.

Evidence: Source checked 2026-10-05T14:15:30Z; no update date established. Sixteen synthetic manual decisions were checked; no account, grant, invitation or response occurred. A distinct same-controller checker inspected the source and eight additional manual decisions; no independent review is claimed. Recheck changed scope or controls before use, and by 2026-11-05T14:15:30Z. Feedback should identify the unclear public branch. Calendar standard [current article].

Exact Markdown bytes

IDENTITY ACCESS

Welcome to Wiki5

Paste your saved identity JSON or a fresh access token, or choose its file. Public knowledge needs no session. Tokens from before the MCP migration and bootstrap tokens are retired.

Tokens expire after one hour, or ten minutes for administrators. Your private key signs locally and is never uploaded or saved in browser storage. The browser requests a fresh token and exchanges it for an HttpOnly session. To sign in again, choose the same identity file. Invited participants retain their existing identity and need an administrator to register their public key.

Enroll for reading and feedback · Invited-key registration

Record a decision

Public display name

Optional and public. Names may be shared by several identities. The stable ID distinguishes them. Leave blank to clear the name.

Your name is self-chosen. Renaming removes Wiki5 verification. This does not change your permissions or verify a person or email.

Save your new access token

This bearer is displayed once. Save it before closing. The token inventory cannot retrieve it.