Extranet
The extranet gives clients, contractors, and other external participants a separate working entrance to LadVen OS. They see only the allowed context: requests, the general channel, documents, and the actions opened for their role. Internal tasks, internal discussions, and other clients' data stay closed.
Use the extranet when a client needs to see work progress and hand over materials but should not enter the internal company portal.
Two Sides of the Extranet
Conceptual guidance, not a UI screenshot or state evidence.
The extranet has two workplaces, and each one has its own documentation page:
| Side | Who works here | Where | Detailed guide |
|---|---|---|---|
| Employees | Administrator, client service lead, account manager | Extranet Governance (/extranet-governance) | Extranet for Employees |
| Clients | External participants: clients, contractors, partners | Client portal (/extranet) | Extranet Client Portal |
Employees connect external participants, configure permissions, and publish documents. Clients create requests, keep up the conversation, and receive and sign documents.
How Access Works
Conceptual guidance, not a UI screenshot or state evidence.
External access rests on three elements:
- Link connects a user to a CRM contact and the client's companies and defines the client context they work in.
- Access policy defines what the participant is allowed to use: requests, chats, calls, documents, and pipelines. The company policy sets the overall perimeter, the contact policy refines the access of a specific person, and the result is shown as the effective policy.
- Invitation — a one-time link for the first login: the client sets their own password and enters the portal.
Where to Start
Conceptual guidance, not a UI screenshot or state evidence.
- Check that the client's contact and company in CRM are up to date.
- Create a link in Extranet Governance: user, contact, companies.
- Configure the effective policy: start with the minimum set — request creation, the request chat, one pipeline.
- Issue an invitation and hand it to the client through a trusted channel.
- After the client's first login, review the request and document lists together with them.
Step-by-step instructions are in the employee guide; what the client will see is described in the client portal overview.
Typical Scenarios
Conceptual guidance, not a UI screenshot or state evidence.
- a client creates a request or an application through an available form;
- the team discusses the request and attaches files;
- the client receives documents, offers, invoices, or case materials and signs them;
- the client sees the status and the next expected step;
- a responsible employee manages access, invitations, and the connection to the CRM context.
Demonstrations and Training Without Client Data
Conceptual guidance, not a UI screenshot or state evidence.
The extranet shows personal client data: contacts, companies, files, invitation links, emails, phone numbers, message history, and documents. Do not take them outside the working context — not into training materials, not into demonstrations, and not into correspondence with other clients.
For employee training and demonstrations, prepare a test environment:
- neutral employee, client, and company names;
- test requests without real contracts, phone numbers, emails, or private links;
- safe files without client content;
- revoked or one-time invitations without active tokens.
If a recording or screen capture includes a real client, an address, or an active invitation link, do not distribute the material — rebuild it with test data.
Good Practices
Conceptual guidance, not a UI screenshot or state evidence.
- Separate external and internal context: the client portal must not show service notes, internal tasks, or technical data.
- Start with minimal access and expand it as the need appears.
- Check the effective policy after changing a company, contact, or permissions.
- Revoke outdated invitations and links when the collaboration ends.
- Keep each discussion in the object it belongs to: a request, a document, or the general channel.
Business Scenarios
Conceptual guidance, not a UI screenshot or state evidence.
Related Sections
Conceptual guidance, not a UI screenshot or state evidence.