Multiple users accessing Admin

We currently have three laptops signed into Admin in our school library. However, teachers want the convenience of being able to return books using their own laptops.

Would you advice multiple user access to Admin especially since they would be able to manipulate the LibraryThing data?

I am offering training to do otherwise and there is successful high trust in our organisation.

Unfortunately, with only one Admin login per TinyCat account and logins being user-based not session-based, you would surely come across issues with multiple users trying to check out and/or return books at the same time in the Admin portal. I'm sorry for any inconvenience here.

We'll be sure to announce if we end up changing the Admin logins to session-based, which would help out here. I do have it on my list of features to consider!

We have TinyCat admin logged in on various PCs here as well, and in terms of Check-in/Check-out, we have no issues with it creating conflict, since each attempt to sign something out initiates a new communication with the server and therefore is always retrieving the most up-to-date information.

I would also love to see multiple users allowed in TinyCat admin. I would also like there to be different levels of admin, so that volunteer staff don't have access to billing, LibraryCat, or "delete all" buttons.

Multiple stations would be really helpful. I noticed today when I was doing training on an iPad station that it updated on our computer station really quickly, so I definitely think that would create some issues if we were circulating at the same time.

Actually, I cannot second calls for additional admin logins strongly enough. Not being able to have limited admin accounts for volunteers basically is a deal-breaker for any library that must obey European data privacy standards. You cannot have students see the full lending history of any of their peers, period. And this means you cannot have students help checking books back in, which is the main task in our library.

Duly noted. I believe one of the biggest blocks against us doing it isn't so much "why" but rather "how". The way our accounts were set up from the beginning would involve some major functional changes to allow this to happen. Our development team is simply too small to take on such a large task where other projects are currently taking precedence. I understand the frustration, so thank you very much for your patience!