01 / The existing evidence
A mapping is not a delivery receipt
The example shows the translation. No data is transferred here.
- Mapping
- Example
- Arrival in the workspace
- Not checked
Peak Docs · Integrations
Documents refer to customers, projects and tasks in Peak One and create tasks. Import and export are partly there. Connections to outside tools are not available yet.
Start Peak DocsExample mapping · status per connection · no connection is made
Peak DocsThe checklist item
TaskThe tasktask.titleA readable path as an example. No transfer.
| Peak Docs | Task element |
|---|---|
| Checklist item | task.title |
| Relation | concerns |
| Người phụ trách | task.assignee |
| Due | task.due_date |
| Source | task.source |
The mapping shows the translation. Only a test in your workspace shows what actually arrives.
02 / Status before logo
Available, partial or not available: this is where things stand today.
References to customers, projects and tasks with backlinks; comment and checklist → task; Inbox notices.
Import from Markdown and text only; export as PDF, Markdown or HTML, no DOCX.
Direct connections to tools outside Peak One do not exist for Peak Docs yet.
Trust needs clarity
01 / The existing evidence
The example shows the translation. No data is transferred here.
02 / Your check
A public read-only page exists only when you release a version on purpose through a share link.
03 / The clear limit
Peak One references, file formats and missing outside connections are named one by one.
The next step
Start Peak Docs and link your first document to a project or a task.
Start Peak DocsCheck in your workspace what actually arrived.
Documents refer to customers, projects and tasks in Peak One, create tasks from comments and checklists and notify through the Inbox.
Not yet. Direct connections outside Peak One are not available for Peak Docs.
Through a share link with a public read-only page, for which you release a version on purpose.