Summary
Feature request: Global (platform-wide) settings should only be accessible from the "Manage Project" page, not interleaved with project settings in the main settings flow. This creates clear separation between what affects the current project vs. what affects the entire platform.
Why
Today global and project settings live in the same settings UI, which makes it easy to confuse scope — a user changing what they think is a project value may actually be changing a platform-wide default (and vice versa). Confining global settings to the Manage Project surface gives a clear, deliberate boundary:
- Project settings = effective for this project only.
- Global settings (Manage Project) = effective platform-wide.
This pairs with the request to mirror settings across scopes (#see companion issue): once the same fields exist at both scopes, the location becomes the disambiguator.
Environment
Summary
Feature request: Global (platform-wide) settings should only be accessible from the "Manage Project" page, not interleaved with project settings in the main settings flow. This creates clear separation between what affects the current project vs. what affects the entire platform.
Why
Today global and project settings live in the same settings UI, which makes it easy to confuse scope — a user changing what they think is a project value may actually be changing a platform-wide default (and vice versa). Confining global settings to the Manage Project surface gives a clear, deliberate boundary:
This pairs with the request to mirror settings across scopes (#see companion issue): once the same fields exist at both scopes, the location becomes the disambiguator.
Environment