Each Namirial Notify site can be independently configured to control default service behavior, user experience, and enabled capabilities. Site-level settings apply to all users on the site unless overridden at the user or request level.
This page covers the site-level settings accessible through the site administration interface. For the process of creating a site, see Create and manage customer sites.
The site administration screen allows a site administrator to update the organization details:
- Organization name
- Tax identification (VAT number)
- Telephone
- Address, city, postcode, region, country
These fields are used for billing records and display purposes, and may appear in service records depending on your configuration.
Each enabled service has a section in the site settings screen where the administrator defines the default behavior for that service. These defaults apply when no user-level or send-time override is specified.
- Sending and certification options
- Acceptance and rejection options
- Custody options
- Event notification options
- Sending and certification options
- Acceptance and rejection options
- Custody options
- Event notification options
- Sending and certification options
- Signature process (notification access method)
- Acceptance and rejection options
- Custody options
- Event notification options
- Sending and certification options
- Signature process settings:
- Default signature method
- Whether to sign at time of acknowledgement or at end of process
- Navigation bar visibility during signing
- Whether signers may substitute another person
- CAPTCHA enablement
- Additional questions JSON
- Signature position JSON
- Delegated signature
- WhatsApp PIN delivery policy (disabled / instead of SMS / retries only)
- Default text for request, reminder, start page, signed notification, rejection notification, and expiry emails
- End URL (destination after signing is completed)
- Documents attached to final notification and to request email
- Differentiated acceptance of annexes
- Number of signing reminders
- Additional terms text
- Acceptance and rejection options
- Custody options
- Additional fields
- Geolocation:
Disabled— geolocation is not collectedEnabled— permission is requested; process continues if deniedCompulsory— permission is required; process stops if denied
- Event and push notification options for issuer and interested parties
Available sub-options may vary by deployment. Contact your Namirial representative for the full list of supported signature process settings.
- Sending and certification options
- Custody options
- Additional fields
- Event notification options
Site administrators can define the password policy for all users on the site:
- Minimum password length
- Password format and regular expression
- Password expiry period
- Number of previous passwords that cannot be reused
- Verification against common passwords or user personal data
Feature flags are configured when creating or updating a site. They control access to advanced or optional capabilities. See the full flag reference in Create and manage customer sites — Feature flags.
Key flags affecting site behavior:
| Flag | Effect |
|---|---|
SecondFactorAuthentication | Requires two-factor authentication for all site users |
NewUi | Enables the updated web interface for the site |
DefaultLanguageLegacy | Forces affidavits and notifications to use the legacy es language default |
CertificationLevelsLegacy | Allows use of legacy certification level identifiers |
Sites that use Qualified Electronic Registered Delivery Service (QERDS) certification levels must have QERDS profiles and, if applicable, identity tenant references configured.
- QERDS profiles specify which QERDS provider profiles the site may use. Each value must contain
::; two-part and three-part values such asProvider::ProfileNameandProvider::ProfileName::Customerare valid when configured for the identity provider. - QERDS identity tenants bind identity verification tenants to specific certification levels (e.g.
tenantId@qerds:es).
Both fields accept semicolon-separated lists. Configure QERDS profiles for QERDS enrollment flows, and configure QERDS identity tenants when tenant-specific QERDS identity validation is used.
Site administrators can register and verify sender email domains from the domain management screen (accessed via the Organization top menu). Only domains in a send-enabled state can be used for EviMail sender addresses.
Domain statuses:
| Status | Meaning |
|---|---|
Active | DNS records confirmed; domain is active and can be used for sending |
New | Domain verification is in progress; may be shown as Pending in the UI |
Failed | Verification attempt failed |
Disabled | Domain is disabled and cannot be used for sending |
Deleting | Domain is pending removal; may be shown as Pending removal in the UI |
Legacy | Domain was active before the current verification system and can be used for sending |
Only send-enabled domain states can be used for sender addresses.
For DNS configuration requirements, see Forwarding domains and email authentication.
Users with sender permissions can register and verify individual email addresses as sending identities. Address registration requires email verification via a PIN sent to the address being registered. Sender address registration is accepted only when the associated domain can send.
Sender addresses are managed from the profile menu under Emails.