HDVerityLawVerityLaw Docs
Help Center

Running Administration

SOP manual for the Administration area covering users, departments, roles, jurisdiction tools, tokens, vault, licenses, system health, settings, POPIA roles, nudges, and audit logs.

publicusers

Running Administration

This page shows internal administrators how to run the current Administration area in VerityLaw. It distinguishes clearly between live CRUD, read-only oversight, helper tools, and buttons that are visible but not yet fully backed by a route or workflow.

Product: VerityLaw
Module: Administration
Role: System administrator, operations administrator, governance support, Information Officer support
Difficulty: Intermediate
Time: 12 to 15 minutes
Last Updated: 2026-03-10
Version: Current repo baseline

Before You Start

  • Sign in to the internal VerityLaw dashboard with the right permissions.
  • Confirm you are in the correct organisation context before changing anything.
  • Know whether you are doing user administration, configuration, integrity review, or audit review.

What is the Administration area?

The Administration area is the control surface for operational setup and oversight. It contains user and department management, governance support tools, token and vault checks, organisation settings, automation rules, and audit visibility.

When do you use this?

Use this area when you need to administer users, configure departments, review permissions, check jurisdiction rules, verify integrity, inspect system health, update organisation settings, or audit what happened in the system.

Where do you find it?

Primary path: Dashboard -> left sidebar -> Administration

Current routes:

  • /dashboard/admin/users
  • /dashboard/admin/users/new
  • /dashboard/admin/departments
  • /dashboard/admin/departments/new
  • /dashboard/admin/departments/[id]/edit
  • /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

How do you run Administration safely?

Manage users and departments

  1. Open Users to review names, emails, roles, status, and last login.
  2. Use New User when you need to create an account.
  3. Open Departments to review department names, heads, and creation dates.
  4. Use New Department or the department Edit link when you need to maintain department data.
  5. Use delete carefully, because department deletion is a direct administrative action.

These are live management routes in the current UI.

Review roles and permissions

  1. Open Roles.
  2. Read the permission matrix by module and role.
  3. Treat this page as read-only.

The page explicitly says custom roles are available post-UAT, so do not describe it as a custom-role builder.

Use jurisdiction tools

  1. Open Jurisdiction.
  2. Review Jurisdiction Rules, Mandatory Clauses, and the Data Transfer Matrix.
  3. Use Check Data Transfer Compliance when you need a rule-based transfer answer.
  4. Use Classify Party when you need a quick consumer or business-protection classification.

These helper tools are interactive and return results on the page.

Review tokens and vault integrity

  1. Open Tokens to review issued token stats and the token table.
  2. Use Verify Token Integrity when you have token JSON and the signing secret.
  3. Open Vault to review vault-entry counts and integrity status.
  4. Use Integrity Check when you need to compare content against a stored hash.

The Issue Token, Create Snapshot, and Export Manifest controls are visible but explicitly marked Coming Soon in the UI.

Review licenses, system health, and organisation settings

  1. Open Licenses to review name, type, status, seats, and expiry.
  2. Open System Health to confirm database connectivity, session counts, user counts, and recent audit volume.
  3. Open Settings to update organisation details, address, contact information, website, and notes.

The Licenses page shows a New License button, but the current route set does not include a matching /dashboard/admin/licenses/new page. Treat the page as a review list until that route exists.

Run compliance-oriented administration

  1. Open POPIA Roles to review current role assignments.
  2. Use Assign Role when you need to assign an Information Officer, Deputy Information Officer, or Employee role.
  3. Note that the current form expects UUID-style User ID and optional Department ID, not a user picker.
  4. Open Nudge Config to create or review automated reminder rules.
  5. Open Audit Logs to inspect the append-only history of system actions.

What if something does not look right?

"I can see a button, but it says coming soon"

What it means: The UI is showing planned capability honestly.

What to do: Do not promise that workflow to users yet. Use the live review or verification tools only.

"I expected to create a license, but there is no route"

What it means: The list page is live, but the create route is not present in the current route set.

What to do: Treat licenses as review-only for now.

"The POPIA role form is asking for IDs"

What it means: The current UI requires direct identifiers rather than dropdown selection.

What to do: Confirm the correct UUID before submitting, because this is not a beginner-friendly picker flow yet.

What's Next

Related Pages

Still Stuck?

  • Confirm whether the route is live CRUD, a helper tool, or a read-only register.
  • Use the functionality gap map before promising an admin action exists.
  • Contact support: support@veva.co.za

Was this page helpful? [Yes] [No]