Modunexmodunex
Scope & Inheritance

Inheritance Rules

Rules that determine which data is inherited automatically, which is optional, and which is never inherited.

What is it?

The rules that govern how data flows from company to project. They determine what a project receives automatically, what it can choose to inherit, and what it must always define on its own.

The rules

Data flows from company to project following three simple rules:

  • Inherited automatically — the directory, roles, fieldsets, and workflows are inherited by default by every project.
  • Optional inheritance — some standards can be inherited or redefined per project, at the administrator's discretion.
  • Never inherited — project-specific data such as project settings, team assignments, and operational items is never inherited; each project defines its own.
CompanyDirectoryRolesFieldsetsWorkflowsProjectNever inheritedProject settingsTeam · Operational itemsInherited automaticallyOptional inheritancePer-project standardsSame element on both scopes → Project value wins
Directory, roles, fieldsets and workflows are inherited by default. Project-owned data is never inherited.

Conflict resolution

When the same element exists at both company and project scope, the project value takes precedence within that project. Removing the project override restores the inherited company value.

If a project should follow the company standard, simply leave the element inherited — do not create a project override.