Home  →  Guides

Virtual Assistant Security and NDA Guide: How to Give a VA Access Without Losing Sleep

The question I hear most often from founders who are about to hire their first virtual assistant is not about price or time zones. It is some version of "how do I give a stranger access to my inbox, my clients and my systems without it going wrong?"

It is a fair question. A good VA ends up touching almost everything: email, calendar, CRM, shared drives, sometimes invoicing and customer records. That is what makes them useful. It is also what makes a careless setup risky.

I run Virtual Assistant Capital, and setting up access for new placements is part of almost every first week we see. The honest answer is that VA security is rarely about the person being malicious. It is far more often about access that was handed over too broadly, shared in the wrong way, and never taken back. Most of that is fixable in an afternoon, with free or low-cost tools you probably already pay for.

This guide covers what an NDA does and does not protect, what to put in a confidentiality agreement, how to share access properly, how to handle client data and AI tools, how to offboard cleanly, and what to watch for in regulated industries. It is practical guidance from an operator, not legal advice. For the agreement itself, have a lawyer in your country review it, especially if you handle health, financial or legal information.

The real risks, in plain terms

Before tools and contracts, it helps to be clear about what you are actually protecting against. In my experience the realistic risks, in rough order of how often they cause trouble, are:

1. Accidental exposure. A file shared with "anyone with the link", a client email forwarded to the wrong address, a spreadsheet of customer details downloaded to a personal laptop. No bad intent, real consequences.
2. Account compromise. The VA's own email or device gets phished, and whoever gets in now has whatever access the VA had. This is why the access you grant matters more than the person you grant it to.
3. Lingering access. The VA leaves, or the engagement changes, and nobody removes their logins. Months later, an old account is still connected to your CRM and your bank feed.
4. Misuse of information. Much rarer, but the one everyone worries about: someone using your client list, pricing or ideas for their own benefit.

An NDA mainly helps with the fourth. Good access hygiene handles the first three, and it limits the damage of the fourth. That is why this guide spends more time on access than on contracts.

What an NDA actually does

A non-disclosure agreement (or a confidentiality clause inside a wider services agreement) does three useful things:

• It sets expectations in writing. The VA knows, on day one, that client data, pricing, financials and internal documents are confidential, and what "confidential" means in your business.
• It gives you a remedy. If information is misused, you have a document that says what was agreed. How useful that is in practice depends on the jurisdiction, the wording and the cost of enforcing it.
• It filters. A professional VA signs a reasonable NDA without fuss. Someone who pushes back on basic confidentiality is telling you something.

What an NDA does not do is prevent anything. It does not stop a phishing email, a misconfigured sharing link or a forgotten login. Treat it as one layer, not the plan.

What to put in a VA confidentiality agreement

You do not need a twenty-page document. A clear, short agreement that the VA actually reads is better. The clauses worth having, in plain terms:

Definition of confidential information. Be specific: client and customer details, pricing, contracts, financial information, login credentials, internal processes and documents, and anything marked or reasonably understood as confidential. Vague definitions are hard to rely on later.

Permitted use. Information may be used only to do the work for you. Not for other clients, not for personal projects, not for "examples" in a portfolio unless you say so in writing.

Data handling rules. Where files can be stored (your shared drive, not a personal one), which devices can be used, no downloading customer data to personal storage, and no forwarding work email to personal accounts.

AI and third-party tools. Which AI tools are approved, and what must never be pasted into any AI tool or outside service. More on this below, because it is the clause most agreements are still missing.

Return and deletion. At the end of the engagement, the VA returns or deletes your information and confirms in writing that they have.

Duration. Confidentiality should outlast the engagement. How long is a question for your lawyer and depends on the type of information.

Ownership of work. Documents, SOPs, templates and anything else created for your business belong to your business.

Breach notification. If the VA suspects something has gone wrong, such as a lost device, a suspicious login or a file sent to the wrong person, they tell you immediately. Make it clear that reporting a mistake quickly is the right thing to do and will not get them in trouble. You want mistakes surfaced in an hour, not hidden for a month.

If you hire through an agency, ask what agreements are already in place between the agency and the VA, what they cover, and whether you can add your own. At Virtual Assistant Capital, confidentiality and data-handling rules are agreed with you before any access is given, and if you want your own NDA signed, you simply tell us in your request.

