Tools Availability For The Step 3.7 Flash Model Hugging Face users are seeking clarity on renaming organization namespaces, with public forum threads and UI elements suggesting a self-service path via Account settings, though the Organization Username field appears read-only for non-admins. Audit logs document an org.rename event, but official documentation focuses on repository-level changes, leaving organization rename policy ambiguous. Longer notes, links, and things worth checking 1. Why website@huggingface.co seems like a reasonable route For regular community account / name / ownership issues, website@huggingface.co appears in several public forum/docs references. Examples: So, for a normal non-Enterprise org rename request, emailing website@huggingface.co looks plausible to me. For Team/Enterprise setups there may be other support paths, but I would not assume those apply to every community org. 2. Personal username vs organization username There are two different issues that are easy to mix up: | Case | What seems publicly documented / discussed | | Personal username | A forum thread says the Hub UI allowed a one-time username change. | | Organization display name | This may only change the visible profile name. | | Organization username / namespace | This is the part used in URLs and repo IDs, like org-name/model-name . This is the relevant thing for models, datasets, and Spaces. | The personal username thread is here: How do I change my username or email? https://discuss.huggingface.co/t/how-do-i-change-my-username-or-email/8855 For orgs, the most relevant public forum clue I found is this 2023 reply from HF staff: Change organization name case and case-sensitive model paths https://discuss.huggingface.co/t/change-organization-name-case-and-case-sensitive-model-paths/35017 In that thread, the issue was that changing Profile → Organization name did not affect the model path. The staff reply said the user needed to change Account → Org username instead. That strongly suggests that, for org namespace/path changes, the relevant setting is not the Profile display name but the Account-level organization username. 3. Current UI observation In the current org settings UI, there is an Organization Username field under the Account tab. The help text says that this value is present in the URL and serves as the namespace for models, datasets, and Spaces. However, in my case the field was read-only. I am not an admin of that organization, so I cannot tell whether: - org admins can still edit it self-service; - only some orgs can edit it; - it is editable only once; - it is currently support-only; - or it is intentionally displayed but locked for some other reason. So the useful check is: | Check | Meaning | Can an org admin open Organization settings → Account ? | Confirms the correct settings page. | Is Organization Username editable for that admin? | Confirms whether self-service rename works today. | | Is there a warning, validation error, or disabled state? | May indicate once-only, conflict, policy, or support-only behavior. | | Is the desired namespace already taken? | Namespace conflicts may require support. | 4. Traces that org rename exists or existed I cannot confirm current HF policy, but there are several public traces that organization rename exists or existed in some form. | Public trace | Why it matters | | 2021 org rename discussion | HF staff discussed renaming an org and its models. | 2023 Account → Org username staff reply | Suggests a UI path for changing the org namespace/path. | | Current UI field | The Organization Username field still appears in org Account settings. | | Audit log docs | org.rename appears as an audit-log event. | Relevant links: The audit log docs do not prove that every user can rename every org from the UI. They only show that org.rename is a recognized organization-management event in the Hub’s event model. 5. Important caveat: repo rename docs are not necessarily org rename docs For repository-level rename/transfer, the official docs are fairly clear: Repository Settings · Hugging Face https://huggingface.co/docs/hub/repositories-settings Those docs say that transferring or renaming a repo automatically redirects the old URL to the new location and preserves download counts and likes. But that is about a single repository . I would not automatically infer that a whole-organization namespace rename has exactly the same redirect behavior. That distinction matters because an org namespace rename could affect many things at once: - model repo IDs; - dataset repo IDs; - Space repo IDs; - Space direct URLs; - git remotes; - READMEs / model cards / dataset cards; - Colab notebooks; - CI scripts; from pretrained ... ; load dataset ... ; hf hub download ... ; - webhooks; - inference endpoints; - tokens / secrets / variables that contain hardcoded repo IDs. There is also a recent related forum question specifically asking about org rename redirects and impact: Clarification on organization rename impact and redirects https://discuss.huggingface.co/t/clarification-on-organization-rename-impact-and-redirects/176576 That thread asks the key question: whether old model/dataset/Space URLs and old repo IDs continue working after an org rename. 6. Historical warning: old org rename behavior may not have had redirects In the older 2021 org rename discussion, HF staff said that renaming the org would also rename the models, and that users would need to update their git remote URLs because there was no redirection system for that case at that time: Delete organizations / models from the Hub - 48 by pierric https://discuss.huggingface.co/t/delete-organizations-models-from-the-hub/954/48 That is old information. It may not describe the current Hub behavior. But it is still useful as a caution: I would not assume org namespace redirects unless HF staff or current behavior confirms it. 7. Suggested test matrix if the rename becomes possible If HF support or the UI allows a rename like: php DZER-Studios - Vexion-LM I would test both the old and new namespace explicitly. | Area | Old form to test | New form to test | | Model page | https://huggingface.co/DZER-Studios/