Reorganize settings page navigation and contents

[nimishavijay]

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
  • 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
  • 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?
• 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

[nickvergessen]

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?

It's kind of dangerous, it breaks all user relevant documentation, screenshots and explanations where to find this exact thing 🙈
But I agree that it's a bad place. I found many people and sometimes even myself looking in "Mobile & Desktop" for adding a device. But that being said, would "Devices & Sessions" (like the list is currently called) be a better name than "Mobile & Desktop", matches naming on Github, Signal, Telegram and many more. For some others I found sections like "Password & Security" (what we basically currently have, but we don't say password because there are user backends (like our LDAP) that don't allow setting a password) and "Connected Devices".
"Connected devices" could then be the subsection header of the app-password-list.

I think all of them work fine, as long as there is no category that is conflicting in the meaning like there is in our case. If we move it out and still keep Security, it might be worth adding a link from there to the new section, so that it's easier to find?

And for adding a device I'm still dreaming of having a QR code option directly in the user menu top right, so you don't have to go anywhere into settings to begin with.

[kra-mo]

It's kind of dangerous, it breaks all user relevant documentation, screenshots and explanations where to find this exact thing 🙈

If we move it out and still keep Security, it might be worth adding a link from there to the new section, so that it's easier to find?

Yeah, just include a placeholder for the time being saying something like "Looking for app passwords? Find them in Devices & Sessions." with a link and it should be all good.

[DaphneMuller]

can this be closed? @lukasdotcom
edit sorry I missed this was a general overview issue

[jancborchardt]

@kra-mo do you have further issues about the settings that you looked into, or would you post results or mockups in here? :) This is possibly something we could pick up for 33.

[kra-mo]

@kra-mo do you have further issues about the settings that you looked into, or would you post results or mockups in here? :) This is possibly something we could pick up for 33.

So far, I've looked into app settings, not server ones but I will do the same with those. I will post them as individual issues once the components are available and the issues are actionable (so as to not have to update them if something changes on that front, which it still might).