Scope & Inheritance
Scope & Inheritance
Explains how Modunex manages configuration inheritance between company and project. This concept is key to understanding how the platform works and how to scale configuration efficiently.
Explains how Modunex manages configuration inheritance between company and project. This concept is key to understanding how the platform works and how to scale configuration efficiently.
For: Administrators · Project Directors
Section contents
| Page | Description |
|---|---|
| Understanding Scope | What "scope" means in Modunex and how it determines where each configuration applies. |
| Company Scope | Configuration that applies to the whole company. |
| Project Scope | Configuration that applies to a single project. |
| Inheritance Rules | Which data is inherited automatically, which is optional, and which is never inherited. |
| Best Practices | What to configure at company level vs. project level. |
General rule: configure at the company level everything reused across multiple projects. Configure at the project level everything specific to that job.