Prepare the document
Identify the document version and the people who will sign.
Agreements, with the evidence that matters
Move your document
towards a trusted signature.
Bring the document, the people signing and their supporting evidence together. See what is missing, prepare the signing flow and keep a record you can review.
Workspace access requires an account. The example below needs no account or upload.
A practical example · illustrative data
Know what still needs attention.
A service agreement between two companies. A known identity is one part of the picture; the authority to represent a company needs its own evidence.
SAMPLE / NOT FOR SIGNING
Service agreement
North Studio & Example Operations
Document version 3
Two company representatives
Prepared for review
Example readiness review
One item to follow up
- Document version identifiedAvailable
- Identity evidence in profileAvailable
- Authority to sign for the companyNeeds review
- Signing methodPending review
Next step: request the missing authority record and review it against the agreement's requirements.
Illustration of the workflow, not a live assessment. Available checks depend on configuration and providers.
From preparation to record
A clear path through signing.
Review requirements
Compare the agreement's configured requirements with available identity and authority evidence.
Complete the signing flow
Resolve missing information and use the available signing route. Each signer provides their own consent.
Keep the record
Review the outcome and the artifacts produced by the selected route. A signed document and its evidence are distinct records.
Reusable Trust Profiles
Build on what you already know.
A Trust Profile brings identity and organization evidence together for reuse across agreements. Each new agreement still has its own requirements.
Review what remains applicable, refresh expired information and request what is missing. The scope of disclosure should follow the transaction.
See profile capabilities and limitations →At the next agreement
- Available
Evidence already recorded in the profile.
- Needs review
A changed role, expired authority or a different requirement.
- Missing
Information that needs to be supplied for this agreement.
Organization authority evidence is beta. Matching follows configured policies; it is not a legal determination.
Start with your agreement
The right questions for each situation.
A personal agreement
Bring the document and signer together, then follow the identity, consent and signing steps required by the configured flow.
Signing for a company
Review both the person and their authority to represent the organization. Follow up when evidence is missing or no longer current.
A document in a business process
Connect the signing request, status and resulting evidence to the work that needs them through an application integration.
Choose how you work
Your workspace. Your application. Your process.
In AccordFlow
Sign in to your workspace to access the document and signing tools enabled for your account.
Open workspace →In your application
Use the API and PHP SDK to prepare signing requests and retrieve their status and evidence.
Explore API & SDK →With Robo Connector
Connect signing with the document and matter workflow. The integration coordinates review, invitations and retrieval of the outcome.
Explore Legal Office →For developers
Bring AccordFlow into your application.
Start with the PHP SDK. Prepare envelopes, add documents and recipients, and retrieve signing status through the application API.
Install with Composer
composer require robo-meister/accord-flow-apiPHP 8.1+ · cURL and JSON extensions
Run the SDK on your server. Keep access tokens out of browser code.
SDK source & examples →Try it without an account
See how a document change is detected.
Edit the sample text and compare its SHA-256 hash with the original. This local integrity demo does not verify a real signature, identity or legal validity.
Sample text stays in your browser. No file is uploaded.
Comparison not started.
What does this check show?
It compares the complete sample text against the original text using SHA-256. Real verification also depends on the signature, supporting evidence and signing method.
Availability & plans
Know what you are starting with.
The public example is free to explore. Workspace features, limits and provider services depend on your plan and configuration.
Profiles & readiness
Implemented capabilities with configured policy requirements. Organization authority evidence is beta.
Signing providers
Availability depends on the selected route and provider. Demonstration routes are identified separately from production services.
Plan & usage
Check current workspace limits and pricing before starting a production flow.
View plans & pricing →Start with one document