nextcloud / nextcloud/server

Separate Admin and User menu

Open
#50,621 6 comments 2 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

0. Needs triage design enhancement feature: files feature: settings feature: users and groups
Dominant language
PHP
Stars
36.9k
Forks
5.2k
Avg merge
2d 3h
Merged PRs (30d)
713

Description

How to use GitHub
  • Please use the 👍 reaction to show that you are interested into the same feature.
  • Please don't comment if you have no relevant information to add. It's just extra noise for everyone subscribed to this issue.
  • Subscribe to receive notifications on status change and new comments.

Is your feature request related to a problem? Please describe.
Clutter of the menu that includes both user and admin functions and is therefore limited to how many items it can hold so it doesn't feel overloaded.

Describe the solution you'd like
Split admin functions into another menu. The menu I'm talking about is the user avatar in the top-right.

  • The user menu (the avatar) would keep the link to View Profile, Set Status and include About & What's New, Help & Privacy and Logout. It would also include the most commonly accessed of the Settings items:

Image

  • The admin menu would then keep Accounts, Apps and then commonly used links from these:

Image

Describe alternatives you've considered
None

Additional context
None

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start at the top-right user avatar menu entry point described in the issue and inspect how its current user and administrative links are assembled. Done means separate menus match the requested grouping, including the specified profile, status, help, logout, accounts, apps, and settings links; no files or tests are named in the issue.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript, php
Domain
design, frontend
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.