Reorganize settings page navigation and contents
Open
@artonge is already working on this.
Since Aug 31, 2026.
design
feature: settings
overview
- Dominant language
- PHP
- Stars
- 36.9k
- Forks
- 5.2k
- Avg merge
- 2d 3h
- Merged PRs (30d)
- 713
Description
Results of the design review for settings (05.08.2025) with the design team.
Navigation
- Create separation under admin settings
- Core
- Apps
- everything else
- Add search in navigation (or search everywhere in settings?)
- Navigation resets scroll on navigating, should retain scroll position
Personal settings
- Personal info ( https://github.com/nextcloud/server/pull/61358 )
- Language, locale, and day of the week doesn't fit w the rest, move somewhere else
- Organize everything into sections and have a single column instead of a multicolumn layout
- Security ( https://github.com/nextcloud/server/issues/63454 )
- Adjust and limit width
- Move devices and sessions to mobile and desktop?
- App password is difficult to reach, move somewhere else @nickvergessen thoughts for this and the previous point, as we are moving things out of the security section?
- Make it easier to log in with qr code ref https://github.com/nextcloud/server/issues/44603 -
- Notifications
- reduce width between mail and push columns
- External storage
- move below in the navigation
- Mobile and desktop
- move below security section
- update the android banner
- rename to something more general --> Apps and clients?
Admin settings
- Artificial intelligence
- Rename to Assistant and use assistant icon @DaphneMuller what are your thoughts?
- organize everything to one line each:
task name [toggle] [dropdown] - move context chat here
- Admin privileges page should be moved somewhere else
- Context chat
- table looks very technical, update with better design
- move to AI section
- combine Activity and Notifications into one section
- AppAPI
- Improve subline to be more informative
- Left align everything
cc @jancborchardt @kra-mo @marcoambrosini
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.
Assessment
This issue has not been assessed yet.