B2C architecture
Architecture
In consumer applications, users fully own their accounts and control their identity and authentication, with no involvement from other “middle-layer” parties like businesses or organizations. This is the key distinction between B2C and B2B identity architectures.
Build your B2C identity system
Various authentication methods: password, passwordless, and social sign-in.
Authenticator app, Passkey, Backup codes. Allow users to enable MFA independently.
Use Logto Account API to develop account settings and user profile pages for your end-users.
Define roles and assign corresponding permissions to control user actions.
Manage user identities in Logto Console or Logto Management API.
Allow users to authorize third-party apps themselves.
Connect your requirements to Logto’s support toolkit
This architecture includes two main parties involved in the management scenario. Depending on your specific needs and objectives, all or only some of these parties may be involved.
We’ve summarized common use cases, highlighting the key objectives of each user identity managing tasks and the related products and APIs we offer. You can map your needs to our services to get started quickly.
| Users | Goal | Logto products and APIs |
|---|---|---|
| Developers | Manage and safeguard the user identity system and work directly with the identity database. | |
| End user/Consumers | Manage their own authentication and personal information. |
Related resources
Use Logto for various business models' identity systems
Logto's authorization system and its use in identity management scenarios