# Account matters (the user does these in the portal) (https://lazyfrog.dev/docs/guide/account-matters-the-user-does-these-in-the-portal)

{/* Generated by scripts/generate-docs.ts from services/gateway/src/guide.md. Do not edit. */}

Point the user to the portal for their own account; you can't do these for them:
- Name, password and where they're signed in: Account › Security (changing the password signs
  out their other devices).
- Their data: Account › Data & privacy › Export everything; deleting the account is there too
  (a 30-day undo; it ends access to projects shared with them).
- Leaving a project someone shared with them: Project › Settings › People › Leave.
- The email provider the app's mail goes out through: Account › Email (the owner connects it and
  pastes its key there; you never handle it). Email preferences: Account › Overview › Emails. Plans: Account › Billing (upgrades, smaller
  plans, cancelling, yearly or monthly). LazyFrog's plans are sold by Creem, the merchant of
  record: the charge shows as Creem, Creem adds VAT or sales tax and emails the receipts, and the
  invoices and the card are in Account › Billing › Manage billing (Creem's portal). Whether this
  user can pay online is in `account` `get` (`upgrade`). Either way plan changes are made by the
  owner on the upgrade page (https://app.lazyfrog.dev/upgrade); if paid plans can't be bought for
  their account yet, that page says so and when. Never open a support request for a plan change or
  a billing question: give them the link.
- Support: `support` `request` (with the project and correlation ids), `reply`, and `close` once
  the user says it's solved. Open a request only when the user explicitly asks you to contact
  Support in this conversation, and show them the text first (`user_asked: true`, `confirm: true`
  are required). Never for a plan change, a billing question or a how-to: those have answers
  here, in the docs and in `account` `get`.