Settings and activity
63 results found
-
2 votes
Bethany Baker shared this idea ·
-
9 votes
Bethany Baker shared this idea ·
-
7 votes
An error occurred while saving the comment -
20 votes
The product team will review this idea for consideration for a future release.
Bethany Baker supported this idea ·
-
6 votes
The product team will review this idea for consideration for a future release.
Bethany Baker supported this idea ·
-
4 votes
Bethany Baker supported this idea ·
-
15 votes
Bethany Baker supported this idea ·
-
10 votes
Bethany Baker supported this idea ·
-
16 votes
Bethany Baker supported this idea ·
-
6 votes
Bethany Baker shared this idea ·
-
8 votes
Bethany Baker supported this idea ·
-
17 votes
Bethany Baker supported this idea ·
-
11 votes
Bethany Baker supported this idea ·
-
6 votes
Bethany Baker supported this idea ·
-
8 votes
Bethany Baker supported this idea ·
-
17 votes
The product team will review this idea for consideration for a future release.
Bethany Baker supported this idea ·
-
12 votes
The product team will review this idea for consideration for a future release.
Bethany Baker supported this idea ·
-
16 votes
An error occurred while saving the comment Bethany Baker commented
As a library consortium that has several library districts with multiple branches, it is critical to our functioning that we are able to assign more granular permissions to user accounts to allow one account to access multiple libraries. For instance, a library district (mp*) has a marketing department that they want to have handle the notices for all of the locations in the district (mpc*, mpd*, mpm*, mpf*, mpg*, mpo*, mpp*). With the current structure, you have to make an account for mp* and then 7 separate accounts that do not use the same email for the branch locations. The user cannot be made an admin for the consortium, because they then have access to all other libraries within the consortium that are not part of their district. Only some notices are sent at the branch level (mp*) but there are also notices sent at the location level, so they also can't just have access to the mp* location.
Bethany Baker supported this idea ·
-
8 votes
Bethany Baker shared this idea ·
-
20 votes
The product team will review this idea for consideration for a future release.
Bethany Baker supported this idea ·
I agree with Jeremy - I would still like the message to appear but the wording is confusing to staff. Wording that another workstation has the patron record open would be more helpful than the "Fines Payment Lock" wording.