How the portal works
What came in, what we do, and what we owe are one work trail. LadVen OS connects the request, the work, and the obligation so that context does not disappear when you move between sections.
This is a conceptual product model, not a UI screenshot or proof that every function is ready.
Three areas on one trail
The areas overlap and have equal standing. They are not three sequential tiers or a list of modules.
| What the team sees | Entity | State |
|---|---|---|
| What came in — the outside world | client and external-participant requests | mature area |
| What we do — the work | tasks and the next verifiable result | mature area |
| What we owe — obligations | orders and commitments to the client | being built |
We show the third area honestly: its surface is expanding, and individual scenarios should not yet be promised as fully ready.
What came in
A request is incoming context: a client request, message, form, or external step. It explains who needs what, but it is not a completed result by itself. See CRM and requests and the client portal.
What we do
A task turns an agreement into work with an owner, deadline, files, comments, and a verifiable result. See Tasks and task work context.
What we owe
An order or commitment records the promised scope and the next execution steps. This area is being built: use only the scenarios described for your portal and check which actions are available. See Operations.
Transitions are the point
The value is not that three sections sit next to one another, but that a transition keeps one context:
- request → task — a request becomes work with an owner and deadline;
- order → tasks — an obligation becomes verifiable execution steps;
- request → order — a request can lead to an agreed scope and commitment.
If a transition is not supported by your configuration or permission, do not replace it with a promise: keep the relationship in the way your process actually supports.
Cross-cutting layers, not new areas
Documents cross all three areas: they preserve versions, decisions, and approval. The client portal is the external view of the same requests, work, and obligations. They are not a fourth and fifth circle; they are layers that show the relevant part of one trail to different participants.
Do not mix internal tasks and documents with external access: visibility is controlled by permissions and context settings.
Where to go next
- Start with getting started if the portal is new to you.
- For incoming requests, open CRM or the client portal.
- For daily work, use Tasks.
- For commitments, see Operations and remember that this area is evolving.
- A live example of the link is CRM for a law firm.