What your clients see

What a client sees when their advisor asks for their bank data: the request email, the code, the share confirmation, their bank consent screen, and the workspace they end up with.

4 min read

On this page

This guide follows a request from your client's side, so you know what they see before you send one.

The request#

Your client gets an email from you, shown as "Jane Smith via BankSync", or a link you sent them yourself. Until you verify your practice, the email and the request page show your email address. Once you verify, they show your practice name with your domain, for example "Smith Bookkeeping (smithbooks.com)".

  1. They open the link and see who is asking and what you are asking for.
  2. They choose Email me a code and enter the 6-digit code from that email, which confirms they are happy to share with you. The confirmation names you, says what you will see, and is recorded. There is no password to set up.
  3. They connect on their bank's usual consent screen. BankSync never sees their bank login.
  4. They answer your questions and send it to you.

If something about a request looks wrong, the request page has a link to report it to BankSync. Reporting it as unexpected or as phishing withdraws the request, so its link stops working.

When the client pays#

A client who pays for themselves chooses a plan before they connect: Starter ($5 a month, 1 bank) or Standard ($7 a month, 5 banks). The workspace is theirs. They see their own banks, and can set up a feed or an export without you. They share it with you, so your staff can work in it with the role they chose.

They can see who they share with, and stop sharing at any time, from their workspace settings. They can share with up to 3 advisors.

When you cover the client#

A client you cover never needs a subscription. If you invite them by email rather than send a request, they sign in or create a free BankSync login, confirm sharing on one screen that names you, and land in the workspace you set up for them. They do not see your own workspace or your other clients.

A covered client's workspace is a constrained one. In Settings, only General and Profile remain:

Settings sectionVisible to a covered client?Why
GeneralYes (name and icon, read-only)Basic workspace information
ProfileYesThe client's own account
MembersNoYou manage membership from your own workspace
BillingNoYou cover it; it has no subscription of its own
DevelopersNoAPI keys are reserved for you
AffiliateNoA rewards page for paying workspaces
Delete Workspace (Danger Zone)NoOnly you can delete it

The routes are guarded too: a client who deep-links to /billing or /danger-zone is sent back to General. A covered client cannot rename the workspace, change its icon or invite new members.

What a covered client can do, by role#

CapabilityEditorViewer
See the workspace's banks and dataYesYes
Connect a new bank (when the Access tab allows it)YesNo
Create feeds into Sheets, Notion or Airtable (when the Access tab allows it)YesNo
Rename the workspace, invite members, or open Billing or DevelopersNoNo

When the Access tab does not let clients connect banks, the client still sees the banks already connected, but the option to add one is removed and the server refuses a direct attempt.

Australian banks#

Australian banks (Consumer Data Right) work for both kinds of client. The client connects them after confirming they are happy to share with you, and you receive their data only while that confirmation is in force.

Troubleshooting#

Common client-side snags

Code not arriving? It goes only to the address the request was sent to; ask your client to check spam, or resend the request. Invitation link not working? Invitations expire after 7 days; resend it from the Members tab. Covered client cannot add a bank? Give them the Editor role and allow bank connections on the Access tab. Client wants the workspace renamed? Only you can do that, from your own workspace.

Use this page with your AI assistant

Every BankSync doc is available as plain Markdown for agents and LLMs.