Publisher Identity AATL EU Advanced OrgID

Publisher Identity

Show your verified organization as signer in Acrobat/Reader with managed AATL or EU Advanced OrgID lifecycle.

Book Demo Start Technical Eval
AATL or EU Advanced
Managed validation
Org signer visible

Show Your Organization as the Verified Signer

Publisher Identity adds organization-level signer identity to your existing Publisher sealing workflow. Keep the same API, CLI, Web sealing, Zapier, Cloud Connector, or Power Automate process while we manage validation, certificate issuance, renewals, and revocation coordination.

When to add Identity

Use Identity when counterparties require your legal entity to appear as signer in Acrobat/Reader, or when policy language requires organization-specific certificate governance.

2

trust path options

Choose AATL or EU Advanced based on reviewer policy expectations.

1

sealing workflow

Keep existing Publisher API, CLI, Web sealing, Zapier, Cloud Connector, or Power Automate automation; Identity changes signer credentialing.

Varies

validation timeline

Issuance timing depends on selected path and CA/RA documentation completeness.

Managed

certificate lifecycle

Coordination for issuance, renewal, and revocation is included.

X.509 organizational certificate AATL or EU Advanced path PAdES / LTV compatible output FIPS 140-3 Level 3 custody
Start Technical Eval

Operational Proof

Add signer identity without creating a PKI program

Identity is designed for teams that need organizational signer visibility in reader-native validation flows.

Finance operations

Reduce invoice and payment-origin disputes.

Procurement and bids

Prove organization-authored submissions.

Compliance teams

Use auditable signer identity controls in reviews.

Engineering teams

Keep existing API, CLI, Web sealing, Zapier, Cloud Connector, and Power Automate integrations unchanged.

Quick answer

If you already use Publisher, Publisher Identity lets the same Web sealing flow show your organization as the signer in Acrobat instead of Trusted Signatures. The PDF is sealed locally in the browser and is never uploaded to Trusted Signatures servers.

Book Demo
See Pricing

How it works

Step 1: Choose trust path

Select AATL or EU Advanced based on customer, regulator, or procurement requirements.

Step 2: Complete validation

We coordinate CA/RA organization verification and certificate issuance workflow.

Step 3: Seal with your OrgID

Publisher continues to seal as before, now showing your organization as signer in Acrobat.

Choose your trust path

AATL OrgID

Broad Adobe ecosystem trust path for global commercial/private-sector workflows.

Discuss AATL fit

EU Advanced OrgID

EU policy-oriented trust path for eIDAS/EUTL-oriented procurement and review context.

Discuss EU Advanced fit

Paths by role

For Developers

Keep your implementation stable. Retain current sealing API, CLI, Web sealing, Zapier, Cloud Connector, and Power Automate controls and map integrations to organizational identity.

API docs

For Security & Compliance

Improve signer provenance governance with managed lifecycle controls and auditable events.

Security overview

What’s included

Validation coordination

Guidance and evidence collection for CA/RA verification requirements.

Certificate lifecycle management

Issuance, renewal planning, and revocation response coordination.

Managed key custody

Non-exportable key operations in FIPS 140-3 Level 3 HSM environments.

Rollout support

Assistance with operational transition and trust-path decisions.

See Pricing

Trust and standards

Identity issues and manages organization-level X.509 certificates that align to AATL or EU Advanced trust-path expectations while preserving the same standards-based sealing behavior (ISO 32000/PAdES profile patterns) in Publisher.

When recipients open sealed PDFs, validation remains reader-native: signer identity, integrity status, and related trust metadata are available in Acrobat/Reader. On-screen trust banners depend on viewer trust-store and local configuration.

For browser-based flows, Identity follows the same local-document model as Web sealing: the PDF stays in the user’s browser, Trusted Signatures never receives the document itself, and the selected organization certificate determines the signer shown in Acrobat.

Trust documentation

Review service boundaries, signer identity controls, and validation behavior.

Open trust docs

Implementation reference

Integrate identity-enabled sealing in existing API, CLI, Web sealing, Zapier, Cloud Connector, or Power Automate automation paths.

Open API docs

Pricing at a glance

Publisher Identity is an annual add-on to Publisher sealing. Path selection (AATL or EU Advanced) and organization validation scope determine issuance timelines and planning.

  • Requires an active Publisher sealing service.
  • Available for teams with one or multiple organization certificates.
  • Includes lifecycle support for renewals and revocation events.
  • Uses the same Publisher subscription across Web sealing, CLI, API, Cloud Connector, and Zapier paths.
See Pricing

Validate Signer Experience

Preview what counterparties will see in Acrobat

Run a side-by-side check with PDF Validator to confirm how signer identity and trust status appear before full rollout.

Open PDF Validator Start Technical Eval

Frequently Asked Questions

What’s the difference between AATL and EU Advanced OrgIDs?
AATL targets broad Adobe ecosystem trust globally. EU Advanced targets workflows that reference eIDAS/EUTL policy expectations.
Do I need Publisher Identity if I already use Publisher sealing?
No. Publisher sealing works by itself. Add Identity when you need your organization shown as signer.
How long does OrgID validation usually take?
Validation timelines vary by CA/RA requirements, trust-path selection, and documentation readiness.
Can we bring our own certificate?
No. We manage issuance and key custody for lifecycle and security consistency.
Can we switch trust paths later?
Yes. Switching requires new certificate issuance; we coordinate transition timing.
Do you offer Qualified Electronic Seal (QSeal) support?
No. Publisher Identity currently provides Advanced organizational seal paths (AATL or EU Advanced), not QSeal.
What happens if a certificate is revoked or expires?
We manage renewal and revocation handling. With LTV enabled, earlier sealed files remain verifiable based on signing-time evidence.
Can one account use multiple organization certificates?
Yes. Accounts can support multiple organization certificates and trust paths. Contact us to plan mapping for teams, brands, or subsidiaries.