Edit Username in Admin App
Once a user is created in the admin app, you are not able to update the username. You may update the password, permissions, etc., but not the username itself.
All of our clerk-level positions are part-time, so there is a lot of turnover. Each time an employee leaves, his/her account must be deleted and a new one created for the replacement. When the new account is created, you then must import all of the permissions, options, locations served, etc., of a comparable employee for the same location.
Ideally, we would simply be able to edit the username and password and provide that to the replacement employee, who will have the exact same permissions, workflow, settings, etc.
Idea Value
Allowing system administrators to edit the Sierra username would cut down on unnecessary work, saving time, staff aggravation.
Alison Pruntel
shared this idea
-
Gerald Rezes
commented
In case this doesn't get voted in, I create template profiles for various job functions then use the copy feature when creating new users.
-
MEEP candidate July 2024
-
Adam Hornsey
commented
Can you also increase the number of characters allowed for the username - currently a maximum of 12. We prefer to keep our Sierra usernames the same as a users network login name (one less thing to remember). Anything over 12 characters we need to make a different Sierra username
New idea from comment
This comment was upgraded into a new idea: Increase Sierra Username Character Limit -
Sheryl VanderWagen
commented
This would be very helpful. We don't have a lot of individual user accounts, this would be great to be able to change for either staff changes and/or name changes
-
Pam Wells
commented
This is also important for people who change their names due to marriage, domestic partnership, divorce, or just want or need. I have had to tell a cataloger either she has to keep the name of her former husband or completely get a new account. Catalogers use their initials tracked in Sierra to see who edited a record last, so having the same initials throughout is very important to them for clarity and accountability.
-
Phil Shirley
commented
This would be helpful when we make a mistake in entering a username, or when someone changes their name. Re-creating the account takes more time and is an opportinutiy to maker errors.
-
Jeremy Goldstein
commented
For another use case, we use shared logins for nearly all of our user accounts and have a naming schema used for helping to identify the role each is used for (think circulation vs circulation supervisors). We have needed to modify that schema in the past, but doing so now means creating whole new accounts instead of simply updating our existing ones in order to fit with such a change.