Skip to content

Sign-in protection & audit trail

Five failed password attempts lock an account for fifteen minutes.

There is a second sign-in surface with different behavior, and the difference is deliberate:

Available per user. Anyone with a CIQRA sign-in can enable two-step verification on their own account.

A store owner can require it of the whole team. Under Settings → Security & access, the card Two-step verification for your team has the switch Require two-step verification for all team members. With it on, a member who has not set up two-step verification is asked to set it up before they can open the admin. The owner has to turn it on for their own account first — the switch refuses otherwise, so an owner cannot lock themselves out of their own policy.

It is off until an owner turns it on. Until then, each person decides for their own account.

Both surfaces now record sign-ins, with one boundary on the merchant side that the table names.

Surface Recorded
CIQRA operator console Yes — failed sign-in (unknown address), failed sign-in (wrong password), blocked sign-in (suspended), successful sign-in, and sign-out, each with the actor and the originating IP address
Merchant admin Yes — successful sign-in, refused sign-in, sign-out, and changes to two-step verification (turned on or off, new recovery codes, the team policy, an owner’s reset). They appear in Settings → Activity log, which staff with the staff-management permission can open.

The boundary on the merchant side: a sign-in refused on the shared multi-store sign-in address happens before any store has been chosen, so there is no store to attribute it to, and it does not appear in any store’s Activity log. Those refusals are rate-limited and logged on CIQRA’s side instead. A refusal on your store’s own sign-in address is recorded in your log.

The events are written where the sign-in happens, not by the audit middleware: the middleware records changes made by someone already signed in, and it is still kept out of the identity and token paths on purpose, so that the component which records changes never sits in the path that handles credentials.

  • It does not claim that every store enforces 2FA. The team policy exists and is off until an owner turns it on.
  • It does not claim that every refused sign-in reaches your Activity log. Refusals on the shared multi-store sign-in address cannot be attributed to a store, so they do not.