[GH-ISSUE #172] Prevent Account Creation with "admin" Username and Resolve Routing Conflicts #114

New issue

Open

opened 2026-03-03 11:13:11 +03:00 by kerem · 0 comments

kerem commented

2026-03-03 11:13:11 +03:00

Owner

Originally created by @manikanta9176 on GitHub (May 19, 2025).
Original GitHub issue: https://github.com/dflow-sh/dflow/issues/172

Originally assigned to: @jagadeesh507 on GitHub.

If a user creates an account with the username "admin", the organization's routing will start with /admin.
This creates a conflict because /admin is already reserved for the PayloadCMS admin panel.
Due to Next.js routing, any route starting with /admin/ will be routed to the PayloadCMS admin panel instead of the intended organization route.
To resolve this issue, we need to:
- Prevent users from creating an account with the username "admin" and throw an error when attempting to do so.
- Check for any other potential conflicts with reserved routes or usernames and ensure they are properly handled to avoid similar routing issues.

Originally created by @manikanta9176 on GitHub (May 19, 2025). Original GitHub issue: https://github.com/dflow-sh/dflow/issues/172 Originally assigned to: @jagadeesh507 on GitHub. * If a user creates an account with the username "admin", the organization's routing will start with `/admin`. * This creates a conflict because `/admin` is already reserved for the PayloadCMS admin panel. * Due to Next.js routing, any route starting with `/admin/` will be routed to the PayloadCMS admin panel instead of the intended organization route. * To resolve this issue, we need to: * Prevent users from creating an account with the username "admin" and throw an error when attempting to do so. * Check for any other potential conflicts with reserved routes or usernames and ensure they are properly handled to avoid similar routing issues.