What is our recommendation to distinguish OOTB apps (ex: Develop) inside the Gate app

[brionmario]

Problem

If users choose to use Thunder's Gate app to sign in to their own applications, we need a reliable way to differentiate User Created Apps from out-of-the-box (OOTB) apps like Develop.

Why is this needed

This distinction is necessary because the layout, theming, and branding should differ between the two:

• OOTB apps (e.g., Develop) should follow Thunder’s native theme and branding.
• User apps should have a minimal, neutral theme by default — with no Thunder branding, slogans, or visuals.
  Instead, they should display ACME (or tenant-specific) logos and styling to create a white-label-friendly experience.

What are your thoughts? @darshanasbg @senthalan @ThaminduDilshan

[ThaminduDilshan]

OOTB apps (e.g., Develop) should follow Thunder’s native theme and branding.

It is a valid use case to allow branding for these apps too right? But I agree we need to separate them out from rest of the apps.

--
Can we achieve this usecase if we introduce a label to the apps? But somehow we need to make it only configurable for the system apps.

Alternatively, as the names for these system apps are fixed, we can enable this through a deployment.yaml config as well.

[brionmario]

It is a valid use case to allow branding for these apps too right?

Yes. That's why this becomes tricky. Otherwise we could have determined whether it's a business app if a branding exists.

[darshanasbg]

We would need to distinguish the system apps, but I don't think that is required to decide theming of those apps..

Gate app serves the login, registration pages. So we should let those pages to fully white label regardless whether its a system app login or user app login.

For example lets consider following three scenarios:

1. Some organization use, Thunder as the IDP for EIAM use case.

• Then we will have set of applications created in Thunder targeting the employees.
• So Gate app serves login pages for these employee applications, include the develop app (because that's also used by the employees of that organization).
• So branding we have for the login pages of the gate app should be same for the both user apps and the system apps (like the develop app).

2. Some organization use, Thunder as the IDP for CIAM use case.

• Then we will have set of (user) applications created in Thunder targeting the customers. So Gate app serves login pages for two different types of users: customers & employees.
• Since we support different branding types for different applications, we can still have one type of branding for customer apps and another type of branding for the develop app (or system apps).

3. Some organization use, Thunder as the IDP for both EIAM & CIAM.

• Then we will have one set of (user) applications created in Thunder targeting the customers another set targeting employees.
• Similar to the scenario 2, Gate app serves login pages for two different types of users: customers & employees.
• Since we support different branding types for different applications, we can still have one type of branding for customer apps and another type of branding for the employee apps including develop app (or system apps).

Would you see an issue with this approach?