Connectors: bring your scattered data in, read-only first

A connector is a link from one of your own accounts, such as email, a calendar or a shared drive, into the server. It lets the server read from them, so one assistant can use all of your data.

Book facts dated . From The MeshVault Book, Edition 3, page 025. All guides

Three habits keep connectors under control

  1. Read-only first. A read-only connector can look at data but cannot change it. We add write access only when a job needs it.

  2. Smallest access. If a connector asks for more than the job needs, we say no.

  3. Every connector can be revoked. Revoke means you switch off its access. Try it once, so you know it works.

A company sits in the middle

Connectors usually go through an integration service run by a third party, and you link your own account to it. That company is not MeshVault and not you. Ask which one it is, and what it can see.

Our integrations page lets you browse the app catalog. A listing there is not a connection to your account.

What read-only does, and where it stops

Connectors begin read-only.
LimitWrite access is added only when a job needs it, and only for that job.
A read-only connector cannot change your data.
LimitIt still reaches outside by its nature. An email connector talks to your email provider.

Page 024 of the book lists what can leave a local setup. Our what can leave your server page carries the same list.

One approved job at a time

We add a connector for a job you chose, test it, and only then add the next.

A new connector is an access change. Access changes always wait for a named person to say yes. If nobody answers, the change is held. Read how approvals work.

Where connectors stand today

Connectors are planned as the second step, after the server is proven. We do not say a connector is ready until we have tested it on your setup.

Questions to ask before any connector

  • Which integration service does it go through, and what can that company see?
  • Is it read-only? If not, which job needs write access?
  • Does it ask for more access than the job needs?
  • Can I revoke it, and can we try that once now?
  • What did you try to make it do that it should refuse?

Sources

  1. MeshVault, The MeshVault Book, Edition 3, 2026-09-29, page 025 (connectors), with pages 024, 026 and 030 for what can leave, access changes and status. Source line printed in the book: MeshVault owner decisions, 2026-09-28/29; agreement draft, sec 12.6; binder p194.

What to do next

The server comes first. Connectors come second, one approved job at a time. Ask about them on your first call, where nobody is asked to sign anything.

The one-week install costs $1,500 as of . Requote before use. It may not cover hardware, taxes or any work after the week. Ask for the quote in writing (book page 035).

Plan my one-week install Next guide: approvals, why a named person says yes