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

Edit existing user outside of org as an orgadmin #975

Open
goddesswarship opened this issue Jan 7, 2025 · 1 comment
Open

Edit existing user outside of org as an orgadmin #975

goddesswarship opened this issue Jan 7, 2025 · 1 comment
Labels
platform support needs to be addressed by staff question open investigation to define scope of issue

Comments

@goddesswarship
Copy link
Contributor

Issue summary
Org admins have limited access in the User Management tool (/appadmin/users.jsp) and can only see users associated with their org in accordance with security permissions. There are two use cases where managing users creates friction for their workflow:

  1. Org admin wants to register a new user for their org, but the user's email address already exists in the system from a previous public encounter submission and Wildbook doesn't allow multiple accounts from the same email address. These are accounts with a UUID but there is no username, password, or role associated with them. Because these UUID placeholder accounts have no org association, an org admin can't search for them to make the account useable.
  2. Org admin wants to add an existing registered user to their org. Any registered user that's not already in the org admin's organization will not appear in a user search.

Workaround
Org admin can contact staff or a site admin for help with completing registration on a shell account or adding the org to an existing user's account.

This is a work in progress while we discuss potential solutions.

@goddesswarship goddesswarship added the question open investigation to define scope of issue label Jan 7, 2025
@goddesswarship goddesswarship added the platform support needs to be addressed by staff label Jan 17, 2025
@goddesswarship
Copy link
Contributor Author

This doesn't appear to be an issue in later versions of Wildbooks, so the likely solution is for Whiskerbook to receive an upgrade as it's currently on 10.3.0. Leaving this open for now until we verify.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
platform support needs to be addressed by staff question open investigation to define scope of issue
Projects
None yet
Development

No branches or pull requests

1 participant