# Page: Parent and Child Objects

## Purpose

This page explains how the platform organizes related records through parent and child relationships so users can understand the structure behind fraud and AML workflows.

## What parent and child objects mean

A parent object is a higher-level record that contains or groups related information. A child object is a detailed record that belongs to that parent context.

### Example

- A case can be the parent object for investigation details, notes, and activity history.
- A score or alert can be a child object that is attached to a larger investigation or workflow.
- A rule or model can be the parent object for configuration details and related conditions.

## How users should think about them

When reviewing the UI:

- start with the parent object to understand the overall context;
- then open child objects to inspect the detail that supports the decision;
- use the relationship between them to trace why an action was taken.

## Example usage

Example: a user opens a case and then reviews the related score details and investigation notes that belong to that case. The case provides context; the child records provide evidence.

## Operational guidance

- use the parent record to understand the broader business context;
- use child records to validate the decision or investigate an alert;
- keep the relationship in mind when updating status, assigning follow-up, or making a rule change.

## Notes

Understanding object relationships is essential for accurate investigations and for preventing users from treating a single alert or detail in isolation.