starred/panel-pelican-dev
1
0
Fork 0
mirror of https://github.com/pelican-dev/panel.git synced 2026-05-04 18:00:48 +03:00
Code Issues 41 Packages Projects Releases 10 Wiki Activity

Option to disable free username changes #443

New Issue
Closed
opened 2026-02-05 17:36:17 +03:00 by OVERLORD · 1 comment
OVERLORD commented 2026-02-05 17:36:17 +03:00
Owner
Copy Link

Originally created by @rmartinoscar on GitHub (Sep 21, 2025).

Originally assigned to: @Boy132 on GitHub.

Users shouldn't be able to change their username by default imo

Discussed in https://github.com/pelican-dev/panel/discussions/1725

Originally posted by Leon-JavaScript September 21, 2025
As I already suggested as a comment regarding this topic, I guess it would be nice to be able to disable users being able to change their own username, like it has already been done with the server description. (So it could be another miscellaneous setting in the admin tab.)

The reason I find it useful is

  1. In some setups, admins want specific username patterns (e.g., when thinking in the long term when the software releases, hosters may want to see by the username what client is associated with a specific account by, for example, including something like a client ID in the username).
  2. In private setups, you want to know which person you created an account for, so if they're now able to change their own username, you could lose track of which person is using which account.
Originally created by @rmartinoscar on GitHub (Sep 21, 2025). Originally assigned to: @Boy132 on GitHub. *Users shouldn't be able to change their username by default imo* ### Discussed in https://github.com/pelican-dev/panel/discussions/1725 <div type='discussions-op-text'> <sup>Originally posted by **Leon-JavaScript** September 21, 2025</sup> As I already suggested as a [comment](https://github.com/pelican-dev/panel/pull/1702#issuecomment-3281388199) regarding this topic, I guess it would be nice to be able to disable users being able to change their own username, like it has already been done with the server description. (So it could be another miscellaneous setting in the admin tab.) The reason I find it useful is 1. In some setups, admins want specific username patterns (e.g., when thinking in the long term when the software releases, hosters may want to see by the username what client is associated with a specific account by, for example, including something like a client ID in the username). 2. In private setups, you want to know which person you created an account for, so if they're now able to change their own username, you could lose track of which person is using which account.</div>
OVERLORD commented 2026-02-05 17:36:21 +03:00
Author
Owner
Copy Link

@Boy132 commented on GitHub (Sep 21, 2025):

Superseded by #1728

@Boy132 commented on GitHub (Sep 21, 2025): Superseded by #1728
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
not confirmed
pull-request
Mirrored from GitHub Pull Request
 👑 sponsor
💰 fund
🔴 hard
🟡 medium
🟡 medium
🟡 medium
🟢 easy
🟢 easy
🟢 easy
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
OVERLORD
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/panel-pelican-dev#443
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?