The atlas of your data.
One catalogue of every object and field — 252 objects across 18 modules — each with an owner, a PII flag and a residency.
Overview
You cannot govern what you cannot see. The Object Registry is a catalogue of all 252 objects and their fields across the platform's 18 modules, treated as data the platform itself can query. Each entry records the object name, its pillar and department, how many fields it holds, how many are PII, where it resides and who owns it.
This turns governance from tribal knowledge into a living inventory. When a new object is added or a field changes, the registry is the single place that answers what data exists, its sensitivity and its steward. It is the foundation the residency, masking, quality and privilege rules all point back to, keeping the whole platform documented and reviewable.
Explore Data & Privileges →- ✓ One catalogue of all 252 objects across 18 modules
- ✓ PII field counts and density surfaced per object
- ✓ Owner and last-reviewed date for every entry
- ✓ Pillar and department classification for each object
- ✓ Residency and status tracked alongside each object
- ✓ Searchable atlas the whole governance model points to
Everything Object Registry gives you
Object Catalogue
All 252 objects across 18 modules are defined once in the registry with their name, pillar and department in one governed place.
Field Inventory
See the full field count for each object and drill into what data it actually stores.
PII Flagging
Track how many fields hold personal data and the PII density of each object at a glance.
Ownership & Stewards
Assign an owner to every object so accountability for its data is never ambiguous.
Residency Reference
Each object records where its data resides, linking the catalogue to residency rules.
Review Status
Capture last-reviewed dates and status so the inventory stays current and auditable.
How the AI agent uses the registry
The Flow-Cognition Agent helps keep the catalogue current, and every suggestion is logged.
Sense
Flags new fields that look like personal data.
Decide
Lists objects with no owner or an overdue review.
Act
Drafts the review reminder for each steward, and logs every suggestion.
Five-tier model routing · field-level permissions · full audit trail. See the AI layer →
Live in four steps
Register Objects
Every object is defined once in the registry with its pillar, department and field list.
Classify Data
Flag PII fields, set residency and record the sensitivity of each object.
Assign Owners
Give each object a steward accountable for its data and its rules.
Review Regularly
Track last-reviewed dates and status to keep the catalogue trustworthy over time.
Where teams put it to work
DPDP data mapping
A privacy team needs to know every place personal data is held; the registry lists each object, its PII fields and residency in one queryable view.
Onboarding a data steward
A new owner inherits an object and instantly sees its fields, sensitivity and last review, instead of piecing it together from scattered docs.
Governance gap audit
Leaders spot objects that are past due for review or missing an owner, closing documentation gaps before an audit finds them.
The payoff
Complete data visibility
Every object and field is documented in one place, so nothing your platform holds is invisible.
Faster compliance mapping
PII flags and residency per object make DPDP data-mapping and audit responses far quicker.
Clear accountability
Named owners and review dates mean every object has a steward answerable for its data.
A single source of truth
Residency, masking, quality and privilege rules all reference one authoritative catalogue.
Questions, answered
A catalogue entry for every object the platform holds — 252 objects across 18 modules — including each object's name, pillar, department, total fields, PII field count, residency, owner, last-reviewed date and status.
It surfaces which objects contain personal data and how much, which is the starting point for data mapping, residency decisions and responding to data-subject requests under the DPDP Act.
Objects are defined in the registry as they are created, and it captures review status and last-reviewed dates so stewards can keep entries current and flag anything overdue.
It is a measure of how much of an object's data is personal, derived from its PII field count relative to its total fields, helping you prioritise the most sensitive objects for governance.
It is the reference point. Residency rules, masking rules, data-quality rules and field permissions all attach to objects and fields defined in the registry, keeping governance consistent.
See Object Registry in your workflow
Start free, or get a guided walkthrough with our team — on the one platform that runs Data & Analytics and your whole business.