Do you need to file a feature request?
Feature Request Description
Two related frontend ideas around the auth/account UI. I'd like to check
interest before building anything.
-
A "Profile" page for the signed-in user. It would show their own account
info (username/email and role) and a Sign out action in one place, and let
them pick an avatar icon. Today a user can only see their identity in the
Admin → User Management table, and only if they're an admin - regular users
have no self-service "my account" view at all.
-
A small redesign of the Admin → User Management page. It works fine, but the
layout is fairly bare (a plain table). Some light polish - avatars, clearer
role badges, a search box, nicer empty/loading states - would make it scale
better as the user list grows.
These are independent; either could land on its own.
Related Module
Frontend/Web
Use Case
-
Profile: any signed-in user - especially non-admins, who never see the Admin
page - needs a single place to see who they're logged in as and to sign out,
without going through the admin table. Picking an avatar is a small
personalization touch that also helps tell users apart at a glance, which
matters more in multi-user deployments.
-
Admin page: as multi-user setups grow, the user list is easier to scan with
avatars, role badges and search, and friendlier empty/loading states make the
first-run experience clearer.
Additional Context
Current Admin → User Management for reference:
I already have a working local prototype of the Profile page (account info +
Sign out, wired to the existing /api/v1/auth/status and fetchAuthStatus),
and I'd be happy to open a PR if there's interest - including avatar selection
if we settle on where to store it.
A few open questions for you:
- Profile as its own route (e.g.
/profile) or a popover from the sidebar?
- Avatars: a predefined icon set, or uploaded images? Where should the choice
be persisted (the auth/user store)?
- Is an Admin redesign in scope right now, or would you rather keep it minimal?
Note: the app already has a SessionAvatar component, so there may be existing
groundwork to reuse for the avatar piece.
Do you need to file a feature request?
Feature Request Description
Two related frontend ideas around the auth/account UI. I'd like to check
interest before building anything.
A "Profile" page for the signed-in user. It would show their own account
info (username/email and role) and a Sign out action in one place, and let
them pick an avatar icon. Today a user can only see their identity in the
Admin → User Management table, and only if they're an admin - regular users
have no self-service "my account" view at all.
A small redesign of the Admin → User Management page. It works fine, but the
layout is fairly bare (a plain table). Some light polish - avatars, clearer
role badges, a search box, nicer empty/loading states - would make it scale
better as the user list grows.
These are independent; either could land on its own.
Related Module
Frontend/Web
Use Case
Profile: any signed-in user - especially non-admins, who never see the Admin
page - needs a single place to see who they're logged in as and to sign out,
without going through the admin table. Picking an avatar is a small
personalization touch that also helps tell users apart at a glance, which
matters more in multi-user deployments.
Admin page: as multi-user setups grow, the user list is easier to scan with
avatars, role badges and search, and friendlier empty/loading states make the
first-run experience clearer.
Additional Context
Current Admin → User Management for reference:
I already have a working local prototype of the Profile page (account info +
Sign out, wired to the existing
/api/v1/auth/statusandfetchAuthStatus),and I'd be happy to open a PR if there's interest - including avatar selection
if we settle on where to store it.
A few open questions for you:
/profile) or a popover from the sidebar?be persisted (the auth/user store)?
Note: the app already has a
SessionAvatarcomponent, so there may be existinggroundwork to reuse for the avatar piece.