> For the complete documentation index, see [llms.txt](https://docs.nxcframework.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.nxcframework.net/nexus-core-docs/configuring/scopes.md). # Who a setting applies to > **Available.** Scope precedence is implemented and in use. The interface for setting a value at a particular scope arrives with `nxc_devtools`. ## Precedence Lowest to highest. A value set at a higher scope overrides lower ones: ``` default package value → environment → server-wide published → resource → organization or business → location → permitted player preference ``` ## What each scope is for | Scope | Set by | Example | | ------------------------ | ----------------------------------- | -------------------------------------- | | Default | The resource's schema | A payout's shipped value | | Environment | Operator, per environment | Development versus production behavior | | Server-wide | Operator | A global economy multiplier | | Resource | Operator | Settings for one resource | | Organization or business | A business owner or department head | Opening hours for one business | | Location | Operator | Different pricing at one shop | | Player preference | The player | HUD element visibility | ## Which scopes a field allows A field declares which scopes may set it. Most operational fields are server-wide or resource scoped. Business hours are business scoped. A HUD preference is player scoped. A field that allowed player scope for a payout rate would let players set their own wages — so the allowed scopes are part of the field's security surface, not a convenience. ## Resolution Resolution happens **server-side**. Only fields marked client-visible are sent to a client, and only after resolution. **A security-sensitive value is never exposed to a client merely because it participates in resolution.** ## Effective-value preview Because a value can be set at seven levels, "what actually applies here?" is a real question. The effective-value preview answers it, showing the resolved value and which scope supplied it. Without this, an operator changing a server-wide value and seeing no effect has no way to discover that a business-level override is winning. ## Inheritance An unset scope inherits from the scope below. Setting a business-level value does not require setting every other business — they continue inheriting. Clearing a scope's value returns it to inheritance rather than to the schema default, which are different things when an intermediate scope is set. --- # 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.nxcframework.net/nexus-core-docs/configuring/scopes.md?ask=&goal= ``` `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.