Add Account Button & Ability to Switch Between Nextcloud Accounts (Web Version)
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 36.9k
- Forks
- 5.2k
- Avg merge
- 2d 3h
- Merged PRs (30d)
- 713
Description
Currently, there is no straightforward way to switch between multiple Nextcloud accounts within the web interface. This feature request proposes adding an "Account Button" to the Nextcloud web version, which will allow users to easily switch between their Nextcloud accounts without needing to log out and log back in.
Use Case:
Many users manage multiple Nextcloud instances (e.g., personal and work accounts) and would benefit from the ability to seamlessly switch between them without interrupting their workflow. This feature would increase productivity and provide a smoother user experience for those with multiple accounts.
Proposed Solution:
- Add a user-friendly Account Button in the web interface (e.g., in the top right corner).
- Clicking the Account Button would show a dropdown or modal listing the user's Nextcloud accounts.
- Users would be able to select an account from the list, and the interface would automatically switch to that account.
- Optionally, include the ability to add/remove accounts directly from the dropdown or modal interface.
- The switch should preserve session data where possible (e.g., avoiding the need to re-enter credentials for linked accounts).
Benefits:
- Enhanced User Experience: Users can switch accounts with just a click, making it easier to manage personal and work accounts.
- Increased Productivity: No more logging out and back in, which saves time.
- Convenience: Smooth account management within the Nextcloud web interface.
Additional Context:
- This feature is particularly useful for users who work with multiple Nextcloud instances, whether for personal, work, or collaborative purposes.
- It's also beneficial for Nextcloud admins managing several organizations or domains who need quick access to various accounts.
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
The issue names no files, tests, or entry points. Start by identifying the web interface and authentication/session areas involved, then clarify the account model, security requirements, and expected behavior before implementation; done should include an agreed account-switching design and validation of the complete user flow.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, php
- Domain
- authentication, frontend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100