Settings pages (Models, Tools, Channels and others) write the operator's own org's copy of each resource. An admin of a second org who opens Settings > Models writes that org's provider-settings and model-aliases. The runtime ignores most of those writes, and the rest are org settings that belong under /org. Done when instance-only Settings pages are hidden from members of other orgs and the server refuses writes to instance-only kinds from any org but the system org.
Server side done: instance-only kinds are refused from non-system orgs. Hiding the pages is tracked in the follow-up bead.
Imported from beads archie-core-f5zso · GitHub #1584 · type bug · priority P2 · created 2026-10-10 · closed 2026-10-13
Settings pages (Models, Tools, Channels and others) write the operator's own org's copy of each resource. An admin of a second org who opens Settings > Models writes that org's provider-settings and model-aliases. The runtime ignores most of those writes, and the rest are org settings that belong under /org. Done when instance-only Settings pages are hidden from members of other orgs and the server refuses writes to instance-only kinds from any org but the system org.
### Acceptance criteria
Non-system org admins cannot access instance-only Settings pages or write instance-only resource kinds.
### Close reason
Server side done: instance-only kinds are refused from non-system orgs. Hiding the pages is tracked in the follow-up bead.
---
_Imported from beads `archie-core-f5zso` · GitHub #1584 · type bug · priority P2 · created 2026-10-10 · closed 2026-10-13_
sam
added the mediumbug labels 2026-10-27 13:39:53 +00:00
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Settings pages (Models, Tools, Channels and others) write the operator's own org's copy of each resource. An admin of a second org who opens Settings > Models writes that org's provider-settings and model-aliases. The runtime ignores most of those writes, and the rest are org settings that belong under /org. Done when instance-only Settings pages are hidden from members of other orgs and the server refuses writes to instance-only kinds from any org but the system org.
Acceptance criteria
Non-system org admins cannot access instance-only Settings pages or write instance-only resource kinds.
Close reason
Server side done: instance-only kinds are refused from non-system orgs. Hiding the pages is tracked in the follow-up bead.
Imported from beads
archie-core-f5zso· GitHub #1584 · type bug · priority P2 · created 2026-10-10 · closed 2026-10-13