01 / The existing evidence
A mapping is not proof
The example shows the data path. Nothing was transferred on this page.
- Mapping
- Example
- Arrival in the workspace
- Not checked
Peak Sign · Inside Peak One
In Peak One a contract is one object, not a copy. Parties are the same companies and people as in the CRM, follow-up tasks land in Peak Work, events in history and inbox, and ⌘K finds it all.
Start Peak Sign in Peak OneExample mapping · no connection is made
Peak SignThe contract
Peak WorkThe taskTask referenceA readable field path as an example. No transfer.
| Peak Sign | Field in Peak Work |
|---|---|
| Contract | Task reference |
| Party | Company |
| Signer | 사람 |
| Deadline | Due date |
| 후속 연락 | Task |
The mapping shows where the data goes. Only a test in your workspace shows what actually arrives.
02 / Shared objects
Inside Peak One the contract needs no interface. It is already there.
Companies and people in the contract are the known objects from Peak One.
After signing, follow-up tasks appear in Peak Work, linked to the contract.
⌘K search, inbox and event history show the same contract.
Trust needs clarity
01 / The existing evidence
The example shows the data path. Nothing was transferred on this page.
02 / Your check
Roles and rights in the workspace decide who sees what. An owner or admin approves protected clauses before sending.
03 / The clear limit
External API, webhooks and an automatic flow from offer to invoice to payment are not available yet.
The next step
Start Peak Sign in Peak One and see how contracts, parties and tasks fit together.
Start Peak Sign in Peak OneCheck in your workspace what actually arrived.
No. Parties and signers are the same companies and people as in Peak One.
To Peak Work, as tasks that refer to the agreement.
Not yet. An external API is planned and not available today.