Signing In on Excel and the CLI, and Signing Out Everywhere

Some places you use BankSync can't show the normal sign-in page: the BankSync add-in inside Excel, and the BankSync CLI in a terminal. They sign in with your help from a browser where you're already signed in, using a one-time code you can see.

Sign in from the Excel add-in#

Open BankSync from the Home tab in Excel and choose how to sign in (the Excel add-in guide covers installing it):

• Email and password works right in the add-in.
• Google opens a small sign-in window. Once you sign in there, the window closes and the add-in is signed in. The code that carries your sign-in to the add-in works once and only for a minute.
• On Excel for Mac, where Google refuses to sign in inside Excel's windows, Google goes straight to a code and a link. On the web and Windows the add-in shows them if the window can't open. Follow the steps below.

Approve a code#

The device signs in a few seconds later, and BankSync emails you "New sign-in to your BankSync account". A code works once and expires after ten minutes. After five wrong codes, wait fifteen minutes before trying again.

Never approve a code someone else sent you, even if they say they're from BankSync. BankSync staff never ask you to approve a code.

Sign in from the CLI#

Run banksync login --device on the machine you want to sign in. It prints a code and a link. Open the link in any browser, type the code, check what the CLI is asking for, pick the workspace it may use and approve. The CLI then has the same kind of access as banksync login: it appears under Settings, Developers, Connected apps, and you can remove it there. See the developer guide for scripts and headless machines.

Sign out everywhere#

If you see a sign-in you didn't make, or you lost a laptop:

1. Open Settings, Security, or the link in the "New sign-in" email.
2. Select Sign out everywhere and confirm.

This ends every signed-in browser and the Excel add-in, this browser included. You sign in again afterwards. Sessions that were already open can keep working for up to an hour before they notice.

It doesn't remove API keys, connected apps (the CLI included) or SimpleFIN access, and it doesn't stop your feeds or change where they send data. Check Settings, Developers for any keys or apps you don't recognise and remove them there, and check your feeds and their destinations. Then change your password, and turn on two-step verification if it isn't on.

What a device session can't do#

The Excel add-in can read and sync your data like you can, but BankSync refuses changes that need you in person when they come from a code sign-in:

• Keys and apps: API keys, SimpleFIN access, connected apps and developer apps.
• Other people's access: inviting, changing or removing members, leaving, ownership, sharing a workspace with a firm, client portals and client requests.
• Where data goes: verified and mailbox recipients.
• Money and endings: billing and subscriptions, deleting a workspace or your account, and changing your email.

For those the add-in opens BankSync in your browser, where you sign in yourself.

Two-step verification and your password are set through Google's Firebase sign-in service rather than through BankSync, so BankSync can't refuse those changes itself. For about five minutes after a code sign-in, Firebase treats that session as a recent sign-in. That is why you should only approve a code you started yourself, and why BankSync emails you about every approval. If you see one you didn't make, use Sign out everywhere, then change your password and check your two-step verification settings.