Skip to main content

Your account

Plans: Starter ✓ · Growth ✓ · Pro ✓ · Agency ✓ (account features available to every signed-in user regardless of plan)

The Account page covers your personal Clione account — separate from the org-level settings. Sidebar → click your name (bottom-left) → Settings, or open /settings directly.

The page has sections for:

  • Profile — display name and language.
  • Password — change password (when not using Google).
  • Two-factor authentication (2FA) — TOTP setup, recovery, disable.
  • Google account link — link/unlink Google for one-click sign-in.
  • Trusted devices — devices that skip 2FA for 30 days.
  • Organization — read-only summary of which org you're in, your role, and the plan.

Profile​

  • Display name — what other members see in audit logs and "last edited by" tags. Edit and click Save.
  • Language — picks the dashboard locale. Currently English and Spanish.

Password​

If you signed up with an email + password (not Google):

  1. Enter your current password.
  2. Enter the new password twice.
  3. Click Save.

New password must be at least 8 characters. The change takes effect on next sign-in; current sessions remain active.

Forgot password​

Use the Forgot password link on the login page. You'll get a one-time reset link by email. Links expire in 1 hour.

If reset emails aren't arriving, a Clione admin can resend the link from the Superadmin → Users tab (we ship support tooling for this — task #77).

Two-factor authentication (2FA)​

Strongly recommended for owners and admins.

Enable​

  1. Click Enable 2FA.
  2. Clione shows a QR code + a secret string. Scan the QR with an authenticator app (Authy, Google Authenticator, 1Password, Bitwarden).
  3. Enter the 6-digit code from the app to verify.
  4. 2FA is now on. From now on, sign-in from a new device requires the 6-digit code.

Email fallback​

If you lose your authenticator, you can request a one-time code by email during sign-in. Pick Send code by email on the 2FA prompt.

Disable​

  1. Click Disable 2FA.
  2. Enter the current 6-digit code to confirm.
  3. 2FA is off. Trusted devices are cleared.

Recovery​

If you've lost the authenticator AND email access:

  • Contact your org owner — they can request a reset via support.
  • If you're the owner, contact support directly with proof of identity. Reset typically takes < 24h.

If you'd rather sign in with Google than with a password:

  1. Click Link Google account.
  2. Authorize on Google.
  3. From next sign-in, click Sign in with Google instead of entering email + password.

You can have BOTH a password and a Google link — they don't replace each other. To unlink Google later, click Unlink Google account (only available if you have a password set, otherwise you'd be locked out).

Trusted devices​

When you sign in with 2FA, an optional "remember this device for 30 days" checkbox creates a trusted device entry. From that device, you skip the 2FA prompt for the next 30 days.

The Trusted Devices section lists every active trusted device:

  • Browser + OS (parsed from user agent — usually accurate but generic).
  • City / country (from IP geolocation).
  • First trusted at + expires at.
  • A Revoke button.

Revoke from any device that's stolen or that you no longer use. The next sign-in from that device will require 2FA again.

Organization summary​

Read-only block showing:

  • Your role in this org (Owner / Admin / Member).
  • The org name.
  • The current plan (display name).

To change your org-level role, ask the owner. To change plan, see Billing.

API keys (developer access)​

If you intend to call the Clione API directly (e.g. from your headless storefront or your CI), you'll mint API keys at Org → API Keys. Keys are org-scoped, not user-scoped — anyone in the org can use them. Tie a key to a specific use case (e.g. "Hydrogen build", "Stencil JS"), copy the secret once on creation (it's hashed at rest and not shown again), and store it in your platform's secret manager.

Key types:

  • Read-only — list products, fetch JSON-LD, fetch enriched copy. Safe to expose in client-side code if you scope to the public endpoints.
  • Read + write — additionally allows enrichment, FAQ writes, propagation triggers. Server-side only.
  • Bulk — Pro/Agency, additionally allows long-running batch operations (bulk enrich on >100 entities, full sync triggers).
  • Internal (__-prefixed) — auto-created for Schema Injector etc. These are hidden from the user list and rotated automatically when you reinstall the Schema Injector. You shouldn't touch them.

