Configurable base URL for system-email links
Summary: Vitalii Veremeiev suggests adding a configuration property that allows defining a separate base URL for links in system-generated emails, independent of the Web Server Proxy URL used for multi-domain embedding. This would help ensure that activation, invitation, and other important email links are fully qualified and publicly accessible, improving accessibility and functionality across different features like password resets and scheduled reports.
For multi-domain embedding, a relative Web Server Proxy URL may be required (for example, /sisense) to support SDK and iframe embedding under different customer domains.
In this setup, the URL used for embedding and the URL that should be included in system-generated emails can be different. Emails such as user activation and invitation emails should be able to use a fully qualified, publicly reachable URL, for example:
https://app.example.com/sisense/app/...
Requested Capability
Introduce a configuration property that defines the base URL for links generated in system emails, independently of the Web Server Proxy URL.
This would allow deployments to:
Keep a relative Web Server Proxy URL for multi-domain SDK and iframe embedding.
Define a separate, publicly reachable base URL for system email links.
Ensure activation and invitation links are generated as fully qualified URLs.
It would also be useful to consider whether this configuration could be applied more broadly to other features that generate absolute links, such as password resets, scheduled reports, exports, and share links.
