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.
I see. So you want to enable signups for certain applications, and disable it for others.
This is currently not available through the connection settings. Further, what would stop a user from simply signing up in one of the other apps, then going back and logging in to the base app?
I think the more typical design would be to have a connection that blocks all signups, and would be for, say, admin only, or something of that nature.
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.
Create a Pre User Registration action that checks the event.client and throws an exception if it was hit by the base application.
To only allow log-in for the admin on the base application:
Create a login action that checks the role and throws an exception if the user is not an admin
Branding different applications:
Using page templates for branding different applications log in / register. (Tenants not used due to the need for shared authentication between the apps - Tenants only for different environments)
Organizations:
Consider looking into Organizations for big multi-application set-ups