Repository navigation
feat(list): show the person's own level beside the key's access, by level (v2.15.0) - #240
Merged
Merged
Conversation
…evel (v2.15.0) Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
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>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
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 listonly 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 listreads the person's level fromGET /v1/connections, which carriesviewerAccessLevel(#1195 in pica-v2). The vault route it already lists from does not.viewerAccessLevel(the server's value, as the MCP sends it) andeffectiveLevel: what a call can really do under both the key and the person's level.accesslevels (["read"]beside["GET"]), as the MCP's does, andlevelis judged by level.["GET","POST"]now reads Read & write instead of Custom, andwrite-onlyjoins the levels.Not in this PR
actions findstill offers actions the key or share can't run. Filtering likely belongs on the server, where it would also close the MCP'sfindgap from PICA-1727.actionspolicy still carry no level of their own; they needaccessin the knowledge cache.Testing
heldLevel(key against share, custom and none cases), level-based naming, andlistViewerLevelspaging and an older backend.main(mem migrate,resolveConfig, sync).viewerAccessLevelandeffectiveLevel, allfullon an admin account. With one share faked toread, the table shows Access "Full access", Your level "Read only", and agent outputeffectiveLevel: "read-only".🤖 Generated with Claude Code