Connect your accounts

Three connections power the framework. Start with Gmail — the other two can wait, and nothing breaks if they do.

Each consent screen you see comes from the provider, not from us — and it will name exactly the access its card describes here. If a screen ever asks for more than the card says, stop and tell us.

Gmail

Start here

Powers the first win: your inbox, triaged.

What we connect: Your inbox, for triage — so ops noise stops reaching you.
Access requested: One scope: gmail.metadata — sender, subject, labels, and thread structure.
What we can never see: Message bodies and attachments. The access we request cannot return them — Google's consent screen will say the same.
Where the token lives: In a connector inside your own cloud project. Our database has no column that could hold it.

Connect Gmail

Wealthbox

Connect now or later

Households, tasks, and workflows, ready for prep.

What we connect: Your firm's operational records — households, tasks, workflows.
Access requested: Firm-operational objects only.
What we can never see: Anything outside firm operations — and no connector in any tier can trade, move money, or delete records. That capability does not exist.
Where the token lives: In a connector inside your own cloud project. Our database has no column that could hold it.

Connect Wealthbox

Calendly

Connect now or later

Meeting prep that starts before you ask.

What we connect: Your schedule — event types and availability.
Access requested: Firm-operational objects only: scheduling.
What we can never see: Anything outside scheduling — and no connector in any tier can trade, move money, or delete records. That capability does not exist.
Where the token lives: In a connector inside your own cloud project. Our database has no column that could hold it.

Connect Calendly