Decision Scope
Learn how organization, project, and repository scope determine where a decision applies.
DecisionOps organizes work as organization -> project -> repository. Understanding that hierarchy is the key to knowing where a decision applies, what appears in search results, and why two users in the same organization may see different repository-specific guidance.
Organization Scope
Organization scope is for shared defaults and broad governance decisions. If a decision is organization-scoped, it can act as guidance for all repositories in that workspace unless a more specific repository decision replaces or narrows it.
Repository Scope
Repository scope is for decisions that apply only to one codebase. These decisions are useful for service-level architecture choices, repository-specific delivery rules, and technical decisions that should not automatically affect every other project.
Projects
Projects group repositories inside an organization. They help teams organize related codebases and provide the context used by several IDE and admin workflows. A project does not replace repository scope. Instead, it helps users choose the right working set when installing an IDE integration, browsing repositories, or assigning ownership.
Inherited Reads
Repository views can include both repository-specific decisions and inherited organization decisions. This is useful when a repo needs to honor global standards while still keeping local decisions visible. Organization views, by contrast, focus on organization-wide records.