Consent Docs
Open console

Change a DPDP date, value, list or wording

Record a new DPDP date, period, threshold, list or wording when the Government notifies one. One platform person drafts it and a second approves.

How-to3 min readFor project administrators and deployment operators

Checks, deadlines, forms and erasure follow the deployment's rule set. When the Government changes a rule, record it in the Platform area of the console. One person drafts the change with its Gazette notification. A second person approves it, and every project follows it from its date.

Before you start#

  • You work in the platform organization in the IAM. The console opens the Platform area instead of a project when that organization is selected.
  • Your platform role holds the permissions below. The person who approves needs approveLawAmendment and cannot be the person who drafted.
Permission Lets you
Consent.PlatformServices.fetchLawRules See the rule set, rules, amendments and versions
Consent.PlatformServices.draftLawAmendment Record, edit, send and undo changes
Consent.PlatformServices.approveLawAmendment Approve and publish, or send back, someone else's amendment
  • You have the notification: its number, the date of the Gazette, the paragraph that makes the change and the Gazette link.

Draft the change#

  1. On Home, choose Record a change and find the rule. Can be changed here groups them as start dates, time limits, thresholds, lists, wording and rules your team wrote. Needs a product update lists the product's own checks.
  2. Choose Change and enter the new value. For a list, tick the entries the product understands and reword them, or write each entry with its key. Anything but a date also needs the day it takes effect.
  3. Enter the notification: number, Gazette date, paragraph and link. The link must start https://.
  4. Say why the rule changes. If the change applies from a day already past, confirm it.
  5. Read What it changes: the open cases and projects it touches, counted across the deployment.
  6. Choose Send for approval, or Save draft to finish later.

Approve it#

  1. The second person sees it under Changes to check on Home, or opens Changes. The tab shows how many wait for them.
  2. They open the change, check the notification against its Gazette link and choose Approve and publish, or Send back with a note.

Publishing makes a new rules version, such as 2026.2+1. Within a minute every DPDP Act check uses it. Within a few minutes each project that saw the earlier rule set receives one ruleset.changed webhook and a notice on its check page.

A period takes effect from its date. A request takes the value in force on the day it is received, and a breach the one in force when the business became aware. Cases already open keep their deadlines.

A list or wording applies the same way: a form is checked against the notice elements in force when it is published. The DPDP rule set says what reads each rule.

Take a change back#

Open the published change on Changes and choose Undo this change. Give the reason and, if there is one, the notification that rescinds it. A second person approves the undo like any change. The original stays in the history, and the rule returns to what it was before.

What is kept#

History lists every rule set the deployment has run under, kept whole. Each record kept under the law stores the id of its version.

Each step is written to the audit log under the resource law-amendment: law.amendment.draft, law.amendment.update, law.amendment.submit, law.amendment.return, law.amendment.discard and law.amendment.publish. A publication records the versions before and after, who drafted and who approved. These entries carry no project.

The platform key reads the rule set at GET /v1/api/platform/ruleset but cannot change it.

↑↓ to move, Enter to open