Signing up and signing in

Creating your shop

Four things: your Shop name, Your name, an Email, a Password of at least ten characters and no more than seventy-two (an accented letter or an emoji counts as more than one). Your browser fills the hidden shop timezone. An en-CA or fr-CA browser locale starts in CAD; every other locale starts in USD. Then Create my shop. No card, and nobody rings you.

The email you give becomes your sign-in and is the only address that can reset your password, so use one you will still have in three years. The detected timezone drives your board, appointment times and reminders; change it under Hours if the browser got it wrong. With JavaScript off, signup uses America/Los_Angeles and USD so the form still works. Billing currency can be corrected in Profile until the shop stores its first price or money figure.

That one form creates the organisation, the shop, your owner account and your subscription record together. You are signed in on the spot and land on Get started — one step at a time to your first estimate sent. You do not retype the password you chose ten seconds ago. There is no confirmation email and nothing to click.

Signing in

Email, password, Sign in. There is one checkbox worth a thought: Keep me signed in is on by default and should be off on anything shared. The line under it says the same thing — Turn this off on shared devices.

Sign in with a code is the passwordless shop-floor door. Enter the shop address name and the phone recorded on your staff membership, then type the six digits from the text. The digits work once, expire after five minutes, and five wrong guesses retire them. The text begins with the digits so a phone preview can show them without opening the message.

The request screen always gives the same answer. It does not confirm whether that shop exists or employs somebody with that number. An owner or manager sets the number in Team, under that person's Staff sign-in phone field. Clear the field to turn the code door off for that person. The number receives sign-in codes only; if it is blank, no text goes out. A code sign-in on a shared tablet lasts for the shift rather than being remembered for a month.

A passkey counts as a second factor. If you have set up an authenticator, the second step asks for a 6-digit code and offers to remember the device for a while. Recovery codes go in the same box as an authenticator code; if a passkey is on file, the same step also offers that passkey. Owners and managers must keep at least one of those factors on their account.

Nothing on the two-factor screen stops you turning the last factor off, and it is worth knowing that before you do it. Turn off is offered whenever an authenticator is enrolled, whatever your role and whether or not a passkey is on file; a live code is all it asks for. If you are an owner or a manager and that authenticator was your only factor, the settings gate will then ask you for a second factor you no longer have, and every protected settings screen closes to you until somebody enrolls one again. Add a passkey first, on Settings → Sign-in & security, and then turn the authenticator off.

A failed sign-in tells three different truths, and which one you get is worth knowing. A credential Torqix genuinely refuses says Sign-in failed. Check your email and password. If the software could not finish checking — the deployment or its database is unavailable — it says Torqix couldn't verify your sign-in. This is our fault, not your password. Retyping it won't help; try again in a few minutes. If your second-factor ticket simply took too long, it says Your sign-in expired. Enter your email and password to start again. Only the first of the three is about you.

Where you land

A brand-new shop opens on Get started: seven short steps, one open at a time, from the labor rate to sending your first estimate. Each step ticks itself when the work is done, and the board shows the next one until you finish or hide it. Sample data stays available below the list.

If current code is running ahead of its database, the shell may still open. A strip across every signed-in page says This deployment is waiting on a database migration. Everything on the page underneath is safe to use; newer settings screens may stay unavailable until the migration is applied. That strip is a warning, not a fix — whoever deploys Torqix still has to run the database migration.