Namirial
The automatic signature with Namirial — a qualified electronic signature, with a signature purchased per person and allocation done exclusively by support based on the Seal ID
The automatic signature with Namirial uses each person's qualified signature, from the company's Namirial account, and produces a qualified electronic signature. Unlike Sigiliu SSM.ro, each signer needs their own qualified signature, and the allocation is done exclusively by technical support, based on the Seal ID. Each new person requires a ticket.
For the general context, the comparison between providers and the application restrictions, see the automatic signature overview page.
When to choose Namirial
Choose Namirial when the internal procedure or a legal requirement mandates a qualified signature. It is the only automatic variant that produces a qualified signature, with per-person cost and administration.
Prerequisite
The company must hold its own Namirial account and the qualified signatures with the automatic-signing option for the persons concerned. The automatic signature is not a mere setting.
The support request
For activation, the company opens a support ticket that contains:
| Information | Mandatory | Notes |
|---|---|---|
| The desired provider | Yes | Namirial (qualified signature) |
| Confirmation of the accepted signature level | Yes | The client confirms in writing that the qualified signature is the one required for their documents |
| Confirmation of the signers' individual agreements | Yes | The client confirms they have concluded a written agreement with each person concerned, for the respective document types |
| Confirmation of the contracted service | Yes | Proof that the company has a Namirial account and qualified signatures with the automatic-signing option |
| The list of persons | Yes | Full name and the email address exactly as it appears in the contact's record in the platform |
| Seal ID for each person | Yes | Obtained by the company from Namirial, for each individual signer |
| The targeted document types | Recommended | Allows support to flag from the start if a document type is not eligible |
The email must be identical to the one in the contact's record
The email address in the request must be identical to the one in the contact's record in the platform. The Seal ID is cryptographically linked to this address; a wrong address leads to an activation that looks correct but does not sign. Each new person added later requires a separate ticket.
Active account required
The persons who are to sign automatically must have an active account in the platform (they must have accepted the account-creation invitation). Contacts without an account cannot sign automatically.
Configuration done by support
The configuration is done exclusively by the technical support team. The company does not have access to these settings and does not have to perform any technical operation.
Based on the ticket, support carries out:
- the configuration at company level, for a qualified signature;
- the individual activation of each person in the list, based on the Seal ID of their qualified signature.
Upon completion, support confirms in the ticket the configured variant, the signature level (qualified) and the list of activated persons.
Test before mass use
After support's confirmation, test on a single real document, of an eligible type, with the automatic signer in the second position or lower.
The activation is linked to the contact's email
If the email is changed later, manually or through an import, the automatic signature stops and must be reconfigured by support, through a new ticket.
Allocating the automatic signature
It cannot be done by the company administrator. Each person needs their own qualified signature purchased from Namirial and a Seal ID entered by support. For each new signer a ticket is opened, according to The support request.
In this case too, the person's individual agreement must be obtained before opening the ticket.
Do not manually select the profile for non-activated persons
The Namirial - Automatic profile may appear in the "Tip semnatura electronica" list and can be selected manually. Do not select it for employees who have not been activated by support — signing will not work, and the signer will see an error message in the signing screen.
What the company administrator can and cannot do
| Action | Who can do it |
|---|---|
| Allocating the Namirial - Automatic profile to a person (Seal ID) | Only support |
| Enabling the automatic signature at company level | Only support |
| Changing the company's default signature type | Only support |
| Changing an employee's signature type to one already configured | The company administrator |
| Disabling the electronic signature for an employee | The company administrator |
| Filling in the signature title | The company administrator |
Recommendation when building the flow
The automatic signer must be placed after at least one signer who signs manually — otherwise the signature does not start (see Position restriction).
Troubleshooting — Namirial
| Message / symptom | Likely cause | Solution |
|---|---|---|
| On opening the signing screen the message "Semnatura Automata nu este configurata. Va rugam contactati suportul tehnic pentru configurare." appears | The person was assigned the Namirial automatic signature without being activated by support (no Seal ID) | Support ticket to enter the Seal ID, after purchasing the qualified signature from Namirial |
| The company wants to add a new automatic signer | With Namirial a ticket is needed | The client buys the qualified signature, then opens a support ticket |
| It worked for a while, then suddenly stopped | The contact's email address was changed, and the activation was invalidated | Support ticket to reconfigure the person |
| The automatic signer still receives an email invitation | The automatic signature is not actually allocated to that person | Check "Tip semnatura electronica" in the employee's record; where applicable, a support ticket |
For situations common to both variants (ineligible document type, signer in position 1, unfilled fields, etc.), see Troubleshooting — common situations.