Tenant and OEM

Tenants and OEM are often asked together, but they solve different problems:

• Tenant model handles data, space, and resource isolation plus platform-to-tenant delivery
• OEM handles branding, copy, and portal experience customization

If those concepts get mixed up, teams often end up enabling the wrong feature for the real requirement.

Can the platform give its own dashboards directly to tenants for editing?

Not for direct editing.

The default principle is: platform-owned resources stay owned by the platform, and tenants should not modify the platform's original resources directly. That includes both platform data and platform-built reports.

If the real requirement is "the platform provides a template and the tenant continues from there," the safer pattern is:

1. The platform shares the app with the tenant
2. Export or copy is allowed as needed
3. The tenant continues analysis inside its own resource space

That lets tenants work independently without mutating the platform's original assets.

Why did the platform share a resource to a tenant, but regular tenant users still cannot see it?

Because the platform grants to the tenant, not automatically to every regular user inside that tenant.

The default flow is:

1. The platform shares the resource to the tenant
2. The tenant admin enters the tenant space
3. The tenant admin decides whether to grant it further to regular tenant users

This keeps governance boundaries intact on both sides.

Can the tenant model replace OEM?

No.

If your goal is:

• change logo, fonts, colors, button visibility, or copy: this is closer to OEM / Global CSS / Global JS
• provide isolated spaces, isolated resources, and isolated admins for different customers: this is closer to tenant management

In short, OEM is about presentation and branding, while tenant mode is about resource boundaries and delivery structure.

Why do custom fonts fail in OEM scenarios?

A very common reason is a protocol mismatch.

If HENGSHI runs on https but the font URL still uses http, the browser may block it as mixed content. The visible result is simply "the font did not take effect."

So in OEM delivery, once the main site uses HTTPS, external fonts, scripts, and image assets should also use HTTPS.

Is resource sharing between platform and tenant bidirectional?

No. By default it is one-way.

The platform can share connections, data packages, and apps to tenants. Content created by tenants in tenant space stays in tenant space and does not automatically flow back to the platform.

That is also why many "collaborative editing" requests are better solved through "copy template and continue creating," instead of asking both sides to edit the exact same resource.

Further reading:

• Tenant Management
• Global CSS Settings
• Global JS Settings