Skip to content

feat: configurable user profile information - #5

Merged
Yniphe merged 3 commits into
mainfrom
feat/profile-display
Oct 7, 2026
Merged

Yniphe merged 3 commits into
mainfrom
feat/profile-display

Conversation

@Yniphe

@Yniphe Yniphe commented Oct 7, 2026 •

Copy link
Copy Markdown
Contributor

Profiles can now show selected custom user fields and values reached through single-record relationships. For example, an administrator can show a department name and its manager in both the account profile and the user editor without copying data or hardcoding collection names.

A superuser configures up to 12 rows in Users → Profile display, including their labels, order and explicit visibility to the profile owner. Users with users/read can read configured rows in user cards; owners receive only rows enabled for them. This grants access only to the selected values, not to the underlying directories or editing. Sensitive fields, built-in user columns and unsupported relationship targets are excluded. Changed or replaced source bindings stop disclosing their values until reconfigured.

The change includes an additive configuration migration, typed HTTP contracts and OpenAPI, Russian/English UI copy, and authorization regression coverage. Existing installations start with an empty configuration. No demo data is included.

Validation: 493 Core tests passed (3 optional checks skipped), all 143 UI tests passed, and the focused profile/relationship suite passed 16 tests. Typecheck, lint, formatting, application/documentation builds and package archives installed in a clean consumer passed. Local browser checks covered configuration saving, account and user-card display, and a 390 px viewport. GitHub CI passed the complete checks, split-container smoke test and Helm chart/routing validation.

@Yniphe
Yniphe merged commit 1e90bed into main Oct 7, 2026
2 checks passed
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