Accounts & customer portals

Passwords are hashed with modern algorithms and never stored readable; sessions expire sensibly; role checks happen server-side on every request rather than trusting the browser; and sensitive actions are logged. Where the data warrants it we add second-factor checks. Security is mostly discipline rather than features — the same server-side checks on every route, no exceptions for convenience.

Yes — that is the normal shape of our portal builds. Roles are first-class: a dealer sees and manages their own storefront and customers but nobody else’s; staff roles can be narrowed to specific queues; operators see everything with an audit trail. Sentrix dealers manage their own locations and warranty registrations while customers only verify coverage, on one shared platform.

Usually, yes. Existing records — customers, orders, memberships — are imported and linked so the portal is useful from the first login rather than starting empty. Passwords cannot be migrated from a properly built system (they are hashed), so returning customers set a new one through a verified email flow on first login. We plan that first-login experience deliberately so migration does not feel like a reset.

Where it fits the audience, yes — consumer products often benefit from Google sign-in, while dealer and staff portals usually want plain email accounts the business controls, and corporate clients sometimes need SSO against their existing directory. It is an audience decision rather than a default; we will recommend based on who is actually logging in.