> For the complete documentation index, see [llms.txt](https://docs.yansalabs.com/simple-data-separation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.yansalabs.com/simple-data-separation/technical-docs/separation-rules/parent-inheritance-beta.md).

# Parent Inheritance (BETA)

{% hint style="info" %}
**Parent Inheritance** lets you apply data separation of a parent table to related tables, making it easy to implement data segregation across a complex table hierarchy. For example, *"I want to restrict Incident Tasks so that users only see tasks related to their assigned Incidents."*
{% endhint %}

**Details:**

* Inheritance will follow through parents/grandparents/etc, as long as each table in the hierarchy has 'Follow parent' enabled on its own Separation Rule. This enables inclusive inheritance across multi-level relationships.
* Inherited fields on children will automatically be updated when the parent is changed - no need to make redundant changes.
* Only the selected components will be inherited (separator fields, owners overrides, visibility groups). Selecting 'Follow parent' alone will add a Separation Rule to a record inheritance hierarchy, but will not add any new parameters to data segregation for the table.
* You can add additional data separation criteria to a Separation Rule normally. Parent Inheritance is additive.

<figure><img src="/files/HcWfwVaQj0xzX0AhzxXB" alt=""><figcaption><p>Parent Inheritance Configuration (on Separation Rule)</p></figcaption></figure>

* **Follow parent**: Enable this Separation Rule to inherit from a parent Separation Rule
* **Parent field**: Field on the target table that references the 'parent' record
* **Auto-detect parent rule**: Automatically detect the parent separation rule based on the parent field selected (recommended)
* **Parent separation rule**: Separation rule for the 'parent' table
  * While auto-detection is recommended, you can manually set a parent separation rule. Messages will be displayed on the form when potential misconfigurations are detected.
* **Inherit separator fields:** Inherit separator fields from the parent separation rule
  * Defined relationships will also be inherited from the parent.
  * Selective application of the separator field will be inherited only if there is an aggregate single separation field on the rule after inheritance.
* **Parent separator fields:** Fields inherited for data separation (includes dot-walk to parent/grandparent/etc)
* **Inherit owner overrides:** Inherit owner overrides from the parent separation rule
* **Parent owner overrides:** Fields inherited for owner override (includes dot-walk to parent/grandparent/etc)
* **Inherit visibility groups:** Inherit visibility groups from the parent separation rule
* **Parent visibility groups:** Values inherited for visibility groups

{% hint style="info" %}
Multi-level inheritance can reduce query efficiency. You can set the maximum level of inheritance in [General Settings](/simple-data-separation/technical-docs/general-settings.md).
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.yansalabs.com/simple-data-separation/technical-docs/separation-rules/parent-inheritance-beta.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.