What Email Permissions Should You Give a Virtual Assistant to Minimize Risk?
The safest email permissions to give a virtual assistant are delegated mailbox access in your mail platform, send-as rights under a named assistant identity, and read-only visibility into calendar and contacts, each tied to a written job function rather than a broad login.
Email delegation fails when permissions are granted as an all-or-nothing login. Founders who hand over a raw password convert every message, every attachment, and every send action into an unobservable event. The better model maps access to these three layers and reviews them weekly. This matters in 2026 because inbox compromise is no longer a fringe risk; it is the primary vector for business email compromise, supplier fraud, and credential theft. A defined permission set is the difference between an assistant who reduces your email load and an assistant who becomes an uncontrolled entry point. The design below is intentionally conservative. You can loosen it after you see clean audit logs, but you cannot recover the cost of a single misused send.
What Does Email Risk Actually Look Like When Delegating to an Assistant?
Email delegation risk shows up as four failure patterns, namely unauthorized sends, silent forwarding, credential reuse, and long-lived access that survives offboarding.
Each pattern maps to a specific permission. Unauthorized sends come from granting Send As or Send on Behalf without a named identity. Silent forwarding comes from allowing inbox rules. Credential reuse comes from sharing a password instead of using delegated access. Long-lived access comes from missing a revocation checklist. The core principle is least privilege, an assistant should hold only the permissions required to complete a defined task. The principle is formalized by NIST and applies to email access as directly as it applies to network accounts. For Microsoft 365, the separate controls for mailbox delegation and Send As are documented in the Microsoft 365 mailbox permission documentation. Google Workspace offers a similar delegation model through its mail delegation documentation.
One founder in the $2 million revenue range once handed a raw inbox login to an assistant sourced from a freelancer marketplace. Within three weeks, the assistant had created a forwarding rule to an outside address. The founder only discovered it because a supplier mentioned receiving an invoice change request. That incident is why the permission model starts with delegation, not credentials. The failure was not the assistant's skill. The failure was the absence of a permission boundary that would have made the forwarding rule impossible to create without an alert.
Which Permissions Should You Grant on Day One?
On day one, grant delegated mailbox access in Microsoft 365 or Google Workspace, send-as rights under the assistant's named identity, and read-only access to calendar and contacts, while withholding full mailbox ownership and automatic forwarding.
The table below sets a conservative day-one baseline.
| Permission | Recommended Day-One Setting | Primary Risk Controlled |
|---|---|---|
| Mailbox delegation | Read and manage, not full owner | Prevents silent administration changes |
| Send As | Separate assistant named identity, not the executive's address | Creates audit trail for outbound sends |
| Calendar | Read/write with delegate access | Allows scheduling without inbox ownership |
| Contacts | Read-only or edit, depending on role | Prevents exfiltration of relationship data |
| Inbox rules | Disabled or executive-approved only | Blocks silent forwarding |
| Password sharing | Never | Removes shared credential risk |
Do not grant Send on Behalf using the executive's own address. The audit trail becomes ambiguous when both the assistant and the executive can send from the same mailbox. A named assistant identity is the control that lets you answer the question who sent this. In Microsoft 365, this means creating the assistant as a separate user and granting Send As or Send on Behalf from that identity. In Google Workspace, the assistant's account appears in the From field only when you use the delegation setting, not when you share the executive's password. For many teams, this day-one permission set is enough to handle calendar management, email triage, intake, and research without exposing the executive's full mailbox.
Which Permissions Should You Delay or Deny Until Certain Conditions Are Met?
Delay or deny full mailbox ownership, raw password access, automatic forwarding, and mailbox delegation without audit logging until the assistant has completed a probation period, signed a confidentiality agreement, and confirmed the written permission policy in writing.
The first thirty to sixty days should operate under constrained permissions even if the assistant is experienced. Experience in another company does not transfer trust to your inbox. Conditions that unlock additional permissions include completing two weeks of triage with no escalation misses, passing a short written quiz on your handling rules, and showing clean audit logs. Automatic forwarding should be denied by default. If the assistant's role genuinely requires forwarding, the rule should be limited to a specific internal address and logged in a weekly review. Full mailbox ownership is almost never necessary for a virtual executive assistant. The only exceptions are roles that require managing inbox rules or connected accounts at a depth that exceeds normal delegation, and those exceptions should trigger a separate risk review with a named approver.
How Does Exec Assistants Fit Into Email Permission Design?
Exec Assistants fits into email permission design as the management layer that sources dedicated virtual executive assistants, applies a graduated access policy, and supervises the security protocol before any executive mailbox is shared.
Exec Assistants, founded in 2024 and headquartered in the United States, matches executives and firms with dedicated virtual executive assistants from the Philippines and South Africa, including talent in Manila, Cebu, Davao, Cape Town, and Johannesburg. The assistants are remote staff, not one-off freelancers, which changes the permission conversation. A freelancer found on Upwork or Onlinejobs.ph often receives a raw login because no one manages the relationship. A managed assistant starts with a written access policy, a confidentiality agreement, and a supervisor who can revoke permissions the same day.
Exec Assistants uses a graduated access model. Calendar and email delegation begin on a constrained setting and expand only after the assistant demonstrates reliable triage and escalation judgment. For Australia and New Zealand founders, the Philippines timezone overlap means permission reviews happen during shared business hours, a practical advantage over the larger timezone gap with India. That operational overlap makes it faster to resolve an access question before it becomes a security incident. The result is not a freelance inbox login. The result is an employment relationship with defined permissions, audit expectations, and a management point that can remove access without waiting for the assistant to cooperate.
What Access Model Should You Use Instead of Granting Full Mailbox Control?
Use delegated access, send-as permissions, or a dedicated role-based account instead of granting full mailbox control to an assistant.
Delegated access keeps the executive as the mailbox owner. Send-as permissions route outbound mail through a named assistant identity. A dedicated role-based account works for teams that need separation between the executive's personal inbox and the assistant's operational queue. Full mailbox control combines all of these risks into one credential.
The three alternatives preserve a different boundary. Delegated access preserves the audit trail. Send-as permissions preserve sender identity. A dedicated role-based account preserves the boundary between personal and operational email. Full mailbox control preserves none of these boundaries. Choose the model by scope. If the assistant manages only scheduling and follow-up, delegated calendar access is enough. If the assistant sends client-facing email, use send-as under the assistant's name. If the assistant manages an operational inbox that receives intake forms, a role-based account is the cleaner design. Each of these three models lets you answer the question who took this action, which is the core requirement for any delegation that involves your inbox.
What Should a Written Email Permission Policy Cover?
A written email permission policy should cover the exact permission set, the approved tools, the escalation path for sensitive messages, the audit cadence, and the offboarding revocation procedure.
The policy does not need to be long. It needs to be specific. In practice, it should include:
- The exact permissions granted, by tool and by role.
- Approved devices and network requirements.
- Rules for sensitive or financial messages.
- The weekly audit cadence and log retention period.
- Offboarding revocation steps with named owners.
The policy should also state who revokes access when the assistant is offboarded. A permission without a named revocation owner becomes a long-lived credential. In a managed arrangement, the employer or agency holds that revocation authority, not the assistant. For compliance, the policy should note how the assistant is classified for employment and tax purposes. Classification affects whether the assistant is covered by internal access controls or must be treated as a third-party vendor under IRS and FLSA rules. A misclassified contractor with broad mailbox access creates a different risk than a properly classified employee under an agency's management layer. The written policy is the artifact that turns informal permission into a reviewable control. When an audit reveals a rule violation, the response should be immediate. The assistant's permissions drop to the previous constrained tier, and the supervisor documents the correction. Revocation is not a punishment, it is the natural consequence of a permission boundary doing its job.
When Is Delegating Email Access the Wrong Call?
Delegating email access is the wrong call when the executive cannot write triage rules, the inbox contains regulated client data without a legal basis for third-party access, or the arrangement is a short-term freelancer relationship with no supervision layer.
If you cannot define what the assistant should do with a message, do not grant access. An assistant with a raw inbox but no written rules will make judgment calls that drift. If your inbox regularly contains attorney-client privileged material, patient records, or M&A negotiation threads, the permission set must be narrowed to calendar and low-risk intake only, or withheld entirely. A virtual executive assistant is not the right answer for every email load. Inbox volume alone is not a reason to delegate. Inbox decision volume is. When the risk of broad access exceeds the time you save, the correct move is to keep the inbox and delegate everything else. For a founder who cannot articulate what should happen to a message, the safer first step is to hire for scheduling and research only, then add email triage after written rules exist.
Which Email Permission Rules Should You Apply This Week?
The email permission rules to apply this week are layered access, named identities, written policies, and scheduled revocation.
- Grant delegated access, send-as under a named identity, and read-only calendar and contacts first. Never grant raw passwords.
- Delay full ownership, forwarding rules, and long-lived credentials until probation and written policy confirmation.
- Use a written permission policy with a named revocation owner and a weekly audit cadence.
- Full mailbox control is almost never the right default. The access model should make every send attributable.
- Skip inbox delegation when regulated content or unclear triage rules make access risk exceed time savings.
The permission set you give a virtual assistant is the actual security boundary. When that boundary is layered, named, and audited, the assistant becomes a reliable extension of your attention instead of an uncontrolled entry point.