HDVerityLawVerityLaw Docs
Help Center

Compliance Operations

Manual for working with privacy, compliance status, data subject requests, and related governance workflows in the current VerityLaw dashboard and portal surfaces.

publicusers

Running Compliance Operations

This page shows you how to use the current compliance pages for real work while staying honest about the governance features that are still partial or missing.

Product: VerityLaw
Module: Compliance
Role: Information Officer, compliance operator, administrator, portal user submitting DSRs
Difficulty: Intermediate
Time: 10 minutes for review, longer for live case handling
Last Updated: 2026-03-10
Version: Current repo baseline

Before You Start

  • Sign in to the correct workspace.
  • Know whether you are doing internal compliance work or a client-facing portal action.
  • Have the client or request reference ready if you are reviewing a specific item.

What is the compliance workspace?

This is the area where VerityLaw surfaces compliance posture, obligations, data subject requests, and supporting governance components. In plain English, it is the place where your team checks whether privacy and governance work is on track.

When do you use this?

Use this page during daily governance review, when checking overdue obligations, when tracking a DSR, or when a portal user needs to submit a data subject request. If you do not review this regularly, overdue obligations and SLA-risk requests will quietly pile up.

Where do you find it?

Internal path: /dashboard -> Privacy & Compliance routes and /dashboard/compliance
Portal path: /portal -> Compliance

How to run compliance work

Review compliance posture in admin

  1. Sign in to /dashboard.
  2. Start at Privacy Dashboard or Compliance, depending on the question in front of you.
  3. Review the top-level score and status cards first.
  4. Check for overdue obligations.
  5. Check data subject requests that are overdue or still pending.
  6. Review the available evidence, policy, or governance sections lower on the page.

Review data subject requests in admin

  1. Open DSAR Management.
  2. Review the Data Subject Requests list.
  3. Identify the request reference.
  4. Confirm the request type.
  5. Confirm the status.
  6. Confirm the submission date and whether SLA risk exists.

Submit a DSR from the portal

  1. Sign in to /portal.
  2. Open Compliance.
  3. Click Submit Data Subject Request.
  4. Complete the request form carefully.
  5. Submit the request.
  6. Return to Compliance and confirm the request appears if your environment supports immediate display.

What if you need a wider governance workflow?

"I need regulator registration, PAIA manual, or delegation register features"

Why this happens: The requirement baseline includes broader privacy-governance scope than the current visible end-to-end product flow.

Fix: Use Checking What Is Live, Partial, or Still Missing before claiming the feature exists.

What's Next

Related Pages

SA Compliance Reference

  • POPIA - data subject participation and accountability duties are the main plain-language drivers of the DSR and governance workflows.
  • PAIA - access and manual obligations still matter even where the full in-product lifecycle is partial.

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]