The Executive's Guide to Email Delegation Without Sharing Your Password

The delegation problem most executives run into

Sharing your Gmail or Outlook password with an assistant is the worst version of email delegation. It gives unlimited access to everything — personal messages, confidential communications, financial details, threads that have nothing to do with work — and it creates a single credential that is impossible to revoke cleanly.

Google Workspace and Microsoft 365 both offer formal delegation features that are better than password sharing: a delegate can access, respond to, and manage email as you, with proper account separation. For a highly trusted EA managing a full inbox, this is the right tool. But it still grants access to everything — every personal email, every confidential thread, every message in every folder.

The question most executives face is not "how do I give my assistant full inbox access" — it is "how do I give my assistant access to exactly the email that needs their attention, without exposing everything else."

The scoped delegation model

Stackora's forwarding model enables a scoped approach to delegation:

1. Your main inbox remains yours, fully private
2. You create forwarding rules for the email categories an assistant should handle
3. Those categories route to a shared Stackora workspace or forwarding address the assistant monitors
4. The assistant sees only what you routed — not your full inbox

The assistant gets visibility into newsletters requiring response, scheduling requests, vendor communications, and inbox triage tasks without access to board communications, personal email, or confidential HR threads.

Setting it up

Step 1 — Define delegation scope

Before creating any rules, decide explicitly what belongs in the delegated stream. Common categories for executive delegation:

Route to assistant:

• Meeting and scheduling requests from external contacts
• Vendor and service provider communications
• Conference and event invitations
• Newsletter and subscription content requiring response
• Travel confirmations and logistics
• General business inquiries

Keep in personal inbox:

• Board and investor communications
• Confidential HR or legal correspondence
• Personal email (family, friends, medical)
• Direct messages from direct reports
• Anything requiring your personal judgment or authentication

Write the list down. The explicit scoping prevents creep and prevents accidents.

Step 2 — Create forwarding rules for delegated categories

Build filters in Gmail or Outlook for each delegated category:

from:(@vendorname.com OR @travelagency.com OR @conferenceorganizer.com)
subject:(scheduling OR "meeting request" OR "calendar invite")

Forward matching mail to a dedicated Stackora address — either a shared workspace address or a Stackora account your assistant monitors.

Step 3 — Set up the assistant's Stackora account

The assistant gets their own Stackora account (or access to a shared workspace, on plans that support it). They receive a digest of the routed categories — summaries, action items, any scheduling requests — and handle them according to agreed protocols.

For scheduling delegation specifically: the assistant can respond to meeting requests based on a shared calendar view, without needing access to your full inbox to do so.

Step 4 — Establish response protocols

Delegation without protocols creates more work, not less. Define clearly:

• Which categories the assistant responds to independently (travel logistics, vendor scheduling)
• Which categories the assistant flags for your decision (board-adjacent contacts, press inquiries)
• How the assistant escalates anything genuinely urgent (direct message or call, not email back)
• Response SLAs for each category

A one-page protocol document given to the assistant at setup saves multiple confused handoffs later.

The chief of staff variation

For executives with a chief of staff rather than a traditional EA, the delegation often extends beyond email management to operational decisions. The Stackora setup serves a different function here: rather than the CoS managing the inbox directly, they receive a digest of routed categories and use it for briefing prep.

Before a weekly sync with the executive, the CoS reviews the routed digest: what vendor conversations are open, what scheduling requests are outstanding, what announcements arrived. The briefing is grounded in actual inbox content rather than reconstructed from memory.

This use case does not require the CoS to respond to anything — it simply gives them visibility into the email landscape around operational decisions without requiring full inbox access.

What this is not

Email delegation via Stackora routing is not a substitute for the kind of deep inbox management that some executives need from a full-time EA. It is a scoped, privacy-preserving alternative for the cases where:

• You want selective delegation rather than full access
• You do not have a dedicated EA but want to route lower-priority email to a part-time or virtual assistant
• You want to give a CoS visibility without inbox access
• You want to pilot delegation before committing to full Workspace delegation

The trade-off is that delegated staff can only see what you route. Mail you do not forward is invisible to them. For full inbox delegation, Workspace or M365 delegation remains the right tool. For scoped, private, controlled delegation, routing through Stackora is meaningfully better than any credential-sharing alternative.