type: product

title: Publisher Identity

product_name: Publisher Identity

category: identity

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

intended_use: 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.

non_goals: Publisher Identity currently provides Advanced organizational seal paths (AATL or EU Advanced), not QSeal.

capabilities:
AATL or EU Advanced trust paths
Managed CA/RA validation
Lifecycle and revocation support

limitations: On-screen trust banners depend on viewer trust-store and local configuration.

integrations:
API
CLI
Zapier
Cloud Connector
Power Automate

standards:
AATL
AdES
EUTL
ISO 32000
LTV
PAdES
X.509

audiences:
Developer
Product
For Developers
For Security & Compliance

source_section: frontmatter > description

extracted_from: content

confidence: high


title: PDF Validator - Trust Made Visible

product_name: PDF Validator - Trust Made Visible

category: pdf-validator

summary: Drop a PDF to check who signed it, whether it’s been changed, and when. Runs in your browser; no uploads required. Works with any standards-based signed PDF.

intended_use: Use the Validator when you need a fast answer to three questions: is this PDF signed, has it changed, and does the certificate chain look trustworthy? The check runs in the browser and works with standards-based PDF signatures, not just files sealed by Trusted Signatures.

capabilities:
Standards-based PDF verification
No file upload required
Works with Acrobat trust model

limitations: Results may vary based on local trust stores

integrations: API CLI Zapier Documenso

standards:
AdES
ISO 32000
PAdES

audiences: Developer Product


title: Cloud Connector for Power Automate

product_name: Cloud Connector for Power Automate

category: power-automate-connector

summary: Run sealing actions from Power Automate while PDFs stay inside your Azure cloud through your Cloud Connector for Azure deployment.

intended_use: Cloud Connector for Power Automate lets teams trigger sealing directly from Microsoft Power Automate while keeping PDF handling inside their own Azure deployment. A flow sends the PDF, credentials, and sealing options to the customer's Cloud Connector for Azure, which performs the sealing operation without moving the file outside the customer's cloud.

capabilities: Expose sealing as a repeatable step in Microsoft business workflows.

capabilities: Use the existing Azure deployment as the runtime endpoint that receives requests from the connector.

capabilities: The document is passed within your Azure boundary instead of being uploaded to an external service.

capabilities: Use your Azure secrets and workflow controls to manage API keys and environment-specific parameters.

capabilities: Save the sealed file back to SharePoint, blob storage, email, queue, or another downstream step.

capabilities: Support business workflow owners without requiring each team to build direct API integrations.

capabilities: Recipients still validate the final document in Acrobat/Reader and other compatible PAdES viewers.

capabilities: Monitor, log, and scale the Azure connector with the same controls used for your other cloud workloads.

limitations: The Power Automate action sends the PDF and parameters to your Cloud Connector for Azure, so the document remains inside your cloud boundary.

integrations:
API
Cloud Connector
Power Automate

standards:
AdES
ISO 32000
PAdES
X.509

audiences:
Developer
Product
For Workflow Owners
For Platform and Security Teams


title: Publisher for Cloud Platforms

product_name: Publisher for Cloud Platforms

category: publisher-cloud

summary: Run high-volume Publisher orchestration in your own cloud with function or Kubernetes deployments while sealing stays in Trusted Signatures' secure service.

intended_use: Publisher Cloud gives enterprise teams the same standards-based PDF sealing capability as Publisher, but with orchestration deployed inside your own cloud environment. Use functions or Kubernetes-based services to handle high-volume document flows while keeping your networking, observability, and automation inside your platform boundary.

capabilities: Deploy the service in your own account, tenant, subscription, or cluster.

capabilities: Choose serverless elasticity or container-orchestrated control depending on your platform.

capabilities: Designed for batch operations, queues, scheduled jobs, and event-driven sealing triggers.

capabilities: Production rollout starts with standard egress to Trusted Signatures.

capabilities: Store credentials in Key Vault, Secrets Manager, Secret Manager, or equivalent controls.

capabilities: Expose a controlled internal service to business applications instead of embedding sealing logic everywhere.

capabilities: Recipients still verify in Acrobat/Reader and compatible PAdES viewers.

capabilities: Trusted Signatures continues to handle secure signing operations with managed key custody.

limitations: Trust verification remains document-native in Acrobat/Reader and other compatible PAdES viewers, subject to reader trust-store configuration.

audiences:
Developer
Product
For Platform Engineers
For Security & Compliance


title: Publisher - Trusted PDF Sealing

product_name: Publisher - Trusted PDF Sealing

category: publisher

summary: Seal PDFs in place with API, CLI, Web sealing, Zapier, Cloud Connector, or Power Automate so recipients see trusted, tamper-evident status in Acrobat/Reader.

intended_use: Publisher adds tamper-evident trust to PDFs you already generate. Use API, CLI, Web sealing, Zapier, Cloud Connector, or Power Automate from your existing systems, keep documents in your environment, and let recipients verify trust directly in Acrobat/Reader.

non_goals: Publisher seals PDFs and proves integrity/origin; it is not a routing workflow for signer approvals.

non_goals: Identity & keys: certificates/keys are issued and managed by Trusted Signatures (no BYO)

capabilities: Trigger sealing from your app or export path; PDFs stay in your environment.

capabilities: Unauthorized edits are surfaced during reader validation checks.

capabilities: Acrobat/Reader can show signer and certification details when trust paths are configured.

capabilities: Embed RFC 3161 timestamp and OCSP/CRL evidence for long-term verifiability.

capabilities: Works in Acrobat/Reader and other compatible PAdES viewers without plugins.

capabilities: Use API, CLI, Web sealing, Zapier, Cloud Connector, or Power Automate in product workflows, CI/CD, scheduled batch jobs, or local browser flows.

capabilities: Allow approved forms/comments while blocking unauthorized content edits.

capabilities: Lock specific fields, including signature fields, without breaking trust policy.

limitations: On-screen trust banners depend on the viewer trust store and local configuration.

standards:
AATL
AdES
CRL
DocMDP
FIPS 140-3
HSM
ISO 32000
OCSP
PAdES
RFC 3161
X.509