The seven tool categories a remote executive assistant needs, and how to give access without sharing a single password. Setup takes one to three days.
A remote executive assistant needs access to seven tool categories: communication, calendar, project management, document collaboration, financial administration, travel, and AI. Which platforms you use matters far less than the access level the assistant gets: the common failure is not the wrong tool but an assistant given view-only access to a calendar they are meant to be defending. Granting logins takes one to three days; the documented rules that make them usable take two to four weeks. DonnaPro sets access levels per tool during onboarding, before the assistant starts work.
The technology a founder uses every day is also the technology their executive assistant needs to use every day. That sounds obvious, but it is where most remote EA relationships stall.
The founder signs up for a project management tool, a calendar system, a shared drive, and a messaging platform. They give the EA a login to one or two of them. The EA ends up chasing information across channels they cannot see, requesting files they do not have permission to open, and waiting for approvals they could have handled themselves. The result is an assistant who looks reactive when the real problem is restricted access.
Harvard Business Review research by Cross, Arena, Pryor, Hinds and Bowman found that time spent on the collaborative aspects of work has grown by roughly 50% over the past twelve years (Cross et al., “How to Fix Collaboration Overload,” Harvard Business Review, 2022 (opens in a new tab)). Buffer’s State of Remote Work report, surveying 3,000 remote workers globally, found that 78% of companies now have dedicated systems and technology for remote team collaboration (Buffer, State of Remote Work, 2023 (opens in a new tab)). The tools exist. The question is whether the EA has enough access to use them properly.
This guide covers the seven tool categories that make a remote EA relationship work, what each category needs to do, and how to set them up so the EA operates as a partner rather than a bottleneck. It is the practical companion to the CEO delegation playbook.
What this category covers: real-time messaging, email, and video calls.
The EA needs to be inside the founder’s primary communication channels, not alongside them. That means shared access to the inbox (with permissions to draft, send and archive on the founder’s behalf), a seat on the messaging platform the team uses, and the ability to join or schedule video calls.
Most communication tools now support delegated access. Email platforms allow shared mailbox access or send-on-behalf permissions. Messaging tools like Slack, Microsoft Teams or Google Chat let the EA sit in the same channels the founder uses, which means they see the same context and can act on requests without waiting for a forwarded message.
What to set up from day one: inbox delegation with send-on-behalf permissions, a shared messaging workspace with access to the relevant channels, and calendar integration so the EA can schedule calls directly. The EA should also have access to the founder’s contact list or CRM so they can identify who is writing and prioritise accordingly. This is the foundation for inbox, calendar and travel management.
The goal is for the EA to manage the communication flow, not monitor it from the outside.
What this category covers: diary management, meeting scheduling, and time blocking.
Calendar access is usually the first thing a founder grants, but partial access creates problems. An EA who can view the calendar but not edit it will send a request every time something needs to move. An EA with full edit access handles scheduling, rescheduling, buffer time and travel windows without the founder being involved at all.
Scheduling tools that allow external guests to book directly into the founder’s calendar (such as Calendly, SavvyCal, or the native scheduling features in Google and Microsoft) are particularly useful. The EA manages the availability rules, the booking link handles the coordination, and the founder’s diary stays defended without manual effort.
What to set up from day one: full read-write access to the founder’s calendar, a scheduling tool the EA controls, and agreed rules on meeting length, buffer time, and protected blocks. Document these rules in a short SOP so the EA can enforce them consistently without checking every decision. Our guide on how to build SOPs to delegate covers the format.
What this category covers: tracking work, managing deadlines, and coordinating across people.
A shared task management system is what stops an EA relationship from becoming a string of messages that starts with “Can you also…” and ends with something forgotten. The EA needs a tool where tasks are visible, assigned, and tracked, and where the founder can see progress without asking for an update.
The specific platform matters less than the structure. Whether the team uses Asana, Monday, Notion, Trello, ClickUp or a simple shared spreadsheet, the EA needs full access to create tasks, assign deadlines, update statuses, and close completed items. If the founder is the only person who can create or assign work, the tool becomes a read-only list rather than an operating system.
What to set up from day one: a shared workspace where both the founder and the EA can create, assign and update tasks. Agree on a weekly review cadence so nothing drifts. The EA should own the system, meaning they maintain it, chase overdue items, and flag blockers rather than waiting for the founder to check in. This is standard practice for a virtual executive assistant working at a senior level.
One of the most common patterns our EAs describe is this: the founder starts a project management tool with good intentions, uses it for two weeks, and then reverts to sending instructions by message. The EA’s job is to pull those instructions back into the system, because that is what keeps the work visible and accountable.
What this category covers: shared drives, document editing, and version control.
The EA will spend a significant portion of their time working inside documents: drafting briefing packs, updating trackers, assembling reports, and organising files. They need access to the shared drive, not a separate folder where files are copied across.
Cloud-based document tools (Google Workspace, Microsoft 365, Dropbox, or similar) allow real-time collaboration without version conflicts. The EA works inside the same document the founder will review, which removes the cycle of drafting, emailing, editing, and re-emailing that adds days to simple tasks.
What to set up from day one: shared drive access with edit permissions, a clear folder structure the EA can maintain, and naming conventions so files are findable without asking. If the founder’s business generates contracts, proposals, or other recurring documents, the EA should have access to the templates and the authority to draft from them.
The document system is also where SOPs live. Every process the EA manages, from inbox triage rules to travel booking preferences, should be documented in the shared drive so it survives personnel changes and remains consistent over time.
What this category covers: invoicing, expense tracking, receipt management, and payment follow-ups.
An EA handling financial administration needs access to the accounting or invoicing platform the business uses. This does not mean the EA is doing the bookkeeping. It means they are managing the operational layer: chasing outstanding invoices, reconciling expenses, preparing summaries for the accountant, and ensuring nothing falls through the gap between “sent” and “paid”. It is one of the clearest examples of what an executive assistant actually does beyond calendar work.
Tools in this category include accounting platforms like Xero, QuickBooks or FreeAgent, expense tools like Pleo, Spendesk or Expensify, and simple invoice trackers. The EA needs enough access to see what is outstanding, send reminders, and prepare reports, but not necessarily the access to authorise payments or submit tax filings. Those boundaries are functional, not about trust; they reflect where operational work ends and regulated work begins.
What to set up from day one: read access to the invoicing or accounting platform (with send or chase permissions if the tool supports them), a shared expense tracker, and an agreed process for receipt capture and categorisation. The EA should know the accountant’s deadlines and the documents they need, because that handoff is where most financial administration delays occur.
What this category covers: flight and hotel bookings, itineraries, visa and insurance coordination, and ground transport.
Travel management for a busy founder involves research, comparison, booking, rebooking, and post-trip admin. The EA needs access to the booking platforms the founder prefers (or the authority to choose), any corporate travel tools in use, and the founder’s loyalty programme details.
What to set up from day one: the founder’s travel preferences documented (airline, seat preference, hotel chain, meal requirements), access to the booking platform or travel management tool, login details for loyalty and rewards programmes, and a shared itinerary template the EA populates for every trip. Most of the time savings come from having these preferences written down once rather than discussed every time a trip is booked.
What this category covers: drafting, research, summarisation, data extraction, and workflow automation.
AI tools have become part of the working EA’s daily stack, which is why we train for it directly: see AI-trained executive assistant. They do not replace the EA’s judgement, but they compress the time between a question and a usable answer. An EA who would have spent two hours researching a market comparison can produce a structured first draft in twenty minutes, review it for accuracy, and deliver a finished version faster than most founders could have briefed the task.
The most common use cases are drafting and editing written content, summarising long documents or email threads, extracting structured data from unstructured sources (receipts, contracts, PDFs), building templates and standard operating procedures, and automating repetitive formatting tasks. Tools in this category include general AI assistants (ChatGPT, Claude, Gemini), integrated AI features within platforms the EA already uses (Microsoft Copilot in 365, Gemini in Google Workspace), and specialist tools for transcription, image generation, or data processing. Our comparison of the best AI note takers covers the transcription layer in detail.
What to set up from day one: agree which AI tools the EA is authorised to use (our guide to AI tools for founders is a reasonable starting list) and establish clear rules on what information may be entered. Sensitive financial data, client details, and confidential documents may need to stay out of third-party AI tools, or the EA may need to use a business account with data protections enabled. The EA should also document which recurring tasks they are using AI to accelerate, so the founder has visibility into where the time savings are coming from.
The EA’s value is not in typing. It is in knowing what to produce, for whom, and to what standard. AI handles the production. The EA handles the decisions around it, which is also the line that defines what you cannot delegate to a virtual assistant.
The question that comes up most often on DonnaPro sales calls is not about tools or pricing. It is about access. One CEO of a 100-person company said mid-call, “I did not know you could do that.” The concern is always the same: how does an EA get into my systems without me handing over every password?
The answer is delegation, not password sharing. Modern platforms are built for this.
Google Workspace allows the founder to grant domain-wide delegation to the EA’s account. The EA accesses the founder’s Gmail, Calendar, and Drive through their own login, with permissions set by the administrator. The founder never shares a password. The administrator controls exactly what the EA can see and do, and can revoke access from a single admin panel in under a minute.
Microsoft 365 works similarly through its delegate access model. The founder grants mailbox delegation, shared calendar access, and SharePoint or OneDrive permissions through the Microsoft 365 admin centre. The EA logs in with their own credentials and operates within the founder’s environment without ever seeing the founder’s password.
WhatsApp is trickier because the standard app ties to a personal phone number. The solution is WhatsApp Business, which allows the EA to manage messages from the same number through a linked device or the web interface. The founder keeps their personal WhatsApp separate, the EA handles business messages, and both can operate simultaneously.
Financial tools and cards do not require the EA to hold the founder’s bank login. Expense platforms like Pleo, Spendesk, and Revolut Business allow the administrator to issue a virtual or physical card to the EA with a preset spending limit. The EA can make purchases within that limit, every transaction is logged, and the founder can freeze or revoke the card instantly.
Everything else goes through a password manager. Tools like 1Password, LastPass, or Bitwarden allow the founder to share credentials with the EA through an encrypted vault. The EA accesses the login without seeing the actual password. If the relationship ends, the founder removes the EA from the vault and every shared credential is revoked in one step.
The pattern across every platform is the same: the EA operates under their own identity, the founder controls what they can reach, and revoking access is a single action rather than a scramble to change twenty passwords.
Every tool category above follows the same logic: the EA needs access, permissions, and documented context. Without all three, the tool becomes a source of friction rather than a solution.
A founder who grants partial access to save time ends up spending more time answering questions and approving actions the EA could have handled alone. Full access, within documented boundaries, is what makes a remote EA operate like someone sitting in the same office.
A managed executive assistant at €2,700 per month includes the onboarding work most founders never get around to: mapping the full tech stack, establishing the right access levels for each tool, building the SOPs that make those tools operational from week one, and configuring delegated access so nothing depends on a shared password. You can see the full scope on our executive assistant services page, or compare plans on the pricing page.
Book an Introductory CallThis guide draws on published research into workplace collaboration and remote work patterns, and on practical experience from DonnaPro’s executive assistants supporting founders across multiple industries and tech environments. The tool categories and setup recommendations reflect real onboarding processes and ongoing engagements.
Sources reviewed:
Checked for accuracy against how DonnaPro actually works before publication.
Explore more guides to help you hire, work with, and get the most from your executive assistant.
