New accounts on a self-hosted dev instance are flagged as staff

(#1050) Bug Closed: Fixed security self-hosting

Problem

For now, i set up an devenv for selfhost for testing. i tried to mess around a bit. and found out that if im registering a second account for testing, this account is automatically flagged as a staff member, i dont know if that is because of dev environment and if that is no longer the case if the environment is set at production.

Proposed solution

Everyone who registers should not be flagged as staff
  1. Rex changed the status from Shipped to Fixed
  1. The pull request fluxer#3469 mentions this post Merged

6 comments

Sign in with Fluxer to comment and vote.
Comment by Rex
RexSystem 1 vote
Status changed from Fixed to Needs triage
Reopened because it was closed only to ask for an issue and the problem was never looked at.
Comment by Rex
RexSystem 1 vote
Status changed from Needs triage to Fix pending
Fixed via #3469. New accounts are never flagged as staff, even when an instance runs in development mode. Ships in the next release.
Comment by Rex
RexSystem 1 vote
Status changed from Fix pending to Fixed
Fixed in api 2026.1014.200615, running in prod and on the v1 tag
Comment by @Divij-Bhoj
RexSystem 1 vote originally by @Divij-Bhoj on GitHub
Users who register through the normal registration process should not be automatically flagged as staff members. The default behavior should be: is_staff = False is_superuser = False Standard user role assigned by default Staff privileges granted only manually by an administrator This ensures proper role separation and prevents unintended privilege escalation.
Comment by glyph
glyph 1 vote 1 reply
Just happened to me on my self-hosted instance as well
Comment by glyph
glyph 1 vote
Yeah never mind - I just forgot to set FLUXER_ENV to production