Mosaic B2B Identity centralizes access to your applications for members of external business organizations, such as customers, partners, and branches. It lets you model applications, organizations, optional hierarchies, and roles to manage different access needs at scale. Each organization can manage its own members within the scope you define. Mosaic B2B Identity is a centralized way to manage access for external business organizations such as customers, partners, and branches. It helps you model Mosaic applications, organizations, optional hierarchies, and roles, while allowing each organization to manage its own members within the scope you define.
In B2B scenarios, your customer-facing application is used by people who belong to other organizations, such as customers, partners, or branches. Each organization may need different levels of access, which can become difficult to manage at scale.
Use B2B Identity when:
- Your app is used by multiple organizations (companies, partners, or branches).
- Each organization has its own set of members who log in to your app.
- You need to control what each organization can do (which apps and which roles they can use) while letting organizations manage their own members.
For example, a holiday booking platform:
- Your app: a booking platform (flights, hotels). You create it and define what roles exist in the app (for example, Booking agent, Viewer, Approver).
- Organizations: your business customers—e.g. travel agencies. Each agency is an organization. You create organizations and give each one access to the app and to a set of roles (role groups) they can assign to their members.
- Members: the agency’s staff (e.g. agents, managers). They log in to your platform as members of that organization. The agency admin assigns them roles (e.g. Booking agent or Viewer) from the role groups you allowed for that organization.
In Mosaic, a user is the underlying identity record, while a member is that user in the context of a specific organization. The same user can be a member of multiple organizations.
In this example, travelers who book directly as individual customers are B2C users, while agency staff access the platform as B2B members of their organization. See B2C identity management.
1. Learn the model
See Main concepts — applications, organizations, members, optional parent–child hierarchy, app-level versus organization-level roles, and how the Admin Portal differs from the Organization admin portal.
2. Implement in order
See Setup overview — numbered path from B2B application settings and authentication through Define app roles, Create app role groups, Create organizations, Configure org roles & auth, and Set members. Each step links to its detail page.