Skip to content
LitePassword
Sign in Get started — free
← All use cases
FOR PEOPLE SHARING LOGINS WITH VIRTUAL ASSISTANTS

How to share login credentials with a virtual assistant (safely)

Virtual assistants need real access to real tools — your inbox, your scheduler, your social. LitePassword gives them view-only access to exactly what they need, nothing more, and revokes in one click.

Start free — under 60 seconds See Family pricing
YOU PROBABLY DEAL WITH
  • · You text the VA your Gmail password and hope for the best
  • · They need to schedule meetings but you do not want them to see your Stripe dashboard
  • · You change VAs every 4-6 months and re-share everything from scratch
  • · You have no idea what credentials your last VA still has saved in their browser
  • · The VA works from another country and your team uses a tool that does not work there
CREDENTIALS YOU'LL ACTUALLY STORE
  • Gmail / Google Workspace inbox access
  • Calendly / SavvyCal scheduling links
  • Stripe dashboard view-only role
  • Notion / Linear / ClickUp project access
  • Instagram / X / LinkedIn social accounts
  • Canva, Adobe Express for graphics
  • Slack workspace for client comms

How to share login credentials with virtual assistant

That's exactly the size LitePassword is shaped around. Same zero-knowledge encryption, same three roles, but priced for people sharing logins with virtual assistants — not enterprise. The Family plan covers you, and you can start on Free today.

Try free →

Why “just text it to your VA” stops being safe fast

A virtual assistant needs real access to your tools — inbox, scheduler, social, project management. Texting them passwords works for the first week. By month three you’ve sent eight credentials across iMessage, three across WhatsApp, and you’ve forgotten which ones you’ve already rotated.

When the engagement ends (VAs typically rotate every 4-12 months), you have no clean way to know what they still have. Their browser still has saved logins. Their notes app still has the screenshot. Your iMessage history has the value in plaintext.

This is the exact problem zero-knowledge vault sharing solves.

The clean setup

  1. Create a “VA access” shared vault. Or one vault per role if you have multiple VAs.
  2. Add only the credentials they actually need. Calendly, Instagram, your Notion project — not your AWS root or banking logins.
  3. Invite the VA as View only with per-vault access only to that vault.
  4. They sign up, set their master password, save a recovery key.
  5. They get to work — they open the vault when they need a credential, use the one-click copy, and never see anything outside that vault.

When the engagement ends, you revoke their account in one click. The vault key rotates. Their cached ciphertext (if any) becomes undecryptable. The credentials still need to be rotated on the underlying tools (Calendly password reset, Instagram password reset) — but the leakage path through the VA’s device is closed.

Don’t share account-level credentials when you don’t have to

A common mistake: handing the VA your Google Workspace login because they need to send email. Don’t. Use Google’s official email delegation — they can send-as you without the password. Use LitePassword only for credentials that don’t have a delegation mode (scheduling, social, project management).

Don’t share one account between multiple VAs

If you rotate VAs, give each their own LitePassword account with View-only access. Sharing one account means you have no audit (who did what?), no clean revoke (changing one master password locks everyone out), and no recovery story (whose recovery key is that?).

The Family plan covers 5 users for $5/mo. Two VAs across two engagement cycles fit comfortably.

What this costs vs the alternative

  • Sharing via iMessage: $0 / month, ~30 minutes of cleanup risk per VA rotation, ongoing exposure.
  • LitePassword Family: $5/month total. One-click revoke. Zero-knowledge encryption.

For the full pattern (with screenshots), see How to share login credentials with a virtual assistant.

FAQ

Common questions from people sharing logins with virtual assistants

Is it safe to share passwords with a virtual assistant?

It is safe if you do it through a zero-knowledge vault with View-only role and per-vault access. The VA gets the credentials they need, you can revoke in one click when the engagement ends, and the underlying secrets are encrypted on the VA's device so a breach of their machine after revoke does not expose anything.

How do I give a VA access without showing them everything?

Invite them as View only. Open Manage Vault Access on their row. Toggle on only the vaults they need. They cannot see vault names or contents for vaults they were not granted.

What happens when I end the engagement?

Users page → Revoke Access. Their account is removed and every vault they had access to rotates its encryption key. Cached copies on their device become undecryptable. Do this the same day the engagement ends.

Should I use a service-account email for the VA or invite their personal email?

Invite their personal email — that is how the recovery key model works (one user, one master password, one recovery key). If you really want a separate identity for the VA-role, set up a forwarding email for them and use that. Avoid sharing accounts; it defeats per-user auditing.

My VA needs to send emails as me — can they without seeing my Gmail password?

If you use Gmail/Google Workspace, set them up as a delegated account through Google's official delegate feature instead of sharing your password. Use LitePassword for the credentials Google's delegation doesn't cover (scheduling tools, social, etc.).

My VA is in the Philippines / India / Europe. Will LitePassword work for them?

Yes. It is a web app that runs in any modern browser. No regional restrictions, no native-app install required. Their master password derives the encryption key locally on their device.

Stop sharing passwords in Slack messages.

Create your account in under a minute. Pick a master password. We'll generate your recovery key for you.