Aller au contenu
Website
Free simulator Append-only audit log Fictitious data

Client Portal via Magic Link: have a choice of materials or a change order validated, with an audit trail

Create a choice sheet or a daywork voucher in a few seconds, send a link without a password, then see what the client sees: the live impact on the budget, a signature with a finger or a mouse, and a time-stamped validation certificate as a PDF.

Try the simulator

Demonstration. All amounts, site names and company names are fictitious examples, and the images are generated diagrams. Enter a fictitious name when you play the client: the IP address and the browser are recorded in the log (see “Personal data” below).

1 Company side: prepare the sheet and generate the link

Proposed options example amounts

Option 1 is the one in the contract (zero supplement). Supplements are in CHF HT; a reduction is written with a minus sign.

The link is signed and expires at the chosen time; you will be able to revoke it.

How the magic link works

  1. A random 256-bit token is created for each link. The server keeps only its SHA-256 fingerprint: even with the database, the link cannot be reconstructed.
  2. The address is signed with the application key (URL::temporarySignedRoute). Any modification of the address, or the exchange of one token for another, is refused; the expiry is in the signature.
  3. Every action is protected : CSRF token for submissions, rate limiting by IP address and by action, code attempts limited to 5, a single decision per link, revocation possible by the company.
  4. The document is frozen from creation: its SHA-256 fingerprint is calculated on a canonical form (amounts in cents) and carried into each log entry.

What is recorded in the audit log

On each consultation, validation or refusal, an entry is added to the log (table client_approval_logs). It will never be modified or deleted by the application.

ip_address
IP address seen by the server (and the X-Forwarded-For header as received, for information).
user_agent
The browser and the system, as declared.
timestamp_utc
UTC date and time of the server clock, never that of the browser.
document_hash_sha256
Fingerprint of the document as it was presented (options, amounts, budget).
client_name
The name entered by the client — declared, not verified.
signature_data
The signature trace (vector) or the proof that a one-time code was checked (never the code itself).
financial_impact_chf
The impact of the decision on the budget, in CHF excluding taxes.
prev_hash / entry_hash
Chaining: each entry contains the fingerprint of the previous one, and its own.

Database rules prohibit the modification and deletion of entries and refuse any insertion that does not exactly extend the chain. A check command (php artisan portail-client:verifier) re-reads the entire chain and reports the slightest inconsistency.

What this simulator is not

  • Not a qualified electronic signature. It records a simple electronic validation, time-stamped and traceable. It is neither a qualified electronic signature nor a qualified time stamp within the meaning of the Federal Act on Electronic Signatures (SCSE); in Swiss law, only a qualified signature combined with a qualified time stamp is equated with a handwritten signature (Art. 14 para. 2bis CO).
  • No verified identity. The name is the one the person entered.
  • Not tamper-proof. The chain makes any alteration detectable; it does not prevent someone who controls the database and the code from rebuilding it. The fingerprint given in the PDF certificate serves as an external anchor.
  • Not legal advice. The probative value of such a record is a matter for the judge's assessment. For important stakes, or if the law or the contract requires a qualified written form, have your process validated by a lawyer.

Personal data (LPD)

Under the Federal Act on Data Protection (LPD, RS 235.1), we inform you of what this simulator collects and why.

  • Data: IP address, browser (user agent), name entered, signature trace or code proof, date and time, fingerprints.
  • Purpose: establish the traceability of the simulated validation and allow its verification.
  • Controller: Art Construction (contact details in the legal notice).
  • Retention: target of 90 days for the demonstration data. Since the log is append-only, deletion goes through an administrative procedure, not a button.
  • Your rights: access, rectification, erasure, via the contact in the legal notice. Enter a fictitious name.

Verify a certificate

Paste the “This entry” fingerprint printed on the PDF certificate. The check compares the fingerprint with the log and re-reads the entire chain; it displays no personal data.

Frequently asked questions

Is the magic link safe?

The link contains a randomly drawn token (256 bits) that the server does not keep in clear, it is signed with the application's key (any change to the address invalidates it) and it expires at the chosen time. The company can also revoke it. Like any link without a password, it opens the page to anyone who holds it: send it through a reliable channel and choose a short duration.

Does this validation have the value of a handwritten signature?

This is not established. The simulator records a simple electronic validation, time-stamped and traceable, in the name declared by the person. It is neither a qualified electronic signature nor a qualified time stamp within the meaning of the Electronic Signature Act (SCSE), the only ones equated by law with a handwritten signature. Its evidential weight is for the judge to assess: for high stakes or a qualified written form required by law or by the contract, have your process validated by a lawyer.

What does the audit log contain?

For each viewing, validation or refusal: IP address, browser, UTC date and time (server clock), SHA-256 fingerprint of the document presented, name entered, option chosen, drawn signature or proof of the one-time code, financial impact in CHF HT (excl. VAT), and the fingerprint of the previous entry.

Is the log really tamper-proof?

It is append-only: database rules forbid modification and deletion, and each entry contains the fingerprint of the previous one, which makes any tampering detectable by a check of the chain. It is not tamper-proof for all that: someone who controls both the database and the code could rebuild it. That is why the PDF certificate given to the client carries the entry's fingerprint (external anchoring) and a page allows it to be checked.

What personal data is collected (LPD)?

IP address, browser, name entered, signature trace or proof of the code, date and time, to establish the traceability of the validation. Enter a fictitious name in this demonstration. Retention target: 90 days; since the log is append-only, deletion is an administrative procedure. Rights of access, rectification and erasure: via the contact in the legal notice.

Are the amounts and photos real?

No. The amounts, site names and company names are demonstration examples, and the images are generated diagrams. No real data is taken over or sent to Soumission.

Where is the one-time code sent?

Nowhere: the demonstration asks for neither an e-mail address nor a phone number. The code is therefore shown on screen. In real operation, it would be sent through a channel separate from the link (e-mail or SMS), which this demonstration does not show.

Move from calculation to full management

Keep your references at hand, then automate them in your quotes, bids and final statements.

📥 Ready-to-use pack · free

Download the document

The file is displayed on screen right away and we also send it to you by e-mail.

Your address is used to send you this file. See our privacy policy.