[Bug]: role and organisation are not editable with disabled profiles
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 36.9k
- Forks
- 5.2k
- Avg merge
- 2d 3h
- Merged PRs (30d)
- 713
Description
⚠️ This issue respects the following points: ⚠️
- This is not a troubleshooting question, general support matter, or webserver/proxy problem, but likely a bug (if unsure, ask the Community Help Forum).
- This issue is not already reported on Github OR solved at the Community Help Forum (I've searched!).
- I'm using a maintained major version of Nextcloud Server and tested against the latest patch level. (Supported major versions and current patch levels).
- I agree to follow Nextcloud's Code of Conduct.
- I've tried my best to provide clear reproduction steps that someone unfamiliar with this bug could use to reproduce it.
Bug description
Before disabling profiles in the server config, one was able to specify the role and organisation in /setting/user . But, after disabling profiles, those fields disappeared .
This shouldn't happen, I still want to be able to edit all fields because the contents are shown in /app/contacts
Steps to reproduce
- add to the config.php
'profile.enabled' => false, - try to edit the role and organisation in your user profile
Expected behavior
The field to edit the role and organisation are still available.
Nextcloud Server version
33
Operating system
Debian/Ubuntu
PHP engine version
PHP 8.3
Web server
Nginx
Database engine version
PostgreSQL
Is this bug present after an update or on a fresh install?
No response
Are you using the Nextcloud Server Encryption module?
Encryption is Disabled
What user-backends are you using?
- Default user-backend (database)
- LDAP/ Active Directory
- SSO - SAML
- Other
Configuration report
List of activated Apps
Admin Cockpit — 1.3.7
Announcement Banner — 2.4.3
Deck — 1.17.4
Forms — 5.3.5
Tables — 2.2.2
Activity — 6.0.0
Announcement center — 7.5.0
Antivirus for files — 6.4.0
Auditing / Logging — 1.23.0
Bookmarks — 16.2.6
Brute-force settings — 6.0.0
Calendar — 6.5.4
Calendar Resource Management — 0.12.2
Client Push — 1.4.0
Collaborative tags — 1.23.0
Collectives — 4.6.0
Comments — 1.23.0
Contacts — 8.7.7
Custom CSS — 1.21.0
Custom menu — 5.3.0
Dashboard — 7.13.0
Deleted files — 1.23.0
External sites — 8.0.1
Federation — 1.23.0
File reminders — 1.6.0
File sharing — 1.25.2
Files download limit — 5.1.0
FormVox — 1.4.3
Full text search — 33.0.0
Full text search - Elasticsearch Platform — 33.0.0
Full text search - Files — 33.0.0
Guests — 4.9.0
Log Reader — 6.0.0
Mail — 5.11.3
Memories — 8.1.0
Monitoring — 5.0.0
Nextcloud All-in-One — 0.8.0
Nextcloud announcements — 5.0.0
Nextcloud Office — 10.3.0
Nextcloud Webhook Support — 1.5.0
Notes — 6.0.2
Notifications — 6.0.0
OTP Manager — 1.2.2
Password policy — 5.0.0
Passwords (Legacy Support Release) — 2026.7.10
Passwords Handbook — 2026.7.20
PDF viewer — 6.0.0
Photos — 6.0.0
Polls — 9.2.1
Preview Generator — 5.14.0
Privacy — 5.0.0
Recommendations — 6.0.0
Related Resources — 4.0.0
Share by mail — 1.23.0
Support — 5.0.0
Talk — 23.0.10
Tasks — 0.18.1
Team Folders — 21.0.15
TeamHub — 4.7.1
Teams — 33.0.0
Text — 7.0.1
Two-Factor TOTP Provider — 15.0.0
Update notification — 1.23.0
Usage survey — 5.0.0
User status — 1.13.0
Versions — 1.26.0
Weather status — 1.13.0
Whiteboard — 1.5.9
Nextcloud Signing status
> No errors have been found.
Nextcloud Logs
Additional info
Nexctcloud Hub 26 Winter (33.0.7) AIO
left part is the entry in the /apps/contacts
right part is editing the profile for the logged in user
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing how profile.enabled in config.php controls the user profile editor at /setting/user, then compare the role and organisation fields with how their values appear in /app/contacts. Reproduce the disabled-profile case and verify that both fields remain editable while other profile behavior is unchanged.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php
- Domain
- full-stack
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 65/100