Repository navigation
Create a Pure GUI Role Editor #1634
Description
Let's fully hide the JSON and allow driving the role from a pure GUI. Let's also allow full editing at both add and edit time to unify things. People can choose to drop to JSON if they want, which follows the pattern we have elsewhere with table schemas, etc.
Activity
feat(roles): edit a role's permissions in a visual editor, with JSON …
fix(roles): keep each role's draft its own, and block saving over a n…
fix(roles): don't save a malformed operations value when the instance…
feat(roles): edit a role's permissions in a visual editor, with JSON …
fix(roles): keep each role's draft its own, and block saving over a n…
fix(roles): don't save a malformed operations value when the instance…
feat(roles): edit a role's permissions in a visual editor, with JSON …
fix(roles): keep each role's draft its own, and block saving over a n…
fix(roles): don't save a malformed operations value when the instance…
dawsontoth commentedon Oct 14, 2026
Shipped in #1893, live in prod since v2.198.0. Add Role and Edit Role both open on a visual editor (role type, structure user, operations, table CRUD and attribute scoping), and Edit as JSON is the opt-in fallback, following the schema editor's toggle.
Still JSON-only, per #1893:
@computedand relationship attributes, because describe_all omits them;attribute_restrictionsroles;describeflag, which is preserved but not shown.There is also no table filter for very large schemas. Any of these can be a follow-up issue.
🤖 Generated by Anthropic Claude Code (Claude Opus 5.5); posted via @dawsontoth.