Skip to content

User profile settings

This guide explains the settings available in the profile area of a single Namirial Notify user account. Use it when you need to review personal profile data, configure per-user web form defaults, or find the related profile tools for password changes, activity, contacts, and registered email addresses.

In most tenants, users manage their own profile settings. Depending on your permissions and tenant configuration, an admin may also be able to review or assist with these settings for another user.

The defaults under Configuration are used in the web forms for creating EviMail, EviSMS, EviNotice, EviSign, or EviPost transactions. API and web service submissions must send their own values explicitly.


Prerequisites

  • you are signed in to Namirial Notify
  • you can access the profile area for the account you want to review
  • the relevant services are enabled on the site if you need to configure service-specific defaults

How profile settings relate to site settings

Namirial Notify can apply sending defaults at different levels:

  1. Site settings define organization-level data and site-wide defaults.
  2. User profile settings define personal data and web form defaults for one user.
  3. Transaction settings selected while creating a communication apply only to that transaction.

When a user creates a transaction in the web application, the form can start from the configured defaults. The user can still change the available options before sending, unless the option is restricted by the site configuration or by the user's permissions.

For site-wide organization data, service defaults, and password policies, see Site settings.


Open profile settings

  1. Sign in to Namirial Notify.
  2. If you are editing your own account, open the menu in the top-right area where the user or site name is displayed.
  3. Open the profile or user details area.
  4. If your tenant allows admins to inspect another user's profile settings, open that user's details first and then review the available profile sections.
  5. Select the section you need to edit.

Profile sections include Data, Configuration, Password Change, Activity, Contacts, and Emails. Under Configuration, you can access General, EviMail, EviSMS, EviNotice, EviSign, and EviPost.

Menu labels can vary slightly by tenant and UI version. Legacy screens commonly expose these settings from the user details area.


Personal data

The Data profile section is divided into two areas: Account information and My Data.

Account information

The Account information area shows account-level details such as:

  • registration date
  • company
  • Tel / SMS origin Alpha
  • user email

These fields identify the account and its site context. Depending on the tenant configuration, they may be informational rather than directly editable from the profile page.

My Data

The My Data area lets a user or administrator review and update personal data such as:

  • name
  • surnames
  • legal ID kind
  • identity
  • phone number
  • language
  • time zone

The exact fields available can depend on the tenant configuration and on the user's permissions.

To update personal data:

  1. Open the profile details area.
  2. Edit the available fields.
  3. Select the save action.
  4. Confirm that the updated values are shown in the profile.

Changes made here apply to that user account only.

Profile Data section showing account information and My Data fields for a user account


User configuration defaults

The Configuration area defines default behaviour for the user's web sending forms. These defaults help users avoid setting the same options manually every time they create a communication.

Each configuration tab can show a note explaining that organization-level values define the defaults for users. Where the UI shows an Edit action on a disabled parameter, selecting it lets the user configure a profile-specific value instead of using the inherited default.

To update configuration defaults:

  1. Open the Configuration section in the profile area.
  2. Select the service tab you want to configure.
  3. Change the default values you want the web form to prefill.
  4. Select the save action.
  5. Create a new web-based transaction later if you need to verify that the new defaults are being proposed correctly.

Profile configuration tabs are organized as follows:

  • General - default SMTP message type and notices for new users joining the site, where available.
  • EviMail - sending and certification defaults, cost centres, commitment options, custody options, notifications, and push notifications.
  • EviSMS - sending and certification defaults, custody options, cost centres, delivery channel priority, notifications, and push notifications.
  • EviNotice - language-specific notification defaults, signing and acknowledgement settings, commitment options, custody options, reminders, delivery channels, notifications, push notifications, and PIN channel attempts.
  • EviSign - language-specific signature defaults, signing process settings, information texts, document and attachment options, commitment options, custody options, geolocation, reminders, notifications, interested-party notifications, and push notifications.
  • EviPost - sending and certification defaults, cost centres, custody options, and notifications.

Reminder schedules for EviNotice and EviSign use a structured format with values such as start, repeat, days, hours, stop, maximum reminders, and time zone. The UI also references ISO 8601 duration notation for period values.

EviSign geolocation defaults can usually be Disabled, Enabled, or Compulsory.

For archiving, retention, and custody concepts that appear in these tabs, see Archiving.


Profile tools documented elsewhere

Some profile sections have dedicated guides:

  • Password Change - see Password management for the signed-in user's password-change form and site password policies.
  • Activity - see User activity for the activity table, columns, and filter options.
  • Contacts - see Contacts for creating, importing, searching, and filtering contacts.

Email addresses

The Emails profile section lists the email addresses registered for the user account. The list can show information such as the email address, display name, creation date, and whether the address is obsolete.

The email-address grid can include fields such as:

  • Email address
  • Name
  • Creation
  • Obsolete

Depending on the tenant and the address status, row actions can include options such as viewing details or deleting the address.

Profile Emails section showing the registered email-address table and add action

Register an email address

To add a new email address:

  1. Open the Emails section in the profile area.
  2. Select the add action.
  3. Enter the display name.
  4. Enter the email address.
  5. Select Send PIN.
  6. Follow the on-screen verification flow.
  7. Confirm that the address appears in the list with the expected status.

Register email screen showing the display name and email address fields before sending the verification PIN

Before registering an email address, keep in mind that:

  • the user must have access to the email address, because Namirial Notify sends a PIN code to verify authenticity
  • the email address can be used for sending notifications only if the site administrator has configured the corresponding domain and completed the required DNS changes
  • if the domain is unsupported or not ready for sending, the platform rejects the change instead of completing it

For the domain-verification process, see Forwarding domains.


What to check before changing profile settings

Before changing profile settings, confirm that:

  • you are editing the correct user profile
  • if you are changing configuration defaults, the relevant service is enabled for the site
  • if you are changing configuration defaults, the setting should apply to future web-created transactions for this user
  • the expected behaviour is not already controlled by site settings, user permissions, or a transaction-specific choice
  • if you are changing contacts or email addresses, the change belongs in this user profile rather than in an organization-level address book or domain configuration
  • API or web service integrations are not relying on profile configuration defaults, because they must send their own values

Expected result

You can review and maintain the personal profile data, user-specific web form defaults, and registered email addresses for the selected account. Focused profile tasks such as password changes, activity review, and contact management are documented in their dedicated guides.