The System Settings tab allows Administrators to set Locations, Client Access Option, and PNG Cache Management.
.png?sv=2026-02-06&spr=https&st=2026-10-10T06%3A26%3A31Z&se=2026-10-10T06%3A39%3A31Z&sr=c&sp=r&sig=5WuRx1GuLOpIaGS9MolCCymTeEwMcY%2FNL5mpUcZqBko%3D)
Make edits to the fields detailed in the following sections, then click Save to save any changes.
Locations
Use the fields listed here to set the location path (with respect to the web server) for the following:
Correspondence
Download Documents
PAL Reading Room
Original Document Location
PNG Cache Location
Client Access Option
Select the Enable XAML Client for Scan option to enable the XAML client for scanning and correspondence.
For Correspondence Templates, there are options to:
Use XAML Client: Use MS-Word based XAML editor
Use Legacy Upload/Download: Download and upload templates in legacy format for editing
Use Rich Text Editor: Edit templates using the Rich Text Editor
Client Secret Expiry Date
When the Authentication Mode is set to Microsoft 365 Email, the Email Domain Credentials table is displayed. Record the expiry date of the Azure AD client secret in the Secret Expiry column of each credential row. A separate expiry date is held for every configured email domain, and the value is required before the configuration can be saved.
An advisory note is displayed adjacent to the field:
NOTE: Please ensure the expiry date entered here matches the Client Secret expiry date in your Microsoft Azure AD configuration.
Setting the Client Secret Expiry Date
1. Navigate to Administration > System Administration > System Settings.
2. In the Mail Server Address section, confirm that the Authentication Mode is set to Microsoft 365 Email.
3. In the Email Domain Credentials table, select the Secret Expiry date for each configured email domain.
4. Click Save.
NOTE: A past date cannot be selected in the Secret Expiry field. The Email Domain Credentials table, including the Secret Expiry column, is displayed only when the Authentication Mode is set to Microsoft 365 Email.
Clearing the Expiry Date
If a Client Secret Expiry Date was previously saved and the administrator clears the field and saves, all expiry tracking is removed and no further notification emails are sent.
Automated Expiry Notification Emails
When a valid future expiry date is saved, the system arms an automated notification scheduler. The scheduler sends warning emails to all admin-role users at the following intervals:
Notification Trigger | Email Type |
|---|---|
30 days before expiry | Warning email |
15 days before expiry | Warning email |
7 days before expiry | Warning email |
1 day after expiry | Urgent expiry email |
Warning emails include the expiry date, the affected email domain, and the number of days remaining.
Each configured email domain is tracked separately, so domains with different client secret expiry dates generate notifications on different days.
The urgent expiry email is sent on the first day after the Client Secret has expired.
No further notification emails are sent after the post-expiry notification.
NOTE: All notification emails (both before and after expiry) are logged under the Email Log of the application.
Email Templates
The Client Secret expiry notification scheduler sends two email templates. Both templates use the following merge fields:
Domain name — the email domain affected by the expiry.
Expiry date — the Secret Expiry date entered for that domain in the Email Domain Credentials table.
Days remaining — the number of whole days between the current date and the expiry date (warning emails only).
System name — the sending application name used in the email signature.
Warning Email — 30, 15, and 7 Days Before Expiry
Post-Expiry Notification Email — 1 Day After Expiry
PNG Cache Management
Use these fields to set the PNG Cache Limit (in GB). There is also the option to Delete PNG Cache if the folder has not been access in more than, which will delete the PNG cache if not accessed in the set number of days.
Request Recycle Bin
Use the Request Recycle Bin option to determine the number of days that deleted requests will be held in the Recycle Bin before being permanently deleted. Requests can be held in the Recycle Bin from 1 to 365 days, and you cannot enter a value of "0" in this field.
NOTE: Requests in the Recycle Bin are not included in search results or system reports.