Settings and activity
106 results found
-
8 votesEliza Richards supported this idea ·
-
10 votesEliza Richards supported this idea ·
-
37 votesEliza Richards supported this idea ·
-
79 votesEliza Richards supported this idea ·
-
9 votesEliza Richards supported this idea ·
-
58 votesEliza Richards supported this idea ·
-
39 votesEliza Richards supported this idea ·
-
15 votesEliza Richards supported this idea ·
-
80 votes
An error occurred while saving the comment Eliza Richards supported this idea · -
125 votesEliza Richards supported this idea ·
-
7 votesEliza Richards supported this idea ·
-
17 votesEliza Richards supported this idea ·
-
36 votesEliza Richards supported this idea ·
-
10 votes
An error occurred while saving the comment Eliza Richards commentedWe have been asked for this especially in the patron info, i.e. holds, checkouts, reading history
Eliza Richards supported this idea · -
15 votesEliza Richards supported this idea ·
-
10 votesEliza Richards supported this idea ·
-
24 votesEliza Richards supported this idea ·
-
49 votesEliza Richards supported this idea ·
-
31 votesEliza Richards supported this idea ·
-
17 votesEliza Richards supported this idea ·
This is very important for a large organization. We need to be able to tie down staff who can update the homepage which differ from staff who update the locations. These staff are different from those who update the config of Vega. We also need to be able to have separate logins per person. It's not reasonable to give everyone one login/password, which we can't change ourselves.
The current way to change the admin password based on an email in the system seems problematic and slow.