Is it possible to combine two separate Mendix apps into one project, where screen visibility is controlled by the calling external application?

0
Hi everyone,I have two separate Mendix apps, both still in development and not yet deployed. Both connect to an Oracle database via the External Database Connector. One app is called from an external system using SSO, the other is called from a different external system as an extension.The requirement is to have both in a single Mendix project with a single deployment. The tricky part is that screen visibility needs to be driven by which external system is calling — users of one external system should only see that app's screens and vice versa.Is this possible in Mendix? If yes, what would be the recommended approach?Thanks in advance!
asked
1 answers
0

In our case, we handled a similar requirement by keeping the applications separate instead of merging them into one Mendix project.

We have one external/portal application acting as the parent application. From there, users can navigate to different Mendix child applications using Deep Links.

The flow is:

External System

→ Parent/Portal Application (SSO login)

→ User clicks the required application

→ Deep Link redirects to Child App A / Child App B

Each child application maintains its own:

  • security model
  • modules
  • deployment lifecycle
  • business logic

The parent application only works as an entry point/navigation layer.

If you need both applications under one deployment, then you can merge them and control visibility using roles and conditions, but for independent applications the parent + child app approach with Deep Links is cleaner and easier to maintain.

Kindly mark this as the accepted answer if it helps.

answered