GitHub user dosubot[bot] added a comment to the discussion: Custom User Info 
Fields and FAB User View Overrides No Longer Work in Superset v6 (React 
Migration)

<!-- Answer -->
Superset v6’s React User Info page does not support custom user fields or Flask 
AppBuilder (FAB) view overrides—these extension points were removed in the 
migration. The React component only displays and edits a fixed set of fields 
(username, roles, login count, first/last name, email), and there’s no config, 
hook, or documented workaround to restore custom fields in the UI or backend as 
of v6. The frontend ignores any customizations made in Python or via the 
security manager, and the API endpoint `/api/v1/me/` only returns the default 
attributes 
([source](https://github.com/apache/superset/blob/829e4d92d91ceae4b43b1ed3b063ffe45377799c/superset-frontend/src/pages/UserInfo/index.tsx#L82-L232),
 
[source](https://github.com/apache/superset/blob/829e4d92d91ceae4b43b1ed3b063ffe45377799c/superset-frontend/src/features/userInfo/UserInfoModal.tsx#L30-L140)).

There’s no official migration path or extension mechanism for organizations 
relying on custom FAB user views and fields. Supporting custom fields would 
require backend changes (to return and accept additional attributes in 
`/api/v1/me/`) and a frontend refactor to drive the UI from a configurable 
schema—none of which exist yet 
([source](https://github.com/apache/superset/issues/36549)). 

There are ongoing SIPs and roadmap discussions about making Superset more 
extensible and pluggable (e.g., plugin architecture, security model redesign), 
but these do not currently provide a solution for custom user fields in the 
User Info page 
([source](https://github.com/apache/superset/issues/32116#issuecomment-2657483490)).
 For now, organizations impacted by this change may need to maintain a fork or 
monitor SIP/plugin architecture progress for future extensibility.


<!-- Dosu Comment Footer -->
*To reply, just mention [@dosu](https://go.dosu.dev/dosubot).*

---
<sup>How did I do? 
[Good](https://app.dosu.dev/response-feedback/2fc5b0e5-5418-4333-8dc8-518a17e64527?feedback_type=great_response)
 | 
[Irrelevant](https://app.dosu.dev/response-feedback/2fc5b0e5-5418-4333-8dc8-518a17e64527?feedback_type=irrelevant_answer)
 | 
[Incorrect](https://app.dosu.dev/response-feedback/2fc5b0e5-5418-4333-8dc8-518a17e64527?feedback_type=incorrect_sources)
 | 
[Verbose](https://app.dosu.dev/response-feedback/2fc5b0e5-5418-4333-8dc8-518a17e64527?feedback_type=too_verbose)
 | 
[Hallucination](https://app.dosu.dev/response-feedback/2fc5b0e5-5418-4333-8dc8-518a17e64527?feedback_type=hallucination)
 | [Report 
🐛](https://app.dosu.dev/response-feedback/2fc5b0e5-5418-4333-8dc8-518a17e64527?feedback_type=bug_report)
 | 
[Other](https://app.dosu.dev/response-feedback/2fc5b0e5-5418-4333-8dc8-518a17e64527?feedback_type=other)</sup>

[![Chat with 
Dosu](https://dosu.dev/dosu-chat-badge.svg)](https://app.dosu.dev/a28d3c7e-a9d3-459e-9fb6-3a6f9ff4f357/ask?utm_source=github)&nbsp;[![Open
 in 
Cursor](https://dosu.dev/dosu-in-cursor.svg)](https://cursor.com/link/prompt?text=Superset%20v6%E2%80%99s%20React%20User%20Info%20page%20does%20not%20support%20custom%20user%20fields%20or%20Flask%20AppBuilder%20%28FAB%29%20view%20overrides%E2%80%94these%20extension%20points%20were%20removed%20in%20the%20migration.%20The%20React%20component%20only%20displays%20and%20edits%20a%20fixed%20set%20of%20fields%20%28username%2C%20roles%2C%20login%20count%2C%20first/last%20name%2C%20email%29%2C%20and%20there%E2%80%99s%20no%20config%2C%20hook%2C%20or%20documented%20workaround%20to%20restore%20custom%20fields%20in%20the%20UI%20or%20backend%20as%20of%20v6.%20The%20frontend%20ignores%20any%20customizations%20made%20in%20Python%20or%20via%20the%20security%20manager%2C%20and%20the%20API%20endpoint%20%60/api/v1/me/%60%20only%20returns%20the%20defau
 
lt%20attributes%C2%A0%28%5Bsource%5D%28https%3A//github.com/apache/superset/blob/829e4d92d91ceae4b43b1ed3b063ffe45377799c/superset-frontend/src/pages/UserInfo/index.tsx%23L82-L232%29%2C%C2%A0%5Bsource%5D%28https%3A//github.com/apache/superset/blob/829e4d92d91ceae4b43b1ed3b063ffe45377799c/superset-frontend/src/features/userInfo/UserInfoModal.tsx%23L30-L140%29%29.%0A%0AThere%E2%80%99s%20no%20official%20migration%20path%20or%20extension%20mechanism%20for%20organizations%20relying%20on%20custom%20FAB%20user%20views%20and%20fields.%20Supporting%20custom%20fields%20would%20require%20backend%20changes%20%28to%20return%20and%20accept%20additional%20attributes%20in%20%60/api/v1/me/%60%29%20and%20a%20frontend%20refactor%20to%20drive%20the%20UI%20from%20a%20configurable%20schema%E2%80%94none%20of%20which%20exist%20yet%C2%A0%28%5Bsource%5D%28https%3A//github.com/apache/superset/issues/36549%29%29.%20%0A%0AThere%20are%20ongoing%20SIPs%20and%20roadmap%20discussions%20about%20making%20Superset%20m
 
ore%20extensible%20and%20pluggable%20%28e.g.%2C%20plugin%20architecture%2C%20security%20model%20redesign%29%2C%20but%20these%20do%20not%20currently%20provide%20a%20solution%20for%20custom%20user%20fields%20in%20the%20User%20Info%20page%C2%A0%28%5Bsource%5D%28https%3A//github.com/apache/superset/issues/32116%23issuecomment-2657483490%29%29.%20For%20now%2C%20organizations%20impacted%20by%20this%20change%20may%20need%20to%20maintain%20a%20fork%20or%20monitor%20SIP/plugin%20architecture%20progress%20for%20future%20extensibility.)&nbsp;[![Join
 
Discord](https://img.shields.io/badge/join-5865F2?logo=discord&logoColor=white&label=)](https://go.dosu.dev/discord-bot)&nbsp;[![Share
 on 
X](https://img.shields.io/badge/X-share-black)](https://twitter.com/intent/tweet?text=%40dosu_ai%20helped%20me%20solve%20this%20issue!&url=https%3A//github.com/apache/superset/discussions/36925)

GitHub link: 
https://github.com/apache/superset/discussions/36925#discussioncomment-15425327

----
This is an automatically sent email for [email protected].
To unsubscribe, please send an email to: 
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to