Settings and activity
68 results found
-
14 votes
The product team will review this idea for consideration for a future release.
Bethany Baker
supported this idea
·
-
22 votes
An error occurred while saving the comment
Bethany Baker
supported this idea
·
-
9 votes
Bethany Baker
shared this idea
·
-
25 votes
The product team will review this idea for consideration for a future release.
Bethany Baker
supported this idea
·
-
30 votes
The product team will review this idea for consideration for a future release.
Bethany Baker
supported this idea
·
-
7 votes
The product team will review this idea for consideration for a future release.
Bethany Baker
supported this idea
·
-
14 votes
Bethany Baker
supported this idea
·
-
23 votes
Bethany Baker
supported this idea
·
-
21 votes
Bethany Baker
supported this idea
·
-
18 votes
Bethany Baker
supported this idea
·
-
37 votes
Bethany Baker
supported this idea
·
-
166 votes
Bethany Baker
supported this idea
·
-
10 votes
Bethany Baker
supported this idea
·
-
28 votes
Bethany Baker
supported this idea
·
-
8 votes
Bethany Baker
supported this idea
·
-
64 votes
We are planning to add the item cost to overdue notice data so it can be included in overdue notices sent through LX Starter as of Sierra 6.7.
Additional changes will be needed in LX Starter before the new data can be included on emails for overdue items.
Bethany Baker
supported this idea
·
-
31 votes
This will be implemented in Sierra in 2027.
Bethany Baker
supported this idea
·
-
39 votes
The product team will review this idea for consideration for a future release.
Bethany Baker
supported this idea
·
-
21 votes
Bethany Baker
supported this idea
·
-
14 votes
Bethany Baker
supported this idea
·
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.