Team & access settings
Three of these four decide who can do what. The fourth records what was done.
What is in this group
Section titled “What is in this group”| Destination | What it governs |
|---|---|
| Team members | Who has access to your store’s admin. |
| Roles & permissions | What each of them can do. Roles are a matrix of permissions, and you can define your own rather than only using the built-in ones. |
| Activity log | What has been done in the admin, and by whom. |
| Social login | Whether shoppers can sign in to your storefront with an external account. |
Social login is about shoppers, not staff
Section titled “Social login is about shoppers, not staff”The one that catches people out. Social login sits in this group because it is an access setting, but it governs your storefront’s customers signing in to their own accounts — not your team signing in to the admin. Turning it on does not create a way into your admin.
What the activity log covers, and what it does not
Section titled “What the activity log covers, and what it does not”The activity log records actions taken in the admin. It is not a security audit trail of sign-ins: CIQRA keeps a complete sign-in audit on the operator side, and the merchant admin deliberately does not expose one. If you need to answer “who signed in, from where, when”, that is a question to put to us rather than one this screen answers.
Two-step verification is available per user — each person turns it on for their own account. There is no store-level setting that requires it of the whole team in this release. We would rather say that plainly than let “2FA supported” imply it can be enforced.
What this page does not say
Section titled “What this page does not say”- It does not give click-paths. No verified screenshot of these screens exists in this help centre yet — though our test suite does capture the roles matrix and the custom-role dialog, so this is the group most likely to gain one first.
- It does not list the built-in roles or their exact permissions. A permission matrix printed here would go stale the first time one changes; the screen is the authority.
- It does not explain impersonation. Support-side access to your store is a platform-side capability and is described under Transparency, not here.