A personal account (customer or partner cabinet) is a logged-in product: profile, orders or tickets, documents, roles, and an API your mobile app can reuse. This page does not assume 1C. When the ledger is 1C, use personal accounts for 1C. Generic admin tools for internal staff are admin panels.
I design auth (email/magic link/OAuth as the brief says), session handling, and a permission model that matches how you actually sell—not a single “isAdmin” flag. Typical slices: order history and invoices, file exchange, status of a request, B2B price lists. Payments still belong in a real checkout if you sell goods—see cart and payments. The cabinet should not become a homemade shop.
Stack: React + TypeScript UI, Node.js API, PostgreSQL. Related work: nextevents, employment_cal, EmploymentApproval—logged-in flows, roles, and operational data. CRM as the system of record for deals is Bitrix24 / amoCRM.
Handoff: how to create a user, how to impersonate safely on staging, password reset, audit log. Out of scope: designing your entire brand identity, or a marketplace with escrow.
Timeline: a focused B2C or B2B cabinet MVP is often 5–10 weeks depending on integrations.
What you get
- Role matrix, screens, and “done” for the first release
- Auth, cabinet UI, API, staging, tests on critical paths
- Hypercare for login edge cases and permission bugs
- Notes so your team can add a page without archaeology
