HDVerityLawVerityLaw Docs
Help Center

VerityLaw Overview

Product overview explaining what VerityLaw does, who uses it, and how the current staff dashboard and client portal fit together.

publicusers

Understanding What VerityLaw Does

This page explains what VerityLaw is, what problems it solves, and how the current product surfaces fit together.

Product: VerityLaw
Module: Whole Product
Role: Any user
Difficulty: Beginner
Time: 5 minutes
Last Updated: 2026-03-10
Version: Current repo baseline

Before You Start

  • Know whether you are staff or a client.
  • Be ready to decide whether your task belongs in the staff dashboard or the client portal.

What is VerityLaw?

VerityLaw is a legal operations, privacy, governance, and client-service platform. In plain English, it is the place where your team keeps clients, matters, compliance records, contracts, governance work, billing, trust activity, and client-facing updates in one operating system instead of spreading them across email, folders, and spreadsheets.

The current docs baseline should treat these as the main surfaces:

  • the internal staff dashboard at /dashboard
  • the client portal at /portal

Smaller admin, law, and standalone portal apps still exist in the repo, but they are not the main user-manual baseline unless your environment explicitly uses them.

When do you use this product?

Use VerityLaw when your team needs one place to manage legal work, privacy and compliance work, governance records, client communications, and related operational support. If you do not use a structured system for this work, client records drift, deadlines get missed, evidence becomes hard to trace, and governance work turns into a guessing game.

Where do you find the main workspaces?

Primary paths:

  • Internal operations: /dashboard
  • Client-facing access: /portal

If you are not sure which one to use, stop and read Choosing the Right VerityLaw Workspace before doing anything else.

How the current product family is arranged

  1. Use /dashboard for internal work such as practice operations, privacy and compliance, finance, contracts, governance, verification, reports, API management, and administration.
  2. Use /portal for client-facing visibility into cases, documents, invoices, messages, and compliance actions.
  3. Treat legacy admin or law surfaces as environment-specific exceptions, not as the default docs baseline.

What if you assume everything in the requirements is already live?

"The product should have a full governance or automation feature, but I cannot find it"

Why this happens: The requirements and feedback describe a broader platform than the currently visible routes prove end to end.

Fix: Use Checking What Is Live, Partial, or Still Missing before telling anyone a feature exists.

What's Next

Related Pages

Still Stuck?

  • Search the VerityLaw help set.
  • Use the support bot if your environment exposes it.
  • Contact support: support@veva.co.za

Was this page helpful? [Yes] [No]