Log in Start free

a portal per client

One dashboard for every client's bank data.

Invite your clients to connect their own bank, brokerage, or crypto accounts. Isolated workspaces per client, one Stripe subscription, granular permissions, full audit trail. Built for accountants, bookkeepers, financial advisors, and tax preparers.

Start your free trial Read portal guide

No client account requiredRegulated open bankingOne subscription

Send a link; clients connect their own bank.

the three bad options

Stop managing logins. Start managing clients.

Every client-services firm currently picks one of these three bad options. Portals replace all of them.

Painful

Chasing PDFs

Email client. Wait. Client downloads statement. Emails it back. You re-key into your software. Repeat every month, for every client. Tax season makes it ten times worse.

✗Hours per client per month
✗Manual re-keying = errors
✗PDFs lose categorization, merchants, balances

Risky

Shared workspace

Add every client as a member of your workspace. They can see each other's data. Removing one means surgically deleting their banks. One careless click and a client sees another client's transactions.

✗Zero data isolation
✗Confidentiality breach waiting to happen
✗Revoking access is manual surgery

Expensive

Separate subscriptions

Make each client buy their own BankSync subscription, then add yourself as a member. You manage 30 logins, 30 billing portals, 30 places things can go wrong.

✗30 separate invoices to chase
✗Friction onboarding non-technical clients
✗Lose a client → they delete the workspace

the third way

Client Portals

Each client gets their own isolated workspace under your account. You manage everything. They only see their own data. One subscription. Done.

Try it free →

under five minutes

How Client Portals work

From "I have a new client" to "their transactions are in my dashboard" in under five minutes.

A list of BankSync client portals with status pills

every client, one list

1
Create a portal
Name it, pick an icon, add your client’s email.
Under a minute
2
Send the invite
A branded email naming your firm lands in their inbox.
3
They connect their bank
The same regulated flow — CDR, PSD2 or OBIE. Their tokens, not yours.
4
It rolls up to you
Tagged with the portal chip in your unified Banks list.

a real product

Built like a real product, not a feature flag

Portals are full workspaces, not tags, not labels, not filters on a shared table. That means everything that works for your workspace works for your client's.

Truly isolated workspaces

Own tokens, members and audit trail. Revoke one, keep the rest.

Granular per-client permissions

Who can connect banks, build feeds or invite teammates — per portal.

One subscription, family quota

Bank limits pool across the family. No per-seat, no per-client invoice.

Unified family dashboard

Every client bank in one list, tagged by portal, filterable.

Status pills & lifecycle tracking

Active, Awaiting client, Lapsed, Suspended — at a glance.

AI agents query across portals

One API key, scope=family, every client visible to your agent.

What a BankSync client sees inside their own portal

what your client sees

for your workflow

Built for every client-services workflow

Wherever you are in the finance world, if you manage other people's money data, Portals fit your workflow.

For Accountants

Stop chasing PDFs across 40 clients. Send a portal link, watch them connect their bank, see every transaction roll up to your dashboard.

See the accountants workflow →

For Bookkeepers

Run a 10-client practice from one workspace. Per-client portal caps mean no client can accidentally rack up your bank quota.

See the bookkeepers workflow →

For Financial Advisors

See every client's holdings, trades, balances, and loans in one consolidated view, without asking them to share their portfolio screen again.

See the financial advisors workflow →

For Tax Preparers

Seasonal? Portals are perfect. Onboard 80 clients in a week, sync their year's transactions to your sheet, archive the portal when filing's done.

See the tax preparers workflow →

side by side

Portals vs. how you do it today

A side-by-side of the three legacy options and what Portals replace them with.

Job to be done	Chasing PDFs	Shared workspace	Client Portals
Client onboarding	Email them a PDF request	Add them to your workspace	Email a portal invite; they sign up in 2 minutes
Bank credentials	You re-key from statements	Client shares login (✗ never do this)	Client authorizes via regulated open banking
Data isolation	No structured data	Client sees your other clients	Cryptographic per-portal isolation
Billing	Free, but you pay in hours	Pay per seat, per client	One plan covers every client
Revoke a client	Just stop emailing them	Manual surgery on shared data	Delete portal → cascade in 30 days
AI agents (Claude, ChatGPT)	Not possible without manual export	Per-workspace, no aggregation	One API key sees all clients with scope=family

one subscription

Your plan covers every client, with no per-seat charges.

Your Stripe subscription pays for the parent workspace and every portal under it. Your bank quota pools across the family; set per-portal caps if you want to limit any one client.

View pricing →

Example: Professional plan, 15-bank quota

Your workspace

3 of 15 banks

Acme Co portal

4 of 15 banks

Smith LLC portal

5 of 15 banks

Family total12 / 15 banks

for developers

Query across every client with one API key

