This guide explains the retention and custody options that appear in Namirial Notify site and user configuration tabs. Use it when you need to understand how online retention, notarial retention, access control, and long-term archive storage are represented in the admin UI.
Configuration defaults apply to web-created transactions. API and web service submissions must send their own values explicitly.
Archiving and custody-related options can appear in both:
- Organization > Configuration service tabs, where values become site-wide defaults.
- Profile > Configuration service tabs, where values become defaults for one user.
They can appear under service tabs such as EviPost, EviMail, EviSMS, EviNotice, and EviSign.
Custody option groups can include:
- Universal message access control - controls how generated evidence can be accessed.
- Default online retention period - default period, in years, during which generated evidence is kept online.
- Default notarial retention period - when enabled, a notarial retention period can be applied so evidence is kept in safe custody.
- LTA Storage - when available, evidence can be archived in LTA service, shown in the UI as Namirial Archive. See What is Namirial Archive for how this long-term archive works.
Exact availability depends on the service, tenant configuration, and enabled modules.
Namirial Notify can apply retention and custody defaults at different levels:
- Site settings define organization-wide defaults.
- User profile settings can define per-user defaults.
- Transaction settings selected while creating a communication apply only to that transaction.
When the same option exists at more than one level, the transaction value normally takes precedence over the user default, and the user default takes precedence over the site default.
Before changing custody or archiving defaults, confirm:
- the service is enabled for the site
- the selected retention behaviour matches the organization's retention policy
- LTA storage is available before enabling an LTA-related default
- changing the default should affect future web-created transactions
- existing evidence retention is not assumed to change retroactively
- API or web service integrations are not relying on these web defaults
Administrators understand where retention and custody defaults are configured and can decide whether a change belongs at organization level, user level, or transaction level.