> ## Documentation Index
> Fetch the complete documentation index at: https://docs.arya.so/llms.txt
> Use this file to discover all available pages before exploring further.

# Public link and signature

> Share quotes securely, protect with PIN, collect digital signatures.

Every published quote has a **unique public URL** you can send to the customer. Accessible without login, protected by random tokens impossible to guess.

## Sharing

<Tabs>
  <Tab title="Email">
    Click **Send via email** → fill recipients, subject, message. Arya tracks email open and link click.
  </Tab>

  <Tab title="WhatsApp">
    Click **Send via WhatsApp** (if integration active). Pre-filled message with link.
  </Tab>

  <Tab title="Copy URL">
    **Copy link** → paste wherever. Tracking works regardless of channel.
  </Tab>
</Tabs>

## PIN protection

For sensitive quotes (high value, confidential customers):

<Steps>
  <Step title="Enable PIN">
    At publication → **Options → Require PIN**.
  </Step>

  <Step title="Set PIN">
    Arya generates a 6-digit PIN (customisable). Send it to the customer on a different channel from the link (e.g. SMS, phone).
  </Step>

  <Step title="Access expiry">
    After N failed attempts or X hours without access, Arya temporarily invalidates the link.
  </Step>
</Steps>

## Customer view

<Frame>
  <img src="https://mintcdn.com/agevole/cM9eEPJE8FVhTNOb/images/preventivi/en/client-view.svg?fit=max&auto=format&n=cM9eEPJE8FVhTNOb&q=85&s=067f5824081c4dc6dd570bd03c5839b9" alt="Customer-side quote page with accept/reject buttons" width="1200" height="720" data-path="images/preventivi/en/client-view.svg" />
</Frame>

From the public link the customer sees:

* Header with your logo
* Quote content (per type)
* Bottom action bar: **Accept**, **Reject**, **Request changes**, **Comment**

Comments arrive to you as a side panel notification.

## Digital signature

### Advanced Electronic Signature (FEA)

Quick method based on email + SMS OTP:

<Steps>
  <Step title="Customer clicks 'Sign'">
    The signing flow opens.
  </Step>

  <Step title="Enters personal email">
    If not already known.
  </Step>

  <Step title="Receives OTP">
    Via email and/or SMS to the contact's number.
  </Step>

  <Step title="Confirms">
    Enters OTP → signature collected with timestamp, IP, device fingerprint, document hash.
  </Step>
</Steps>

**When enough**: simple commercial agreements, standard quotes, renewals. Not equivalent to handwritten signature legally, but widely accepted.

### Qualified Electronic Signature (QES)

The most robust legally — equivalent to handwritten signature.

<Steps>
  <Step title="Customer clicks 'Sign QES'">
    The flow redirects to the signature provider (integrated: Namirial, Aruba, InfoCert).
  </Step>

  <Step title="Strong authentication">
    Customer identifies via:

    * **SPID** (level 2 or 3)
    * **CIE** (Italian electronic ID) with NFC
    * **CNS** (National Services Card)
    * **Qualified certificate** on smart card or remote
  </Step>

  <Step title="Apply signature">
    Provider applies qualified signature to the quote PDF. Arya receives callback and updates status.
  </Step>

  <Step title="Download">
    Both you and the customer receive the QES-signed PDF. The validity is enforceable in court.
  </Step>
</Steps>

**When needed**: high-value contracts, regulated sectors, explicit customer or legal request.

## Multi-party signature

If the quote requires multiple signatures (e.g. two executives):

<Steps>
  <Step title="Configure signatories">
    At publication → **Signatories** → add all required contacts with role.
  </Step>

  <Step title="Signing order">
    Pick sequential (one at a time) or parallel (all simultaneously).
  </Step>

  <Step title="Arya orchestrates">
    Each signatory receives their link when it's their turn. After the last signature, the quote moves to `Signed`.
  </Step>
</Steps>

## Audit trail

For every signed quote, Arya stores:

* Timestamp (UTC) of every event
* Signer's IP and device
* SHA-256 hash of the document at signing time
* Verified identity (email, phone, SPID, etc.)
* Accepted consents

Export the signature certificate from **⋯ → Signature certificate (PDF)**.

## Frequently asked questions

<AccordionGroup>
  <Accordion title="Is the public link indexed by search engines?">
    No. Arya sets noindex and blocks crawlers via robots.txt. The link is effectively private.
  </Accordion>

  <Accordion title="Can I revoke an already-sent link?">
    Yes. **⋯ → Revoke link**. The customer will see "Access revoked" on next load.
  </Accordion>

  <Accordion title="Which QES providers are supported?">
    Namirial, Aruba, InfoCert, Universign. Configuration in **Settings → Quotes → QES signature**.
  </Accordion>
</AccordionGroup>