Add scope=family to any list endpoint and your parent-workspace API key returns rows from every portal, each tagged with which client they came from. Perfect for AI bookkeeping workflows that need to reason across clients.

Read the API guide →

GET /v1/banks?scope=family

{
  "success": true,
  "data": [
    {
      "id": "bnk_abc",
      "name": "Chase Checking",
      "workspaceId": "ws_parent",
      "portal": null
    },
    {
      "id": "bnk_xyz",
      "name": "Acme Co Operating",
      "workspaceId": "ws_acme_portal",
      "portal": {
        "id": "ws_acme_portal",
        "name": "Acme Co",
        "icon": "🏢"
      }
    }
  ]
}

good questions

Frequently asked questions

What is a Client Portal in BankSync?

A Client Portal is a dedicated workspace BankSync creates for each of your clients under your parent workspace. Your client signs in, connects their own bank accounts through regulated open banking (open banking in the US/Canada, CDR in Australia, PSD2 in Europe, OBIE in the UK), and their data syncs into your unified dashboard. You manage every client from one place; each client only ever sees their own portal.

Who is the Client Portals feature for?

BankSync Portals are built for accountants, bookkeepers, tax preparers, financial advisors, virtual CFOs, fractional finance teams, family offices, and any client-services firm that needs ongoing access to multiple clients' bank, brokerage, or investment data. If you currently chase PDF bank statements, add clients to a shared workspace, or run multiple separate subscriptions for clients, Portals replaces all three.

How is a Client Portal different from sharing my workspace with my client?

Sharing your workspace means your client can see every other client's data. Portals create a cryptographically isolated workspace per client, so they only ever see their own banks, transactions, and balances. Provider tokens (open-banking user IDs, CDR consent IDs) live on the portal, so revocation is granular: removing one client never affects another.

How is billing handled for Client Portals?

Your Stripe subscription on the parent workspace covers every portal under it; there's no per-seat or per-client charge in v1. Your plan's bank limit pools across the family: a 15-bank Professional plan covers, say, 3 banks in your own workspace plus 12 across all your portals combined. You can also set per-portal caps (e.g. "Acme Co maxes out at 5 banks") to prevent any one client from consuming your full quota.

Can my clients invite their own team members to their portal?

Optionally. Each portal has a "Members can invite" capability toggle. Off by default in v1, since the typical accountant flow is one client per portal. Flip it on and your client can add their bookkeeper, business partner, or finance team to their portal (but never to yours).

What if a client wants to leave?

Two paths. They can leave the portal voluntarily: banks they connected stay with the portal (you keep historical data) and their user account is removed. Or you can delete the portal entirely: provider tokens are revoked, data is soft-deleted, and a 30-day cleanup window starts. Either way, deleting a portal never affects your other clients.

Can I see all my clients' bank data in one view?

Yes, that's the whole point. Your Banks list aggregates every connected bank from your parent workspace and every portal under it, tagged with a portal chip ("via Acme Co"). Filter by portal, drill into per-client detail, or export everything with one CSV. Feeds, integrations, and jobs all support cross-portal queries.

Do Client Portals work with AI agents like Claude or ChatGPT?

Yes. The BankSync MCP server understands portals natively. Use one API key from your parent workspace, pass `scope=family` on supported endpoints (`/v1/banks`, `/v1/feeds`, `/v1/integrations`), and your AI agent gets data across every client. Build a "find me every unreconciled transaction across all my bookkeeping clients this week" Claude workflow in minutes.

How secure are Client Portals?

BankSync never stores banking credentials. Clients authorize read-only access through their bank's own consent screen via regulated open banking providers. Each portal has isolated tokens, isolated members, and an isolated audit trail. Cross-workspace queries require admin or owner role on the parent. All data is encrypted in transit and at rest.

Which regions are supported for Client Portals?

Every region BankSync supports: United States and Canada (Plaid), Australia (CDR via Fiskil, ADRBNK000246), United Kingdom (Open Banking via Salt Edge), and the EEA (PSD2 via Salt Edge). Mix and match: your portal for an Australian client uses CDR, your portal for a US client uses Plaid, your dashboard sees both side by side.

How do I get started with Client Portals?

Sign up for BankSync, create your parent workspace, then open the Portals tab in your workspace menu and click "New portal". Pick a name, an icon, and optionally enter your client's email to send the invite straight away. They'll receive a branded email, click through, sign up, and connect their bank, typically in under 5 minutes. Then watch them appear in your unified dashboard.

Is there a limit on how many portals I can create?

Portals are available on the Professional and Enterprise plans. Soft limits depend on plan tier, but the practical constraint is your bank quota, not the portal count. Need to support hundreds of clients? Talk to us about Enterprise.

Onboard your first client in five minutes

Sign up, create a portal, send the invite. We'll handle the open-banking flow, the isolation, the audit trail, and the rollup. You handle the client work.

Start free trial Book a demo