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

Extranet Client Portal

This page describes the extranet through the client's eyes. It helps the team explain what exactly an external participant gets after the invitation: where they see requests, how they write in the chat, where they accept documents, and which actions do not give them access to the company's internal work.

How to grant access and manage policies is described on the Extranet for Employees page.

What the Client Gets​

The client logs in through an invitation and sees only their own working perimeter:

  • requests and their statuses;
  • the request chat and, if allowed, the general chat with the team;
  • documents published for their company or contact;
  • files and comments related to the available requests;
  • notifications about new messages, status changes, and document actions.

The extranet does not show the client internal tasks, other companies, internal comments, service settings, or other clients' work.

First Login​

  1. The client receives an invitation through the agreed channel.
  2. Opens the link, sets a password, and enters the portal.
  3. Checks the default company, their name, and the available sections.
  4. If they see something extra or cannot see what they need, they tell the manager — an employee checks the link and the effective policy.

Do not ask the client to forward the invitation to another person. Each participant needs their own account so the history of messages, signatures, and actions stays verifiable.

Requests and Chat​

A request is the client's main working object. It shows the subject, status, the responsible person on the team side, the conversation, files, and the next actions.

Good practice for the client:

  • write a question in the chat of the specific request, not in the general channel;
  • attach files to the request where they are needed;
  • reply to clarifications in the same conversation so the history does not fall apart;
  • look at the status before asking again — the next step is often already stated.

Documents and Files​

The client sees only the documents published for them. Before publishing, an employee must check that the document belongs to the right company, contains no internal notes, and the expected action is clear to the client: review, approve, sign, or attach a file.

If a document requires a signature or approval, the action must be available directly in the document card. Do not replace it with email forwarding: that loses version control and the decision history.

Security​

Client access is limited by the company and contact policy. If an employee needs to expand access, they change the policy and check the effective result. If the collaboration is over, the link, invitations, and external channels must be revoked.

Common Client Questions​

  • Why can I not see a request? Most likely it belongs to another company, pipeline, or contact. Ask the manager to check the link.
  • Can I add a colleague? Yes, but through a separate invitation and account.
  • Where is the final document? In the documents section or in the request where the decision was made.
  • Why does the link no longer open? The invitation or the external access may have expired or been revoked.
Last updated on