Understanding Scope
What "scope" means in Modunex and how it determines where each configuration applies.
What is scope?
Scope is the level at which a piece of configuration applies. In Modunex every configurable element — a role, a permission, a fieldset, a workflow — lives in one of two scopes. Company scope applies to the whole company and, by inheritance, to all of its projects. Project scope applies to a single project only.
How scope determines where configuration applies
- When you configure something at company scope, it becomes the default for every project of that company.
- When you configure something at project scope, it applies only to that project and can override the company default.
- If the same element exists at both scopes, the project value wins within that project.
Why it matters
Scope is what lets you define standards once and reuse them everywhere, while still adapting each project to its particular needs without duplicating data.
Continue with Company Scope and Project Scope.
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.
Company Scope
Configuration that applies to the whole company: roles, permissions, fieldsets, workflows, and the directory shared across all projects.