Extranet
The extranet gives clients, contractors, and other external participants a separate working entrance to LadVen OS. They see only the context allowed for them: requests, the general channel, documents, and actions opened by their access policy.
Use it when a client needs to participate in work without receiving access to the internal company portal.
Where to Find It
External participants work in the Extranet client portal (/extranet/*). It can include requests, a general channel, and documents, depending on the access policy.
Employees and administrators manage access in Extranet Governance (/extranet-governance). This area is used for user-to-contact and company links, invitations, access policies, allowed pipelines, and security settings.
When to Use It
The extranet is useful when a client must see progress and provide materials, but must not see internal tasks, private discussions, or data from other clients.
Typical scenarios:
- a client creates a request through an allowed form;
- the team discusses the request and exchanges files;
- the client receives documents, offers, invoices, or case materials;
- the client sees the current status and the expected next step;
- a responsible employee manages access, invitations, and CRM context.
Requests
A request records the external participant's need. Depending on the pipeline setup, the client can fill in a form, attach files, read the history, write in the request chat, and see a clear status.
Before submitting a request, the client should check the title, description, attachments, and contact context. Employees should not ask the client to repeat information in chat when it is already present in the request form.
General Channel
The general channel is for ongoing communication with a client or partner outside a single request. Use it for organizational questions, clarifications, and quick approvals.
Do not move internal decisions into the general channel when the client should not see them. If the discussion belongs to a specific request or document, keep it in that context.
Documents
The document area shows external participants only the materials intended for them. A document card can show status, next step, files, preview, download, or a signing action when allowed.
Before publishing a document, check that it belongs to the right company or contact, contains no internal comments, and does not expose another client's data.
Access Governance
Extranet access should be tied to a real contact, company, and allowed work areas. Do not use external access as a generic shortcut into the portal.
Check:
- which user is linked to which contact;
- which companies are available to the external participant;
- which company is selected by default;
- which requests, chats, calls, documents, and pipelines are allowed;
- whether invitations are active and not expired;
- whether password and session policies match the risk level.
If a client sees too much or cannot see the right object, do not work around it with a direct link. Check the user link, company, policy, and object visibility.
Good Practices
- Separate external and internal context: the client portal must not show service notes, internal tasks, or technical data.
- Use clear request and document names so the client does not have to guess.
- Recheck access after changing a company, contact, or policy.
- Revoke outdated invitations and links when collaboration ends.
- Use prepared demo data for screenshots and training, not real requests or real people.