Documents
Documents in LadVen OS keep working files next to the process: a task, CRM card, client, workgroup, or workflow. This is not just file storage. A document should make clear what the material is, which case it belongs to, which version is current, who must review or sign it, and what happens next.
Use documents as a managed work layer, not as a folder of random attachments.
Where to Find It
Main areas:
- Documents (
/documents) - document list and working cards; - Document card - files, status, links, actions, history, and comments;
- Bundle templates (
/documents/templates) - repeatable document sets for tasks, CRM, clients, and workgroups; - Inbound exchange (
/documents/exchange/inbound) - processing documents received through external exchange; - related blocks inside tasks, CRM, extranet, and workspaces.
Available actions depend on permissions, document type, linked object, and signature or exchange policy.
Registry presets and filters
The general registry offers All, Mine, Participating, Incoming, Needs action, and Overdue presets. Mine and Participating require a current user; Needs action selects documents awaiting signature, while Incoming and Overdue use their own sorting. The link-state filter separates All, Linked, and Unlinked and is available only without a task, opportunity, client, or source context. Search, status, and type refine results; the link preserves the selected preset, sort, link state, and view scope. Source only limits results to the source object, while With children includes linked child records. Counters describe the full matching set, not just the rows already loaded. An empty result means the filters produce no match, not that documents were deleted.
Select several rows to start Download for the chosen documents. The portal downloads available files or display packages one after another; it does not create one archive. Rows without a download URL or without download permission are skipped, and the result reports how many were skipped. Check permissions and the selected set before starting. Clicking a row opens its card, the file link opens a new tab, and the separate control starts a download; when no usable file link exists, the row action strip is hidden. Open the row actions menu from the ellipsis or context action to open the card/file, download the primary file or display package, run an available primary action, open a related record, or copy a link. When an action is not allowed, the menu shows the reason instead of implying success; Esc, arrow keys, and Enter operate it, and the mobile menu closes when you tap outside.
Working Flow
- Create or open a document from the right context: task, opportunity, client, project, or document list.
- Use a clear title and type: contract, invoice, act, proposal, case materials, power of attorney, or another business type.
- In the Upload file modal, the file and document title are required. Optionally search for and select a client, project, legal entity, opportunity, or task; with no context selected, you can upload without a link and link it later. Loading, no-results, and denied search states mean waiting, no match, or missing access respectively—retry or check permissions.
- Check the version before approval, client sending, or extranet publishing.
- Leave a comment: what changed, who must review it, and the next step.
- If the document set repeats, use a bundle template.
Document Card
The document card should show the work context: title, type, status, linked files, client or task, responsible participants, and action history. If the document is linked to CRM, tasks, or extranet, the user should understand why it exists and who waits for the result.
Avoid names like scan.pdf or final_new_2. A good title helps people find the document without opening the file.
Document Editor: Text, Formatting, and Tables
You can prepare document text right inside LadVen OS, without switching to a separate office editor. The built-in editor supports formatting (headings, lists, emphasis, links) and tables - enough to put together a proposal, a meeting record, an instruction, or an internal policy in the same place as the rest of the work on the document. A new Markdown table starts with headings and cell placeholders in the portal's active language; the placeholder clears when you type the first character, so a Russian seed does not leak into another locale.
If a document is already prepared in Word, you can import it from a .docx file: the text, formatting, and tables are moved into the editor, and from then on the document lives in the portal together with its status, versions, links, and approval. This is handy when a draft arrives in Word but then needs to be managed as a working document rather than as an attachment.
The formatting toolbar is localized in all portal languages. The same formatting is available in comments, so a note on a document or task can be made readable - with lists, emphasis, and links instead of a solid wall of text.
What to avoid. Do not move complex Word layouts into the editor just to get an exact copy - the portal stores a working document, not the layout of a printed form. If you specifically need the original layout or design, attach the source file as an attachment and keep it as the main version.
Before external sending or signing, check that the current version is open. If a document has several files, identify the main file and the supporting attachments.
Do not delete an older version if it is needed for approval history. Leave a clear comment explaining why a new version appeared.
When this Rich Markdown editor mode is available, Tab/Shift+Tab move through a table one cell at a time. Pressing Tab in the last body cell appends a row; Enter moves to the next row in the same column and appends a row when you reach the end. After a row is appended, the first character you type is retained; typing inside a cell is grouped into one undo step instead of undoing one letter at a time. Ctrl/Cmd+Z and the platform’s redo shortcut (Ctrl+Y or Cmd+Shift+Z) undo and redo structural table edits. The exact shortcuts depend on the current editor mode; the deployed version may lag behind this behavior, so verify it before relying on it.
Bundle Templates
A bundle template describes a repeatable set of documents: which documents are needed, which are required, where the bundle applies, and which approval or signature rules are used.
Use templates for recurring processes: sale package, contract package, service request, legal case, onboarding, or project start. Do not create a template for a one-off case the team will not repeat.
Tasks and CRM Links
A document should be linked to a work object when execution depends on it. In a task, the document gives the assignee input materials and expected result. In CRM, the document records the commercial or legal basis of work.
If a document must be prepared, reviewed, or sent, create a task with an owner and due date. If it belongs to a client, check the CRM link and access permissions.
Signature and Exchange
For documents sent to external exchange or signature, counterparty, legal entity, current version, and status matter most. Before sending, check that the document belongs to the right client, contains no internal comments, and is ready for an external action.
If external exchange needs attention, do not bypass it with undocumented manual sending. The registry can show an explicit rejection, deletion, error, or import failure (rejected, deleted, error, import_failed) with a danger action. Do not treat the ordinary document status “Ready” as success when an exchange error is shown nearby: check the provider label, cause, and whether a retry is safe. unknown means the operator did not report a status, not that the exchange completed. Record the state and next step so the team sees where the document stopped.
An exchange failure is shown as a danger state without a position on the progress track. If your own action is also required, such as signing or confirmation, that action takes priority over the exchange-error message. unknown appears as a separate qualifier beside the ordinary status and does not mean the exchange completed.
How to send a document for signature, manage signers, and open external access via a link is covered in Signature and External Access to Documents.
Inbound Documents
A document received from outside must be sorted first: identify the client or opportunity, check for duplicates, link it to a task or CRM record, and assign an owner. Do not move an inbound file into the general list without context, or the team will quickly lose the reason it appeared.
If the document contains personal, financial, or contractual data, check access before discussing it in a task, chat, or extranet space.
Manager Control
Managers should regularly check:
- documents without a linked task, client, or CRM card;
- bundles where a required document is missing;
- documents waiting for approval, signature, or external exchange;
- old versions that people still use;
- templates that create unnecessary or unclear documents;
- files published externally or to extranet without an access check.
Good Practices
- Name documents by business meaning: client, type, period, or result.
- Do not put private data into public descriptions.
- Check the version before sending, signing, or extranet publishing.
- Link documents to tasks, CRM, client, or workgroup.
- Use templates for repeatable bundles.
Business Scenarios
- Client portal for document approval
- Sales pipeline with tasks and documents
- CRM for a law firm
- All scenarios
Related Sections
Conceptual guidance, not a UI screenshot or state evidence.