Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Streamline New Role Configuration and Assignment Workflow #3969

Open
ghislaineguerin opened this issue Oct 17, 2024 · 0 comments
Open

Streamline New Role Configuration and Assignment Workflow #3969

ghislaineguerin opened this issue Oct 17, 2024 · 0 comments
Labels
affects: ux Related to user experience needs: requirements The problem is clear and worth solving, but we're not yet sure of the best solution needs: ux design type: bug Something isn't working type: enhancement New feature or request

Comments

@ghislaineguerin
Copy link
Contributor

Description

When users add a new login role in the database settings, they must then navigate to the role configuration to enter a password before the role appears in the collaborator role selection list. This additional step can be confusing, as users may not realize it's necessary. It also disconnects them from their primary goal of adding a new role for a collaborator, whether existing or new.

Expected behavior

Users should be able to add a new collaborator with a new login role or modify a collaborator's role from a single view, without needing to switch between multiple, unrelated tabs.

Within the collaborators view, users should be able to:

  • Add a new role to the server.
  • Have that new role immediately available for assigning to a collaborator without re-entering a password.
  • Enter a password for any login role on the server at the moment they assign it to a collaborator.
@ghislaineguerin ghislaineguerin added type: bug Something isn't working type: enhancement New feature or request affects: ux Related to user experience needs: requirements The problem is clear and worth solving, but we're not yet sure of the best solution needs: ux design labels Oct 17, 2024
@ghislaineguerin ghislaineguerin added this to the v0.2.0 (beta release) milestone Oct 17, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
affects: ux Related to user experience needs: requirements The problem is clear and worth solving, but we're not yet sure of the best solution needs: ux design type: bug Something isn't working type: enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant