There isn’t a turn-key way to customize per application like there is for the global branding settings. Some customers will use separate tenants for their different branding, or there are some workarounds for the branding using page templates and application variables listed there.
It sounds like organizations would probably be a good fit here. It’s certainly worth looking at:
“You can disable signups for database connections in their settings.”
Would this not disable signups for database connections over all the applications within the tenant? We need to disable this for only some of the applications within the tenant.
“Some customers will use separate tenants for their different branding”
As far as I’m aware when using different tenants, we will lose sso capabilities over the different applications (logged into A, and then automatically logged in B, etc). Unless I am missing something?
We will definitely look into the other suggestions you made.
For more context on the base application:
The base application (accessed through the other applications) could be used by any user and an admin.
Basically, it is a management app “extension” to all the other applications where there is admin functionality and it is a place where a user can manage their profile etc.
We would want a normal user to sign up only through the other applications.
Only the admin should be able to log in directly to the base application. - but if for any reason a user gets to the base application’s admin login without having a profile - they should not be able to sign up.
You should be able to set up a Pre User Registration Flow Action and block registrations based on the event.client param and spits an error saying ‘signups are disabled for this client’ or something to that effect.