Multi-portal, multi-app and multi-tenancy address business entry points, application boundaries and customer isolation. They can be combined: organize several business areas within one app as portals, split apps when data, configuration and versions need separate management, and create an independent app for each tenant when serving multiple customers.
Multi-portal: one app, multiple business entry points
An app can offer portals for reagent, equipment and asset management. Each portal provides an entry point to its business area, shares the app's authentication and runtime, and upgrades with the app.
A portal is an entry point within an app, not an independent app or a tenant isolation boundary. Permissions still control access to business data. An app can use multiple database connections; portals do not have to store all their data in one database. Multi-portal management, the portal generator and the multi-portal app template are commercial capabilities.
Start with Create a multi-portal app, then follow the guides for portal development, access and management.
Multi-app: independent operation, unified access
Customer, order and warehouse management can run as separate apps. Each app manages its own data, configuration and version, and can upgrade on its own schedule.
The platform is itself an app. Once centralized authentication is integrated, users with a valid platform session can switch between apps they are authorized to access without signing in again. A shared login does not grant access to every app or automatically connect their business data. Cross-app business operations need appropriate interfaces.
Independent apps do not require separate servers. Choose a deployment approach according to resource and isolation needs.
Multi-tenancy: an independent app for each tenant
This approach implements multi-tenancy with multiple apps: each customer or organization gets an independent app with its own data, configuration and upgrade schedule. Each tenant app can also contain portals for sales, inventory and finance management.
Tenant A · Independent App
Tenant B · Independent App
Tenant C · Independent App
Use the same template for tenants with the same business needs, or different templates for different needs. Apps created from the same template remain independent instances that can be configured and upgraded separately.