# Auto-stamp — Automatic CER Attestation

URL: https://docs.nexart.io/docs/dashboard/auto-stamp

Auto-stamp is a project level ingestion setting controlling whether Certified Execution Records are automatically sent to the NexArt attestation node.

## Overview

Auto-stamp is a project-level ingestion setting. It controls whether CERs are automatically submitted for attestation when they are ingested into nexart.io.

Auto-stamp is not a client-side or SDK-side interception feature. It runs during ingestion on the NexArt platform and affects only records associated with the configured project.

## How It Works

- Enabled. CERs ingested under the project are automatically sent through the stamping flow during ingestion. Records receive a signed receipt without manual intervention.
- Disabled. CERs are still ingested and stored, but no automatic stamp is requested. Manual stamping remains available later.

Auto-stamp behavior is evaluated during ingestion. It does not change the CER structure itself. It only affects whether an attestation receipt is added automatically.

## Configuring Auto-stamp

- Open the NexArt Dashboard
- Navigate to Projects
- Select a project
- Open the project settings
- Toggle Auto-stamp CERs during ingestion

The setting applies at the project level. All CERs ingested under that project follow the configured behavior.

## Manual Stamping Still Works

Even when auto-stamp is disabled, records are still created normally. Users can manually stamp a record later. Available stamping actions include:

- Full attestation, which produces a signed receipt
- Redacted reseal, where applicable
- Hash-only timestamp, for legacy or incomplete records

## When to Use It

Enable when:

- You want newly ingested records to become verifiable immediately
- You want consistent automatic attestation for a project

Disable when:

- You want to review records before attesting them
- You want to control node usage more carefully
- You only want to stamp selected records manually

## Relationship to Verification

Auto-stamp affects whether a record receives a signed receipt automatically. Signed receipts allow all verification checks to return PASS, producing a VERIFIED status with full attestation coverage.

If a record is not stamped, it can still verify as VERIFIED for bundle integrity, but the Node Signature and Receipt Consistency checks will be SKIPPED until a stamp is added.