Using the Client Portal

SOP manual for the live client-portal routes under `/portal`, covering dashboard, cases, documents, invoices, messages, and compliance.

publicusers

Using the Client Portal

This page shows portal users and support staff how to use the live client-facing portal in apps/app. It treats the /portal/* routes as the canonical product surface.

Product: VerityLaw
Module: Client Portal
Role: Client, external stakeholder, portal support user
Difficulty: Beginner
Time: 10 minutes
Last Updated: 2026-03-10
Version: Current repo baseline

Before You Start

  • Sign in with a portal user account, not an internal admin account.
  • Know the organisation, case, or invoice you expect to see.
  • Remember that the portal is a client-facing view, not the internal operating dashboard.

What is the client portal?

The client portal is the controlled client-facing surface for case visibility, shared documents, invoices, secure messages, and client-facing compliance activity. It is intentionally narrower than the internal workspace.

When do you use this?

Use the portal when you need to review shared matters, download portal documents, inspect invoices, send secure case messages, or submit a data subject request. Do not use it when you need user administration, trust operations, or internal governance control.

Where do you find it?

Primary path: client portal -> top navigation

Current live routes:

  • /portal
  • /portal/cases
  • /portal/documents
  • /portal/invoices
  • /portal/messages
  • /portal/compliance
  • /portal/compliance/dsr

Current top navigation labels are:

  • Dashboard
  • Cases
  • Documents
  • Invoices
  • Messages
  • Compliance

How do you use the portal?

Review the dashboard

  1. Open the portal Dashboard.
  2. Review Active Cases, Outstanding Invoices, Unread Messages, and recent activity.
  3. Treat the Compliance Score carefully, because the current dashboard shows -- when no assessed score is visible.

Review cases

  1. Open Cases.
  2. Select the correct case from the case list.
  3. In the detail view, confirm the Reference, Type, Status, Priority, Assigned Lawyer, and Deadline.
  4. Review the Activity Timeline and linked Documents.
  5. Use the Messages route for conversation rather than expecting inline case editing.

Review and download documents

  1. Open Documents.
  2. Confirm you are looking at the correct document name, status, version, and date.
  3. Use the Download control only after confirming it works in your environment.

The current /portal/documents page is strong as a document register. Its Download control is present, but the route is thinner than a full download workflow.

Review invoices and payments

  1. Open Invoices.
  2. Review the outstanding, overdue, and invoice-count summary cards.
  3. Open an invoice detail page to review line items, VAT, total, balance due, notes, and payment history.
  4. Use Pay Now from the invoice list when that control is available for unpaid invoices.

Use secure messages

  1. Open Messages.
  2. Choose the correct case thread.
  3. Read the message history carefully before replying.
  4. Treat the route as a secure message-reading and thread-review surface first.

The current /portal/messages page supports thread review and message reading, but its send action is not yet persisted in the page implementation.

Use compliance and submit a DSR

  1. Open Compliance.
  2. Review obligations, due dates, statuses, and existing data subject requests.
  3. Open Submit Data Subject Request when you need to file a POPIA request.
  4. Complete the form carefully and wait for the confirmation state.

The DSR submission form is available in both portal implementations and shows a success confirmation after submission.

What if something does not look right?

"I cannot see internal admin pages in the portal"

What it means: The portal is working as intended.

What to do: Ask an internal user to handle internal administration in the dashboard.

"A control is visible, but it does not fully complete in the portal"

What it means: Some live /portal routes are thinner than a full end-to-end client self-service workflow.

What to do: Treat the page as a review surface and ask internal support to complete the action where needed.

"I need to file a compliance request"

What it means: You should use the DSR route, not secure messages, when you are filing a formal personal-information request.

What to do: Open Compliance and choose Submit Data Subject Request.

What's Next

Related Pages

Still Stuck?

  • Confirm that you are on the live /portal/* routes.
  • Use the portal only for client-facing actions.
  • Contact support: support@veva.co.za

Was this page helpful? [Yes] [No]