Admin and Governance Operations

Manual for the internal VerityLaw dashboard workspace, with emphasis on governance, privacy oversight, administration, and daily operational control.

publicusers

Running Admin and Governance Operations

This page shows internal staff how to use the main dashboard workspace for daily control, governance review, administration, and Information Officer support work.

Product: VerityLaw
Module: Admin and Governance
Role: Administrator, Information Officer, legal operations lead, compliance operator
Difficulty: Intermediate
Time: 10 minutes for daily review, longer for case-by-case work
Last Updated: 2026-03-10
Version: Current repo baseline

Before You Start

  • Sign in to the /dashboard staff workspace.
  • Know which client organisation you are working on.
  • Have the correct internal permissions for governance or admin work.

What is the internal governance workspace?

The dashboard workspace is the internal operating console. Governance and admin work is spread across the Governance, Administration, and Privacy & Compliance groups instead of one tiny back-office menu.

When do you use this?

Use this page at the start of the day, when reviewing governance risk, or when working internal operations that should never be handled from the client portal. If you skip this structure, you will miss urgent items or work on the wrong client.

Where do you find the core admin and governance areas?

Primary path: /dashboard -> left sidebar

Current main governance and admin sections include:

  • Dashboard
  • Governance
  • Entities
  • Authority Matrix
  • Board Packs
  • Resolutions
  • Delegations
  • Privacy Dashboard
  • Information Officer
  • Compliance Health
  • Administration
  • Users
  • Departments
  • Roles
  • Jurisdiction
  • Tokens
  • Vault
  • Licenses
  • System Health
  • Settings
  • POPIA Roles
  • Nudge Config
  • Audit Logs

How to run the workspace safely

  1. Sign in to /dashboard.
  2. Open Dashboard.
  3. Review summary cards for active cases, overdue deadlines, open assessments, and WIP.
  4. If there is urgent work, route yourself to the relevant group first:
    • Practice for cases and clients
    • Privacy & Compliance for privacy obligations and DSR work
    • Governance for entities, delegations, authority, and board material
    • Administration for users, roles, and system controls
  5. Confirm the correct client organisation before you create or edit anything.
  6. Use Administration for users, departments, roles, audit logs, and platform settings.
  7. Use Governance for entities, authority, delegations, resolutions, and board-pack work.
  8. Use Privacy & Compliance for Information Officer oversight, notices, DSARs, breaches, policies, training, and related compliance records.

Information Officer guidance

The business expectation for the Information Officer is wider than the current visible product. In the current build, that role mainly operates through the dashboard privacy routes instead of one tiny standalone console.

That means:

  • responsibility is broader than the current UI,
  • the current UI still supports real oversight work,
  • and the docs must not invent one-click governance flows that do not exist.

What if the governance function you need is missing?

"I need regulator registration or a broader governance workflow, but I cannot find it"

Why this happens: Some governance and privacy-intelligence surfaces are real routes, but not every wider obligation workflow is fully live end to end.

Fix: Check Checking What Is Live, Partial, or Still Missing before promising the workflow exists.

What's Next

Related Pages

SA Compliance Reference

  • POPIA - accountability and governance duties still apply even where product automation is partial.
  • PAIA - manual and access-request obligations should not be assumed complete in-product unless confirmed.

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]