Access design: the part that does the real work

If you only take one idea from this guide, take this one: give the VA their own access, with only the permissions the current work needs, and grow it as the work grows. Everything else is detail.

Their own logins, not yours

Most business tools let you add a user with their own login and a limited role. Google Workspace and Microsoft 365 both support mailbox and calendar delegation, so your VA can manage your inbox from their own account without your password. CRMs, project tools, accounting software and help desks almost all support separate users with restricted roles.

Separate logins give you three things shared passwords never will: permissions you can limit, a record of who did what, and the ability to remove one person without changing everything.

If a tool genuinely only supports one login, share it through a password manager rather than by message, and change that password when the engagement ends.

A password manager, always

Never send a password over email, chat or text. Use a business password manager with sharing. Most let you share individual logins or folders, and many let you share access without the VA ever seeing the password itself. When the engagement ends, you revoke the share in one place.

Two-factor authentication on everything

Turn on two-factor authentication for every account the VA uses, including their own email if it is a work account you control. The US Cybersecurity and Infrastructure Security Agency describes multi-factor authentication as one of the simplest steps for protecting accounts, and its guidance on MFA is a clear, free primer if you want the background.

Agree in advance how codes are handled. A VA texting you at 6 a.m. for a code is annoying for both of you and teaches everyone to approve prompts without thinking. App-based authenticators, or codes stored in the password manager for shared accounts, are cleaner.

Least privilege, grown in stages

Start with the access the first few tasks need and nothing more. A typical first stage is email or delegated email, calendar, a task manager, one shared drive folder, the password manager and perhaps the CRM. If you are not sure which tasks come first, our delegation playbook gives you a starting list.

Things that can usually wait, or stay behind your approval permanently:

• Bank accounts and payment platforms with the ability to send money.
• Payroll.
• Admin consoles for your domain, email or website.
• Anything with bulk delete, export-all or "transfer ownership" buttons.

For many founders, money movement stays with them for good, and that is fine. A VA can prepare payments, reconcile, chase invoices and draft everything, with the final click staying yours. That is not a statement about trust. It protects you both.

Keep an access register

Keep a simple list: tool, what access was given, the date, and who approved it. It takes two minutes per entry and it turns offboarding from a guessing game into a checklist. It also helps you notice when access has grown well beyond the work.

Devices and networks

You usually do not control a remote VA's laptop, so be realistic about what you can ask for. Reasonable, common expectations are:

• A device used for work that has a supported operating system with updates turned on.
• A screen lock and disk encryption, which are built into current versions of Windows and macOS.
• No shared family logins on the work account of the device.
• No working on public computers.
• Care on public Wi-Fi, especially for anything involving client data.

Where possible, keep data in the cloud tools you control rather than on the device. If files live in your shared drive and email lives in your workspace, a lost laptop is an inconvenience you fix by signing the VA out remotely, not a data incident.

Client data and AI tools

This is the area where I see the most confusion right now, because good VAs use AI tools daily, and they should. The future VA, in my view, is an AI manager: someone who runs AI tools to do the routine work faster and applies human judgment to the exceptions. That is exactly the profile behind our AI Manager plan. But it means you need clear rules about what goes into those tools.

Agree, in writing, three things:

1. Which AI tools are approved. Ideally the business accounts you control, where you can check the data settings, rather than whatever free tool the VA happens to use.
2. What must never be pasted in. Passwords, payment details, government ID numbers, health information, and anything a client has asked you to keep confidential. If in doubt, leave it out or anonymize it first.
3. How output is checked. AI drafts are drafts. Anything client-facing, financial or factual gets a human check before it goes anywhere.

Day-to-day habits that prevent most incidents

Contracts and settings matter, but most problems are prevented by a handful of habits. Agree them during onboarding, the same way you agree working hours. Our guide on how to onboard a virtual assistant covers where these fit in week one.

• Verify payment and bank-detail changes by phone. If a supplier emails to say their bank details have changed, the VA confirms by calling a known number, not the one in the email. This one habit blocks one of the most common business email scams.
• Never act on urgent money requests by email alone, even ones that appear to come from you. Agree a simple rule: payment requests from you always come through one agreed channel.
• Share files with named people, not "anyone with the link".
• Report suspicious emails and logins immediately, and make that a no-blame habit.
• Log out of shared tools on shared or borrowed devices, and never save work passwords in a personal browser profile.

