Document Signing arrives in Clear Ideas, alongside important improvements to workflow automation, metadata-aware retrieval, analytics, and overall platform polish.
Document Signing
April introduces a major new capability for Clear Ideas: secure, account-based PDF signing inside the same workspace your team already uses for controlled collaboration. The signing experience is designed for practical business workflows such as approvals, acknowledgements, attestations, and client-facing signature requests, while keeping the request, completed document, and evidence package connected to the original record.
This release includes a complete end-to-end signing flow across web and API, from request preparation through recipient verification, completion, and certificate generation. It also lays the groundwork for organization-level governance so teams can standardize how signing is used across departments and clients.
PDF signature requests with visual field placement Prepare signature, initials, date, name, text, and checkbox fields directly on PDFs. Fields can be required or optional and are assigned to specific recipients.
Sequential or parallel routing Choose whether recipients sign in order or independently. Request progress, participant status, and completion state are tracked directly inside the file experience.
Account-based signing for all recipients Recipients sign through Clear Ideas accounts, including invitation-based accounts created when needed. This keeps signing tied to authenticated user identity instead of anonymous access links.
Signer verification before signing begins Requests can require authenticated access, an email verification code, or account-level two-factor authentication before signing starts. When email-code verification is required, request details and document access remain gated until the challenge is completed successfully.
Saved signatures and smoother signing preparation Signers can save typed, drawn, and uploaded signatures and initials for reuse. The signing flow now does a better job of preparing signers up front, including confirming signer name values when name fields are present.
Authoritative completion and decline certificates Completed requests generate a signed document and a formal signing certificate derived from server-side evidence. Declined requests now generate decline evidence and a decline certificate as well, improving auditability for incomplete ceremonies.
Better request tracking and deliverability visibility Signature request tracking now includes clearer recipient progress and email delivery observability, including bounced-email and complaint states, similar to other invitation-style communication flows in Clear Ideas.
Sender defaults and organization policy controls Senders can define default signing terms for their requests. Organizations can now set default signing terms centrally, choose whether members may override them, and disable signing request creation entirely when needed.
Overall, this release makes signing a first-class Clear Ideas workflow rather than a disconnected add-on. Teams can request signatures, verify recipients, generate authoritative completion records, and keep the entire process close to the source files and audit trail.
Metadata, Search, and Extraction Improvements
Work earlier in March also strengthened the connection between ingestion, extraction, metadata, and retrieval. These changes make Clear Ideas more useful when documents need to be searched and operationalized based on structured attributes instead of relying only on file names or semantic content retrieval.
Metadata-aware search Search now supports metadata-style query patterns, making it easier to combine extracted attributes with normal search terms for more precise retrieval.
Expanded extraction workflow support Extraction and metadata workflows were refined to better validate mappings, persist results, and improve downstream usability in search and file experiences.
Cleaner file-property presentation Metadata and file-property surfaces were improved so extracted information is easier to review and act on.
Workflow and Human Checkpoint Enhancements
March also brought meaningful quality improvements to AI Workflows, especially for teams that need more structured execution and review steps.
Human checkpoint support Workflow tooling now better supports human-in-the-loop patterns and interactive checkpoints where automation needs a deliberate human approval or answer before proceeding.
Structured output contracts for prompt steps Prompt steps can now define output structures using JSON Schema. This makes it easier to require dependable object-shaped results for downstream prompts, looping, and reusable sub-workflows instead of relying on loosely formatted JSON.
Improved sub-workflow step configuration Sub-workflow steps now do a better job of surfacing the selected workflow, required trigger mappings, and parent-to-child variable wiring so reusable workflow modules are easier to configure and review.
Better workflow validation and configuration handling Variable mapping, prompt validation, output-structure validation, and workflow structure handling were improved across web and API, reducing configuration errors and making generated workflows more dependable.
Clearer workflow editing feedback The workflow editor now includes better step-type-aware labeling, stronger schema validation feedback, and clearer canvas indicators for structured steps and sub-workflow relationships.
Internationalization and Platform Polish
Several additional improvements make the product feel more consistent and more ready for broader rollout.
Expanded internationalization work Translation extraction, raw string handling, and locale-related behavior were improved across web surfaces.
Model and platform updates AI model configuration references were updated to reflect newer defaults and current model availability.
General UX refinement A broad set of smaller improvements across content views, PDF handling, and interaction patterns make the application feel more coherent and reliable in daily use.
Under the Hood
This release also includes a large amount of lower-level cleanup and hardening: better validation across request flows, stronger evidence handling for signing, improved API behavior around analytics and workflow execution, and continued refinement of component structure and shared UI patterns across the web application.