Setting System Configurations

When deploying and operating a production-grade instance of Sisense on Linux, getting system configuration right is fundamental to ensuring reliability, security, correct behavior and seamless integration into your infrastructure. This includes four inter-related concerns, from global system settings to email notifications and domain aliasing, that administrators should configure carefully to tailor Sisense to their environment:

• System Configuration via the Configuration Manager — how to access and use the built-in configuration interface to control web-server settings (SSL, proxy/base URL, security headers), logging levels, audit logging, content-security policy, export options, and other core system behavior.

• Email Infrastructure: Custom Email Servers — how to replace the default email service (which by default uses a hosted provider) with your own SMTP server, giving you full control over email delivery for alerts, reports, password resets, and other notifications.

• Email Settings Configuration — how to enable or disable system-wide email sending, choose which kinds of emails should be sent (e.g. scheduled reports, invitations, share notifications), and test your configuration to make sure alerts and notifications work as expected.

• Updating the DNS Alias for Sisense — how to configure (or update) the custom domain name / alias used by the Sisense web server; this is important when you change your server’s IP or want dashboards, emails, and links to reflect a branded, stable domain rather than an IP address.

Taken together, these configuration areas define how Sisense behaves: how it communicates (web server settings, domain alias), how it alerts users (email settings), how it logs and secures operations (logging, audit, security headers), and how it integrates with your infrastructure (custom SMTP, custom domain, proxy/base-URL).