The orgs/workspaces/memberships model exists in the State Store (internal/domain/org) but nothing exposes it: no HTTP API, no page, and the dashboard session acts as the system identity via the shared token, so roles and Cedar policies never apply to the operator. Done when an operator can see their org, its members and roles, act as a person in it, and pick identities from it.
Imported from beads archie-core-kgxw · GitHub #1280 · type epic · priority P1 · created 2026-10-05
The orgs/workspaces/memberships model exists in the State Store (internal/domain/org) but nothing exposes it: no HTTP API, no page, and the dashboard session acts as the system identity via the shared token, so roles and Cedar policies never apply to the operator. Done when an operator can see their org, its members and roles, act as a person in it, and pick identities from it.
---
_Imported from beads `archie-core-kgxw` · GitHub #1280 · type epic · priority P1 · created 2026-10-05_
Triaged: no code change is needed for this. No code change is needed. The issue is a stale epic: every condition it lists is already implemented in this tree, and shipped in the changelog.
What the issue claims vs. what is here:
"no HTTP API" — wrong. internal/webui/orgs.go registers GET /api/orgs, POST /api/orgs, GET /api/orgs/{id}, GET/POST /api/orgs/{id}/workspaces, GET/POST /api/orgs/{id}/members, PUT/DELETE /api/orgs/{id}/members/{identity}, GET /api/orgs/{id}/agents, PUT /api/orgs/{id}/agents/{identity} (instance-only), plus PUT /api/orgs/current for org selection (server.go:343-345). Tested by TestOrgRoutes, TestOrgMembershipNeedsItsRole, TestInstanceAdminOrgs, TestOrgMemberAdd, TestOrgSelection in internal/webui/orgs_test.go.
"no page" — wrong. ui/src/router/index.ts mounts OrgShell with /org overview, /org/members, /org/agents, /org/workspaces, /org/models; OrgMembersPage.vue renders each member's role with a role selector wired to setOrgMember/addOrgMember/removeOrgMember; OrgAgentsPage.vue assigns agent and service identities to the org.
"the dashboard session acts as the system identity via the shared token, so roles and Cedar policies never apply to the operator" — no longer true. webui/authorize.go resolves the request principal from the stored signed-in identity, applies the selected org (webui/org_selection.go) and evaluates Cedar before every handler; the shared token is only a fallback when no identity provider is configured (single-operator install), and CHANGELOG 1.54.0 records "The shared dashboard token is gone". docs/security/authorization.md already carries the org surface in its enforcement inventory with the regression tests that prove it.
"Done when an operator can see their org, its members and roles, act as a person in it, and pick identities from it" — the changelog's 1.47.0 section records exactly this delivery: "feat(org): org, workspace and membership API", "feat(access): the dashboard operator is a person owning org-sys", "feat(org): instance admins manage every org", "feat(ui): org area with members, agents, workspaces, access and tokens", "feat(ui): org switcher and new org for instance admins"; 1.56.0 extends it (per-org forge connections, schedules, alerts, channels, audit).
The one reading under which something would remain is "act as a person in it" meaning impersonation/act-as. There is no impersonation feature anywhere in the tree (the only match for "impersonat" is a prompt line telling the agent not to impersonate vendors). That would be a new feature request against a different issue, not this epic, and the issue body does not ask for it.
Recommendation: close issue 1418 as already delivered (fixed around 1.47.0, extended in 1.54.0/1.56.0). Not verified: the UI and e2e checks were judged from source, not run; no browser or database-driven test was executed in this triage.
If you do want impersonation, that needs its own scoped issue; if you want the stale body corrected first, file the scope note there.
Triaged: no code change is needed for this. No code change is needed. The issue is a stale epic: every condition it lists is already implemented in this tree, and shipped in the changelog.
What the issue claims vs. what is here:
- "no HTTP API" — wrong. internal/webui/orgs.go registers GET /api/orgs, POST /api/orgs, GET /api/orgs/{id}, GET/POST /api/orgs/{id}/workspaces, GET/POST /api/orgs/{id}/members, PUT/DELETE /api/orgs/{id}/members/{identity}, GET /api/orgs/{id}/agents, PUT /api/orgs/{id}/agents/{identity} (instance-only), plus PUT /api/orgs/current for org selection (server.go:343-345). Tested by TestOrgRoutes, TestOrgMembershipNeedsItsRole, TestInstanceAdminOrgs, TestOrgMemberAdd, TestOrgSelection in internal/webui/orgs_test.go.
- "no page" — wrong. ui/src/router/index.ts mounts OrgShell with /org overview, /org/members, /org/agents, /org/workspaces, /org/models; OrgMembersPage.vue renders each member's role with a role selector wired to setOrgMember/addOrgMember/removeOrgMember; OrgAgentsPage.vue assigns agent and service identities to the org.
- "the dashboard session acts as the system identity via the shared token, so roles and Cedar policies never apply to the operator" — no longer true. webui/authorize.go resolves the request principal from the stored signed-in identity, applies the selected org (webui/org_selection.go) and evaluates Cedar before every handler; the shared token is only a fallback when no identity provider is configured (single-operator install), and CHANGELOG 1.54.0 records "The shared dashboard token is gone". docs/security/authorization.md already carries the org surface in its enforcement inventory with the regression tests that prove it.
- "Done when an operator can see their org, its members and roles, act as a person in it, and pick identities from it" — the changelog's 1.47.0 section records exactly this delivery: "feat(org): org, workspace and membership API", "feat(access): the dashboard operator is a person owning org-sys", "feat(org): instance admins manage every org", "feat(ui): org area with members, agents, workspaces, access and tokens", "feat(ui): org switcher and new org for instance admins"; 1.56.0 extends it (per-org forge connections, schedules, alerts, channels, audit).
The one reading under which something would remain is "act as a person in it" meaning impersonation/act-as. There is no impersonation feature anywhere in the tree (the only match for "impersonat" is a prompt line telling the agent not to impersonate vendors). That would be a new feature request against a different issue, not this epic, and the issue body does not ask for it.
Recommendation: close issue 1418 as already delivered (fixed around 1.47.0, extended in 1.54.0/1.56.0). Not verified: the UI and e2e checks were judged from source, not run; no browser or database-driven test was executed in this triage.
If you do want impersonation, that needs its own scoped issue; if you want the stale body corrected first, file the scope note there.
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.
The orgs/workspaces/memberships model exists in the State Store (internal/domain/org) but nothing exposes it: no HTTP API, no page, and the dashboard session acts as the system identity via the shared token, so roles and Cedar policies never apply to the operator. Done when an operator can see their org, its members and roles, act as a person in it, and pick identities from it.
Imported from beads
archie-core-kgxw· GitHub #1280 · type epic · priority P1 · created 2026-10-05Triaged: no code change is needed for this. No code change is needed. The issue is a stale epic: every condition it lists is already implemented in this tree, and shipped in the changelog.
What the issue claims vs. what is here:
The one reading under which something would remain is "act as a person in it" meaning impersonation/act-as. There is no impersonation feature anywhere in the tree (the only match for "impersonat" is a prompt line telling the agent not to impersonate vendors). That would be a new feature request against a different issue, not this epic, and the issue body does not ask for it.
Recommendation: close issue 1418 as already delivered (fixed around 1.47.0, extended in 1.54.0/1.56.0). Not verified: the UI and e2e checks were judged from source, not run; no browser or database-driven test was executed in this triage.
If you do want impersonation, that needs its own scoped issue; if you want the stale body corrected first, file the scope note there.