Configure the email sending (SMTP)
Open Hamilton Meeting, click Administration, then "SMTP configuration" in the Configuration section.
Enter your mail relay settings: server, port, authentication, sender address.
Validate, then send yourself a test notification (for example by making a test booking with the email checkbox ticked).
Without a valid SMTP configuration, no notification, reminder or validation email leaves the application.
Configure the Hamilton API connection
In the Configuration section, click "Hamilton API configuration".
Enter the API endpoint and credentials provided with your platform, and validate.
The Hamilton API powers the companion services (mobile access, modern integrations); its settings normally change only when your platform moves.
Configure the web services and databases
Two technical screens define how the application reaches its data services:
"Web services database configuration": the connection used by the web services layer.
"Web service configuration": the endpoints and access settings of the application's web services.
These settings are established at installation. Change them only during infrastructure operations, with a backup of the previous values.
Configure the scheduled service (ServiceTache)
In the Configuration section, click "ServiceTache configuration".
The list holds the URLs the background scheduler calls (imports, purges, synchronizations). Add or edit entries to match your deployment, and remove obsolete ones.
The scheduler executes the tasks defined in "Import data and schedule automated tasks" — both must be consistent.
Good to know
Single sign-on (SSO) configuration is handled with your Hamilton contact and is not covered here.
After any change here, test the affected chain end to end: an email, an API call, a scheduled task run.
Keep credentials in your organization's secret store; the screens display them for configuration, not for sharing.