Authentication & Access

The problem: new customers need to open an account entirely on their own, at midnight, on their phone. If a sign-up ever needs your help, or a mistyped email quietly sticks to an account, the mess lands on your desk.

Shoppers create their own account with a name, email and password, and are treated as a customer from the first minute. A verification email goes out straight away so the address is confirmed before anything important depends on it, with nothing for you to set up or untangle.

How to use it

1. From the storefront, the shopper opens the Create account page.
2. They enter their name, email address and a password, then confirm the password.
3. On submit they are signed in straight away and shown a "please verify your email" notice.
4. A verification link is emailed to the address they entered.

The problem: somewhere out there, someone is always trying passwords against a shop's sign-in page. And you do not want to run two separate doors, one for shoppers and one for staff, just to keep the back office apart.

The everyday email-and-password sign-in, shared by shoppers and staff. Repeated wrong attempts are slowed down automatically to shut out guessing, and after login each person lands in the right place: shoppers in their account, staff in the admin.

How to use it

1. Open the storefront Sign in page.
2. Enter your email and password, then submit.
3. You are taken to your account (or, for staff, to the admin dashboard).
4. To sign out, use the Log out option in the account or admin menu.

Good to know: after too many failed attempts in a short window the form pauses you with a "too many attempts" message, then lets you try again shortly after.

The problem: a customer who forgot her password either gives up on the order, or opens a second account and loses her history, and either way the "I cannot log in" message ends up with you.

A safe way back in by email. The shopper requests a reset, gets a one-time link in her inbox, and chooses a new password from that link: same account, order history intact, nothing for you to do.

How to use it

1. On the Sign in page, the shopper clicks Forgot password.
2. They enter their email address and submit; a "check your email" message confirms it.
3. They open the email and click the reset link.
4. They set a new password and confirm it, then sign in with the new password.

Good to know: for safety, completing a reset signs the account out of every other device, so a stolen session cannot survive the very fix the customer just made.

The problem: a shopper mistypes her email at sign-up and never notices. From that day her order confirmations, receipts and reset links all go to a stranger's inbox, and she blames the shop.

Confirms that a new account really owns the email address it signed up with. The shopper clicks a one-time link in her inbox to prove the address is hers, before any order mail depends on it.

How to use it

1. After registering, the shopper sees a "please verify your email" page.
2. They open the verification email and click the link inside it.
3. The address is confirmed and they continue into the store.
4. If the email never arrived, they can request a fresh link from the verification page.

Good to know: the link works once and expires, so an old forwarded email cannot be misused, and a fresh link can always be sent.

The problem: your admin password could leak tomorrow, reused on another site, phished, or read off a note by the till, and that one password can change prices, issue refunds and export your customer list.

An optional second lock on top of the password. Once turned on, signing in also asks for a fresh six-digit number from a code app on your phone, so a stolen password alone is not enough to get in.

How to use it

1. Open the security settings and choose Enable two-factor.
2. Scan the on-screen QR code with a code app on your phone (for example Google Authenticator or Authy).
3. Save the recovery codes that are shown somewhere safe, in case the phone is lost.
4. Enter the current six-digit number from the app to confirm, and two-factor is now active.
5. From then on, every sign-in asks for a fresh number (or a recovery code if the phone is unavailable).

Good to know: recovery codes are single-use. Keep them safe; each one lets you sign in once if you cannot reach the code app on your phone.

The problem: you step away from the counter and the admin stays open on the screen. One idle minute is all a passer-by needs to quietly switch off the very settings that protect the shop.

An extra check before the most sensitive actions, such as turning two-factor on or off. Even while signed in, the user is asked to re-enter their current password, proving it is really them at the keyboard and not whoever found the screen unlocked.

How to use it

1. Start a sensitive action (for example managing two-factor settings).
2. If it has been a while since you last confirmed, a short "confirm your password" prompt appears.
3. Enter your current password to continue.
4. The original action then proceeds as normal.

Good to know: once confirmed, you are not asked again for a few hours, so it stays out of the way during normal work.

The problem: a password change that does not evict whoever is already inside is no fix at all. The forgotten session on a shared tablet, or an intruder who got in once, would simply carry on as if nothing happened.

Changing the login email or password is treated as a security event. On save she is signed out everywhere else, and changing the email needs the current password and quietly alerts the old address, so nobody can silently take over an account.

How to use it

1. Open your profile or account settings and update your password (or your login email).
2. Changing the email asks you to re-enter your current password as a safety check.
3. On save, you stay signed in on the device you are using, but every other session is logged out.
4. For an email change, a new verification link goes to the new address and a heads-up goes to the old one.

Good to know: this is why a password change can sign you out of your phone or another browser; it is deliberate, so a stolen session cannot outlive the change.

The problem: you cannot run the shop alone, but delegating should not mean handing over the keys. A seasonal packer needs to move orders along; she does not need to see payout details, change prices or delete your catalogue.

Create accounts for your team and decide exactly what each person can do. Roles range from full Admin down to a read-mostly Shop Manager, and you can fine-tune a single person's permissions on top of their role. A lower-ranked staffer can never edit or delete a more privileged account, and customer accounts never appear here.

How to use it

1. Open Users to see your staff, each with their name, email and role.
2. Click Add user to create a new staff member: enter their details and pick a role (you can only assign roles at or below your own level).
3. Open any staff member to review their account, change their role, or toggle individual permissions in the permission matrix.
4. Save. The new permissions take effect the next time that person uses the admin.

Good to know: the team hierarchy is always respected. A lower-ranked staff member can never edit or delete a more privileged account, and you can only grant a permission you hold yourself, so nobody can quietly promote themselves or another person above their own level.

The problem: a price is suddenly wrong, a product has vanished, and nobody remembers touching it. Without a record, the mystery turns into a guessing game and awkward questions for the whole team.

A complete, searchable record of who changed what. Every create, update and delete made by a signed-in user is captured, and any entry opens into the exact before-and-after of each field that changed, so a mistake or a disputed change always has a clear author and an exact time.

How to use it

1. Open Audit Log under the System area.
2. Browse the time-ordered list of changes, each showing the action, the record, the person and the time.
3. Use the search box and the event filter to narrow down to what you are looking for.
4. Click an entry's changes to open the full before-and-after detail for every field.

Good to know: passwords and card numbers never appear in the log, and the Audit Log is available to Admin and Manager.

The problem: the store does invisible work all day, sending confirmations, receipts and campaign emails, and when that work quietly stalls, the first you hear of it is a frustrated customer days later.

A live window over that background work. Stat cards summarise what is queued, running and failed, tabs let you dig into the Queued, Failed and Batches lists, and admins can retry or clear failed work in minutes; managers get a read-only view.

How to use it

1. Open Jobs under the System area.
2. Glance at the stat cards (Queued, Running, Failed, Batches) for the overall picture.
3. Switch between the Queued, Failed and Batches tabs, using the queue filter and search to narrow the list.
4. On a failed job, click the error to read the full details; admins can Retry or Delete a job, or Retry all / Flush old in bulk.
5. The list auto-refreshes every few seconds; a Refresh button forces an immediate update.

Optional module: switch the Jobs monitor on or off under Settings → Features. Every retry or flush is recorded in the Audit Log.