Skip to content

feat(list): show the person's own level beside the key's access, by level (v2.15.0) - #240

Merged
paulkr merged 1 commit into
mainfrom
feat/list-share-level
Nov 19, 2026
Merged

paulkr merged 1 commit into
mainfrom
feat/list-share-level

Conversation

@paulkr

@paulkr paulkr commented Nov 19, 2026

Copy link
Copy Markdown
Member

Closes PICA-1726.

Why

In an organization, an admin can share an app with a member at a lower level, or cap it with App Controls. one list only knew the key's access, so it said Full access on an app the person can only read, and every write failed with no explanation. It also named access by HTTP verb, so a POST search looked like a write, though One judges each action by its level.

What changed

  • one list reads the person's level from GET /v1/connections, which carries viewerAccessLevel (#1195 in pica-v2). The vault route it already lists from does not.
  • Agent output adds viewerAccessLevel (the server's value, as the MCP sends it) and effectiveLevel: what a call can really do under both the key and the person's level.
  • The table adds a "Your level" column, in the dashboard's words, only when some connection holds the person below Full access.
  • A methods policy now carries access levels (["read"] beside ["GET"]), as the MCP's does, and level is judged by level. ["GET","POST"] now reads Read & write instead of Custom, and write-only joins the levels.
  • An older backend that sends no level leaves the listing as it was.
  • Guide, skill and README updated.

Not in this PR

  • actions find still offers actions the key or share can't run. Filtering likely belongs on the server, where it would also close the MCP's find gap from PICA-1727.
  • Actions in an actions policy still carry no level of their own; they need access in the knowledge cache.

Testing

  • 7 new tests: heldLevel (key against share, custom and none cases), level-based naming, and listViewerLevels paging and an older backend.
  • Full suite: 862 tests, 22 fail, the same 22 as on main (mem migrate, resolveConfig, sync).
  • Built CLI against production: every connection gets viewerAccessLevel and effectiveLevel, all full on an admin account. With one share faked to read, the table shows Access "Full access", Your level "Read only", and agent output effectiveLevel: "read-only".
  • Not yet tested with a real member on a Read only share.

🤖 Generated with Claude Code

…evel (v2.15.0)

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
@linear

linear Bot commented Nov 19, 2026

Copy link
Copy Markdown

PICA-1726

@paulkr
paulkr merged commit 1fcbb09 into main Nov 19, 2026
8 checks passed
@paulkr
paulkr deleted the feat/list-share-level branch November 19, 2026 03:25
paulkr added a commit to RachitSrivastava12/cli that referenced this pull request Nov 19, 2026
main moved to 2.15.0 (withoneai#240); this fix ships as the next patch.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant