Help Center

VerityLaw Screen Map

Route-level map of the current VerityLaw staff dashboard and client portal surfaces, with notes on supporting legacy surfaces.

publicusers

Finding the Right VerityLaw Screen

This page is the route map for the current VerityLaw UI so you can check whether a screen is really in the product before documenting or promising it.

Product: VerityLaw
Module: Reference
Role: Any user, support, QA, documentation author
Difficulty: Beginner
Time: 5 minutes
Last Updated: 2026-03-10
Version: Current repo baseline

Before You Start

Know which workspace you are checking.
Use this page as a route reference, not as a full task guide.

What is this page?

This is a reference page. It lists the currently confirmed route families in the repo and tells you which ones are the canonical docs baseline.

When do you use this?

Use this page when you need to confirm a route, compare workspaces, or keep help pages honest. If a route is not here, it should not be documented as a normal live user path without further verification.

Where do you find the routes?

Routes are grouped below by workspace.

How to use this reference

Choose the workspace: /dashboard or /portal.
Find the route family you expect.
If the route is missing, stop and check the gap map before assuming it exists.

Canonical staff dashboard route families

Route family	Key routes
Overview	`/dashboard`
Practice	`/dashboard/cases`, `/dashboard/cases/new`, `/dashboard/workflows`, `/dashboard/clients`, `/dashboard/clients/new`, `/dashboard/documents`, `/dashboard/ai-legal`
Privacy and compliance	`/dashboard/privacy/dashboard`, `/dashboard/privacy`, `/dashboard/privacy/consent`, `/dashboard/privacy/dsr`, `/dashboard/privacy/data-breach`, `/dashboard/privacy/dpa`, `/dashboard/privacy/policies`, `/dashboard/privacy/training`, `/dashboard/privacy/information-officer`, `/dashboard/compliance`, `/dashboard/assessments`
Finance	`/dashboard/billing`, `/dashboard/billing/time`, `/dashboard/trust`
Contracts	`/dashboard/contracts`, `/dashboard/contracts/new`, `/dashboard/contracts/repository`, `/dashboard/contracts/obligations`, `/dashboard/contracts/negotiations`, `/dashboard/contracts/playbook`, `/dashboard/contracts/heatmap`, `/dashboard/contracts/order-risk`, `/dashboard/contracts/benchmarks`, `/dashboard/contracts/ai-negotiator`
Client operations	`/dashboard/onboarding`, `/dashboard/managed-compliance`, `/dashboard/sector-packs`
Diligence and tenders	`/dashboard/data-room`, `/dashboard/diligence`, `/dashboard/policy-mapper`, `/dashboard/tenders`, `/dashboard/tenders/bid-scoring`, `/dashboard/tenders/response`
Governance and disputes	`/dashboard/governance`, `/dashboard/governance/entities`, `/dashboard/governance/authority`, `/dashboard/governance/board-packs`, `/dashboard/governance/resolutions`, `/dashboard/governance/delegations`, `/dashboard/disputes/simulator`
Intelligence	`/dashboard/privacy/sentinel`, `/dashboard/privacy/dsr-factory`, `/dashboard/privacy/campaigns`, `/dashboard/compliance-twin`, `/dashboard/enforcement-risk`, `/dashboard/remediation`
Verification	`/dashboard/verify`, `/dashboard/verify/identity`, `/dashboard/verify/business`, `/dashboard/verify/bank`, `/dashboard/verify/monitoring`
Reports, API, admin	`/dashboard/reports`, `/dashboard/api`, `/dashboard/api/keys`, `/dashboard/api/webhooks`, `/dashboard/api/docs`, `/dashboard/api/usage`, `/dashboard/admin/users`, `/dashboard/admin/departments`, `/dashboard/admin/roles`, `/dashboard/admin/jurisdiction`, `/dashboard/admin/tokens`, `/dashboard/admin/vault`, `/dashboard/admin/licenses`, `/dashboard/admin/system-health`, `/dashboard/admin/settings`, `/dashboard/admin/popia-roles`, `/dashboard/admin/nudge-config`, `/dashboard/admin/audit-logs`

Portal routes

/portal
/portal/cases
/portal/cases/[id]
/portal/documents
/portal/invoices
/portal/invoices/[id]
/portal/messages
/portal/compliance
/portal/compliance/dsr

Supporting legacy or parallel surfaces

apps/admin still exists in the repo, but it is not the main documentation baseline.
apps/law exists as a much smaller surface and should be treated as environment-specific.
apps/portal also exists as a standalone portal app, but the embedded /portal surface in apps/app is the main current docs baseline.

What if the route you expected is missing?

Why this happens: A menu label, requirement, or assumption may be broader than the confirmed route set.

Fix: Check Checking What Is Live, Partial, or Still Missing.

What's Next

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]