See developers/api-authentication for the full reference.

Per-platform notes​

Your account is platform-agnostic. The same account works across all stores (BC, Shopify) and across all orgs you're a member of.

Some platform-specific touches:

  • BigCommerce SSO — not supported today. You sign in to Clione separately from BC.
  • Shopify SSO — not supported today. You sign in to Clione separately from Shopify.
  • Shopify staff session reuse — not supported. Each Shopify user who needs Clione access creates a Clione account directly.

If your org runs SAML or another SSO that you'd like Clione to integrate with, contact the sales team — it's on the roadmap for Agency-plan deployments.

Session lifetime​

  • A signed-in session lasts 30 days if "remember me" is checked, 24 hours otherwise.
  • Trusted-device 2FA bypass lasts 30 days per device.
  • API key JWT tokens (when using the JWT flow) have a 1-hour TTL; refresh tokens last 30 days.
  • Forced sign-out happens on password change, on 2FA disable, on role demotion to Member from Admin (admin sessions are bumped to revalidate).

Audit log​

The org's audit log (visible to admins under Org → Audit) shows the security-relevant events tied to your user:

  • Sign in (success + failure).
  • Password change.
  • 2FA enable / disable.
  • Trusted device added / revoked.
  • API key created / revoked.
  • Member promoted / demoted.
  • Store added / removed.
  • Plan changed.

Each entry has IP, user-agent, timestamp, and the affected resource. Retention: 90 days on Growth, 180 days on Pro, 365 days on Agency.

Troubleshooting​

"Wrong password" but I'm sure it's right — Account lockout after 5 failed attempts (15-minute cool-down). Wait 15 minutes or reset via Forgot password.

2FA code rejected even though it's fresh from my app — Server / phone clock drift. Make sure your phone time is set to "automatic". If still failing, use the email fallback or contact support.

"Trusted device" entry I don't recognize — Revoke it immediately, then change your password. Then contact support with the entry's IP / city for an audit.

Google sign-in fails with "account not found" — The email on your Google account doesn't match any Clione account. Sign in with email + password first, then link Google from the Account page using the matching email.

Email fallback for 2FA never arrives — Check spam, then check that the email in your Profile section is correct. If still nothing, contact support — we can audit the email log and trigger a manual resend.

Stuck in user impersonation (superadmin) — Known bug (#97). The "Exit impersonation" button in the banner sometimes fails to clear the impersonation cookie. Workaround: open /api/v1/auth/exit-impersonation in the browser tab manually, or sign out completely and back in.

Data export​

You can export your personal data at any time from Account → Privacy → Export my data:

  • Profile (name, email, language preference).
  • Audit log entries tied to your user.
  • API key metadata (not the raw secrets — only IDs and timestamps).
  • Trusted device list.
  • 2FA status (enabled/disabled — not the secret).

Export arrives as a ZIP of JSON files within 24 hours, sent to your account email.

Account deletion​

From Account → Privacy → Delete my account:

  • The deletion request goes through a 7-day grace period (same as store deletion).
  • During the grace period you can cancel via the email link.
  • After the grace period, your user is anonymized in our database — your profile fields are scrubbed, but audit entries you authored are preserved with the placeholder [deleted user].

If you are the Owner of an org, you cannot delete your account until you've transferred ownership. The dashboard blocks the deletion request with a clear error.

GDPR / data residency​

  • Data is stored in EU (Frankfurt, eu-central-1) by default.
  • US-region storage is available for Pro and Agency plans on request.
  • Backups are encrypted at rest and replicated across two AZs in the chosen region.
  • We never transfer raw catalog data outside the chosen region.
  • LLM API calls leave the region per the LLM provider's network topology — the prompts contain catalog text only, no PII.