Skip to content

Account & Security

This section is about who can get into your store and how securely they do it — your own account, the people on your team, and the protections around signing in. Staff sign in with a password and, where it is turned on or required, a two-step (2FA) code; access is controlled by roles and permissions, and sessions are managed. Changes and sign-ins are recorded to an individual account — see Transparency for the one kind of refusal that is not.

On a CIQRA sign-in page, never on the store itself: email or username and password, then a 6-digit two-step (2FA) code if two-step verification is on for the account. It is off for a new account until the person turns it on, or until a store owner turns on Require two-step verification for all team members. See Sign-in & security, and what is and is not recorded.

Enter one of your saved recovery codes in place of the 6-digit code. If you have none left, a store owner can open Team members and choose Reset two-step verification for you. Contact CIQRA support only if you are the owner and no other owner can reset it.

With roles and permissions. Permissions are scoped to areas of the product — catalog, orders, customers, analytics, CMS and settings — so you grant each teammate a role that fits their job and nothing more. See Staff roles & permissions.

Yes. Because permissions are scoped by area, you can grant order-related capabilities without also granting the ability to change settings or edit your catalog. Grant the narrowest role that lets someone do their job.

A session is an active sign-in tied to your account — what keeps you signed in after you sign in. Sessions are managed, which is part of how CIQRA keeps access under control. See Your account & sessions.

Mostly, and the exception is worth an extra sentence.

Actions that change something are recorded and can be attributed to an individual account — which is the reason to give each teammate their own sign-in rather than sharing one.

Sign-ins, refused sign-ins and sign-outs are recorded too, in Settings → Activity log — except a refusal on the shared multi-store sign-in address, which happens before a store is known and so reaches no store’s log. Reads are not recorded: “who looked at this” is not a question the trail can answer today. The detail is in Transparency → Sign-in protection & audit.

Yes. CIQRA has a central Settings area covering billing, domains, languages, notifications, roles, payments, shipping and more.

This section does not walk through it step by step yet. That is a documentation gap, not a product one — and we would rather name it that way round than let a missing article imply a missing feature.