How to build a dynamic, decoupled Landing Page for applications without design-time access to application groups?

Hi everyone,

I am looking for architectural and design recommendations for building a common Application Landing Page in Appian.

The Setup:
I am building this landing page within a separate, standalone "Common/Core" application. Because this is a centralized hub, I, as the developer, do not have design-time access to the downstream application groups. Furthermore, when new applications are deployed in the future, this landing page needs to automatically accommodate them without requiring code changes.

Requirement:
The landing page must display a dynamic list of applications. Crucially, an application should only be visible to the logged-in user if they belong to that specific application's personas/security groups. Because I cannot hardcode or directly reference these group objects, the solution must be fully data-driven or dynamically resolved.

Questions for the community:

1. What is the best-practice design pattern for this? Should we use a database-driven approach where applications register their group UUIDs in a metadata table, and then evaluate membership dynamically?
2. How can we efficiently check group membership at runtime when the group constants or objects are not local to the common application? (e.g., handling pointers or UUID strings safely in expressions like a!isusermemberofgroup).
3. If you have designed a similar plug-and-play architecture for an Appian portal or landing hub, what pitfalls or performance bottlenecks should I watch out for?