The Server Config page in the Admin console is where you adjust how the running server behaves, configure outgoing email, review licensing, and apply a new license. It requires the Server Config global permission.
Changes to the General and SMTP sections are applied and saved to disk when you click Save.
| Setting | Description |
|---|---|
| Server URL | The public-facing URL of this server. Used when building links in emails and redirects. |
| Support Email | The address shown to users for support enquiries. |
| Session Timeout (hours) | How long a user session remains valid before the user must log in again. |
| New users created as disabled | When enabled, newly registered accounts are disabled until an administrator manually approves them. Useful for closed deployments. |
| Only admins can create organisations | When enabled, regular users cannot create organisations — only administrators can. |
udServer sends email for invitations and notifications through an SMTP server. Enable SMTP and provide:
| Setting | Description |
|---|---|
| SMTP Server | Hostname or IP of the outgoing mail server. |
| From Address | The email address used as the sender. |
| Use TLS | Whether to connect using TLS. |
| Username | SMTP authentication username. Leave blank to clear stored credentials. |
| Password | SMTP authentication password. Leave blank when saving to keep the existing password unchanged. |
The SMTP password is never returned by the server, so the field is always shown blank. Entering a value replaces the stored password; leaving it blank keeps the current one. Clearing the Username clears both the username and password.
This read-only section reports the current state of the server:
If the active license includes domain or pool entitlements, they are listed here with each domain's session limit and whether it is a premium domain. This section is hidden when the license defines no domains.
You can apply or update the server's license directly from this page — there is no need for filesystem access to the host.
The license is validated against the running server (contacting the licensing server for online licenses), applied immediately, and persisted so it survives a restart. The Server Info and Licensed Domains sections refresh to reflect the new entitlements.
If the license is rejected, check that the JSON is complete and valid and that the server can reach the licensing server for online licenses.
Applying a license is recorded in the System Log as a
LicenseAppliedevent.
For the underlying API used by this page, see /_config/full, /_config/modify, and /_config/license in the developer guide.