Yes, with an added advantage of not needing to configure wildcards and SSL

This input accept a URL to be redirected to after every first instance created by your customer.

It can be useful to accept some survey while the tenant instance is being deployed. We add some basic information about the new instance to the URL also such as tenant id, slug and name.

Go to "Plan -> Advanced Settings -> Shared Settings". Search for "SMTP" and select all the relevant fields as shared.

For the SMTP password, you can mark it as "masked" to prevent it from being directly revealed in tenant settings (please note that this feature is experimental). 

The shared settings will be overridden when the tenant provides their SMTP settings, provided none of the SMTP settings have been marked as "enforced."

You can share leads and other database table content with tenants through “SaaS Settings – Tenant Seed -> Tenant seeding data tables” settings.

“SaaS Settings – Tenant Seed -> Tenant seeding data tables” allows you to select specific database table data that will be included for every new tenant during deployment. The SaaS already designates some crucial tables as default selections, like email templates and currencies.

For instance “Web to Leads” forms with customers, you can simply mark “Web To Lead,” and all your web-to-lead forms will be included during tenant deployment.

To share Leads, mark the "Lead" table same applies to other data. We provide a search box to find any table easily.

Note that, the data created into the table after tenant deployment won’t be available to tenants (except for newly created ones).

You can share your custom fields with tenants through “SaaS Settings – Tenant Seed -> Tenant seeding data tables” settings.

Kindly navigate to "SaaS Settings -> Tenant Seed -> Tenant seeding data tables" and ensure "customfields" option is checked. This option is included in seeding by default and you should find it marked except you have unmark it earlier.

You can use the seach box for faster access.

Note that, the custom field data created into the table after tenant deployment won’t be available to tenants (except for newly created tenants).

“Plan – Advanced Settings – Shared Settings” vs. “Settings – Tenant Seed Settings”

• “Plan -> Advanced Settings -> Shared Settings” is particularly useful when you want to share certain super admin settings, such as SMTP configuration, with all tenants. It’s also handy for sharing module licenses, purchase keys, or other third-party module settings with all tenants.
• “SaaS Settings – Tenant Seed -> Tenant seeding data tables” allows you to select specific database table data that will be included for every new tenant during deployment. The SaaS already designates some crucial tables as default selections, like email templates and currencies. For instance, when you want to share “Web to Leads” forms with customers, you can simply mark “Web To Lead,” and all your web-to-lead forms will be included during tenant deployment. However, forms created after tenant deployment won’t be available to tenants (except for newly created ones).
• “SaaS settings -> Tenant Seed -> Sensitive Options”: By default, the SaaS copies all super admin options and settings (including third-party modules) to the tenant during seeding (deployment), except for settings designated as “Shared settings” in the “Plan.” The SaaS also excludes some settings that appear to pose potential security risks based on their names, such as keys containing “password,” “key,” “secret,” “token,” etc. However, we acknowledge that this may not be the most efficient method, so we’ve introduced a way to control sensitive options through “SaaS Settings” > “Tenant Seed” > “Sensitive Options.” Any options marked here are considered confidential and will not be copied over for the tenants.