One address, answered by one person.

1. On the old machine, copy the folder Documents\Binse Data Analytics & Dashboards\. Workflows, dashboards, diagrams, schedules and everything else you saved are ordinary files inside it, and the shape libraries, templates and plugins you added to Diagrams are in folders under Diagrams\, so copying the folder copies the lot.
2. Still on the old machine, press Release this computer, in the footer of the home page, of Data Flow or of Dashboards. It needs an internet connection, and it gives that computer's place on the licence back.
3. Install Binse on the new machine. The download, the hash and the first-run prompt are on the install page.
4. Open Data Flow or Dashboards, paste the licence key from the receipt email into the Licence key box, and press Activate. A copy licensed by a file issued by hand needs a new file for the new computer instead, loaded from the same screen, and support issues it against the computer code shown there.
5. Put the copied folder back under Documents\ on the new machine, under the same name.
6. Open the Schedules page once. Every switched-on schedule that has lost its Windows task is given one back in the background while the list loads.

How this actually works

Installing Binse again costs nothing. The activation is saved outside the program folder, so a repair or a fresh install of Binse on the same computer finds it where it was.

Renaming the PC does not make it a new computer. Binse identifies a computer by a computer code made from the Windows machine identifier alone, so renaming the PC or signing in under a different Windows account leaves the code as it was. Reinstalling Windows gives the computer a new identifier, and Binse then treats it as a computer it has not seen, which is why step two comes before a machine is wiped.

Releasing a computer is a button. If the old machine is already gone, lost or dead before anybody pressed it, write to support naming the key, and its place is given back by hand inside the response window.

In the receipt email. Lemon Squeezy is the merchant of record for every sale. It makes the licence key at the checkout and sends it with the receipt, so the key is in that email rather than on a page of this site.

If the email has gone. Write to support from the address the purchase was made with. The order is found by hand and the key is sent back. Nothing is reset and nothing is reissued, so an old copy of the key stays valid.

What the key is for. The licence screen in Data Flow and Dashboards has one box, labelled Licence key. Paste the key, press Activate, and the app confirms it with Lemon Squeezy from then on, about once a week, in the background. A shop that hands out keys from a list issues a key in the shape BINSE-XXXX-XXXX-XXXX instead, and the same box takes it. The security page prints what each kind sends.

Not open yet. The store has not opened, so no key has been sold. Until it opens, a licence is a file issued by hand against the computer code Binse shows under Have a licence file, or need one issued by hand?, and this page will say so on the day that changes, with the date on the changelog.

What to press. Choose More info, then Run anyway. The publisher shows as unknown, and that is accurate: there is no Authenticode signature on the shipped file and no signing step anywhere in the installer script.

Check the file before pressing anything. The SHA-256 of the published installer is on the install page, beside the download, with the receipt it was measured in. Because the file is unsigned, that hash is the check that exists.

Nothing asks for administrator rights. The installer asks Windows for the lowest privileges it offers and installs into one user's own AppData folder. There is no Windows service, no machine-wide registry key and no elevation prompt.

A managed machine may refuse outright. Where an employer blocks unsigned installers by policy, the prompt does not offer Run anyway at all, and nothing inside Binse can change that. The next step there is a conversation with whoever manages the machine, and the hash on the install page is what they will ask for.

A certificate has not been bought. Until one is, every first run meets this prompt. It is a fair reason not to buy, and support cannot make it go away.

There are two parts to it: a connection string and a sign-in that happens outside Binse, with the warehouse itself. Binse Enterprise adds a third for Explore, a guard on what a query is allowed to read.

Add the connection

Open Connections to databases and APIs from the home page, or press the plus beside the connection picker on a tool. The connection string is bigquery://project/dataset, for example bigquery://acme-analytics/curated. That dataset becomes the default, so a table in another one is named as dataset.table, and a table in another project as project.dataset.table. Add ?location=EU when the data is not in the multi-region the driver would otherwise guess.

The driver is bundled in the installer, so there is nothing to download and no pip install line to run.

Sign in once, outside Binse

With no credentials option in the string, the driver uses the machine's default credentials. On an ordinary laptop that means running this once, in a terminal, with the warehouse's own command-line tool:

gcloud auth application-default login

A browser window asks you to sign in and leaves the credentials where the driver looks for them. That command-line tool is not part of Binse and is installed separately, from whoever runs the warehouse. Binse writes no key of its own, and there is a test that fails the moment that default changes.

Queries run as the person who asked

Every query carries that identity, so the warehouse's own access control decides what may be read. A table you cannot see in the warehouse is invisible in Binse, and the error text comes from the warehouse. In Binse Enterprise, two people opening one Explore report can see different numbers, or one of them an error, because they hold different grants. An Explore catalogue says what is published, not who may read it.

A service-account file can be named with ?credentials= for the rare case that needs one. Binse hands that file to the driver and creates no key itself.