Join the LadVen OS testing programRequest a demo
Skip to main content

Glossary

LadVen OS terms that are used consistently in the interface and the documentation. Each term has a short definition and a link to the section with details.

Tasks and Work​

Task​

A unit of work with an assignee, a deadline, a description, files, and a discussion. A task goes through a cycle: assignment, execution, review, closure. Details — Tasks.

Reporter​

The user who created the task and accepts its result. The reporter formulates the expected result and decides whether the task is closed or returned to rework. Details — Assign Participants.

Assignee​

The user who performs the task and is responsible for the result. A task always has one assignee — this keeps responsibility unambiguous. Details — Assign Participants.

Co-executor​

A user who takes part in the work together with the assignee. Co-executors see the task and work in it, but the result is accepted from the assignee. Details — Assign Participants.

Observer​

A user who follows the progress of a task without taking part in the execution: receives notifications and sees the discussion. A role for control, not for work. Details — Assign Participants.

Checklist​

A list of verifiable steps inside a task. A checklist turns the description into a sequence of actions that makes progress visible. Details — Add a Checklist.

Deadline​

The date by which the task result must be ready. Overdue tasks are highlighted in lists and views — they show the manager where work is stalling. Details — Task List, Filters, and Views.

Acceptance​

The reporter's check of the result before closing the task: match with the description, a completed checklist, final files. Details — Review and Close a Task.

Rework​

Returning a task to work after review, with a comment on what exactly was not accepted and what result is missing. Details — Review and Close a Task.

View​

A saved way of looking at the task list: a set of filters, columns, and sorting, including Kanban. Views let a manager keep ready-made slices: overdue, in review, by department. Details — Task List, Filters, and Views.

Kanban​

A task view as boards with columns by status or stage. A card moves across the columns as the work progresses. Details — Task List, Filters, and Views.

Task template​

A task blank with a ready description, checklist, participants, and deadlines for repeatable work. A template turns a verbal procedure into a standard. Details — Templates, Recurring Tasks, and Automation.

Recurring task​

A task that is created automatically on a schedule: a weekly report, a monthly reconciliation. Details — Recurring tasks.

CRM and Sales​

Client​

A company or contact the business works with: a card with details, interaction history, and links to tasks and documents. Details — Clients, companies, and contacts.

Deal​

A specific sale or client inquiry that moves through pipeline stages from interest to result. Details — Deals and inquiries.

Pipeline​

The path of working with a client, split into stages: from incoming interest to completion. The movement of deals through the pipeline shows the state of sales. Details — Pipelines and stages.

Stage​

The pipeline step where a deal currently sits. A stage change reflects real progress: the call happened, the contract was sent, the payment arrived. Details — Pipelines and stages.

Inquiry​

An incoming client request — for example, from a website form. An inquiry enters CRM with a source and an owner and goes through triage: accepted, spam, or needs clarification. Details — Forms and inbound flow.

Form​

A configurable web form for receiving website requests directly into CRM. Details — Forms.

Follower​

An employee who tracks a deal or client record and receives notifications about its changes — similar to an observer in tasks. Details — Deals and inquiries.

Automation and Processes​

Rule​

An automatic reaction to an event: the status changed — create a task, send a message, update a field. Details — Task rules.

Robot​

An automatic action in CRM tied to a pipeline stage: the deal reaches the stage — the action runs. Details — CRM robots.

Workflow​

A multi-step automated chain with participants, conditions, and branches: approval, hiring, shipment. Details — Workflows.

Process instance​

One specific run of a workflow: which data it carries, which step it is on, and who must act now. Details — Process instances.

Operation guard​

An automatic check that prevents completing an action against the rules: for example, closing a task without a final file. Details — Operation guards.

Message template​

A prepared text for automatic notifications and process messages. Details — Message templates.

Documents and Files​

Document card​

The document's page with versions, status, and links to tasks, deals, and the client. Details — Documents.

Version​

A saved state of a document. Work happens in the current version, and the change history stays available. Details — Documents.

A link to a file for a person outside the portal — with an expiration limit and, if needed, a password. Details — Disk and Files.

Access and Structure​

Department​

A company unit in the portal structure. The department defines whose work a manager sees and how control slices are built. Details — Company and teams.

Workgroup​

A group of employees around a project or work stream — with its own tasks, files, and discussions, independent of the department structure. Details — Company and teams.

Extranet​

A restricted portal for external participants: a client sees only their own requests, documents, and discussions, but not the company's internal work. Details — Extranet.

Access policy​

A set of rules that defines what an external participant or role can see and do. Before access is granted, the effective policy — the combined result of all settings — is checked. Details — Extranet.

Notification​

A message about an event in an item you follow: a new discussion, a status change, a role assignment. Details — Notifications.

Role​

An employee's base access level: administrator (configures the portal), head (runs a department), employee (works with their own tasks and clients). The exact rights are refined by policies per area. Details — Access and roles.

Access area​

The boundaries within which a right applies: company, department, pipeline, stage, project, or a specific user. Access is granted by area, not "to everything at once". Details — Access and roles.

Two-factor authentication (2FA)​

A second login confirmation step after the password — a one-time code from an authenticator app. It protects the account even if the password becomes known to outsiders. Details — Two-factor authentication (2FA).

Communications and Telephony​

Channel integration​

Connecting an external communication channel (Telegram, WhatsApp, a website form) to the portal chat: client messages arrive in LadVen OS, where the team replies and links inquiries to the work. Details — Connecting External Channels to Chat.

Inbound rule​

A condition and an action for automatically processing an incoming letter: create an inquiry in CRM, assign an owner, send an auto-reply, move it to a folder. Details — Inbound Email Rules.

Call log (CDR)​

The portal's overall call history: direction, numbers, status (missed and failed calls are highlighted), duration, and date. Details — Call log (CDR).

Last updated on