Offboarding: the step everyone forgets

Most lingering-access problems come from engagements that ended quietly. Whether the VA is leaving, being replaced, or simply moving to different work, run the same checklist the same day:

1. Remove or suspend their user accounts in every tool on your access register.
2. Revoke password manager shares, and change any password that was shared directly.
3. Remove email and calendar delegation.
4. Check shared drive sharing on key folders and remove their access.
5. Sign them out of active sessions where your tools allow it.
6. Collect or confirm deletion of any local copies, as your agreement requires.
7. Make sure the SOPs and documents they wrote are in your systems, not theirs.

This is also where documented processes pay off. When the SOPs live in your systems, a replacement can pick up the work without starting from zero. With Virtual Assistant Capital, if the fit is not right within 30 days, we replace your VA at no cost, and because the processes are documented in your systems, the handover is far less painful.

Regulated and sensitive industries

If your business handles health records, legal matters, financial accounts or children's data, the general advice above still applies, but it is not enough on its own. Rules such as HIPAA in the US, GDPR in Europe and the UK, and professional confidentiality rules for lawyers and accountants can place specific obligations on you and on anyone who handles that data for you.

I am not going to tell you what those obligations are for your practice, because that depends on your situation and jurisdiction, and getting it wrong is expensive. What I would suggest is:

• Ask your lawyer or compliance adviser what agreements you need before a VA touches regulated data. In US healthcare, for example, that conversation usually includes whether a business associate agreement is required.
• Start the VA on work that does not involve the regulated data at all, such as scheduling, internal admin or marketing, while that is settled.
• Use the access controls your practice software already has, so the VA sees only what their role needs.

Our industry pages, such as the one for medical practices, describe the kinds of tasks VAs commonly take on in those settings and where the line usually sits. They are not a substitute for compliance advice, and we do not make compliance claims on your behalf.

FAQ

Do virtual assistants sign NDAs? Professional VAs generally sign a reasonable confidentiality agreement without any fuss. If you hire directly, have your own agreement ready before access is shared. With Virtual Assistant Capital, confidentiality and data-handling rules are agreed before any access is given, and if you want your own NDA signed, tell us in your request.

Is an NDA enough to protect my business? No. An NDA sets expectations and gives you a remedy if information is misused, but it prevents nothing. Most real incidents come from broad access, shared passwords, phishing and accounts that were never removed. Separate logins, a password manager, two-factor authentication and a clean offboarding process do most of the protecting.

Should I give my virtual assistant my email password? Ideally not. Google Workspace and Microsoft 365 both support delegation, so the VA can manage your inbox and calendar from their own account. If a tool only supports one login, share it through a password manager and change the password when the engagement ends.

Can my VA handle payments and banking? A VA can prepare payments, reconcile accounts, chase invoices and draft everything, while the final approval to move money stays with you. Many founders keep it that way permanently. It protects you, and it protects the VA from being the target of payment scams.

Can my VA use ChatGPT or other AI tools with my data? They can, and a good one should use AI to work faster, but agree the rules first: which tools are approved, what must never be pasted in (passwords, payment details, ID numbers, health information, confidential client material), and that anything client-facing gets a human check.

What should I do when a VA leaves? Run your offboarding checklist the same day: remove user accounts, revoke password manager shares, change any directly shared passwords, remove delegation and drive access, sign out active sessions, and make sure the SOPs they wrote are in your systems. An access register makes this a fifteen-minute job.

The short version

Most VA security problems are not about bad people. They are about access that was too broad, shared the wrong way and never removed. Sign a short, specific confidentiality agreement that covers data handling and AI tools. Give the VA their own logins with limited roles, use a password manager and two-factor authentication, and keep money movement behind your approval. Agree a few daily habits, keep a list of what you granted, and offboard the same day the work ends.

Do that, and handing over your inbox stops feeling like a leap of faith. If you would like a VA who is used to working this way, see how it works and our pricing: Essentials at $899/month for 20 hours a week, Executive at $1,599/month full-time, and AI Manager at $2,599/month for a full-time, AI-fluent VA. There is no recruitment fee, you get a free shortlist of 2-3 VAs in 72 hours, and you pay only once your VA starts.