Bethany raises a good point. Assigning print templates to individual logins can be a very time-consuming process, especially in environments with many templates or in consortium settings where administrators may need to configure dozens of staff accounts.

While it is possible to speed the process slightly by opening multiple user records in the Sierra Admin App and toggling between tabs, this is still inefficient and does not scale well. In the Sierra Desktop App the process can be even slower, since it often requires opening multiple instances of the application or repeatedly opening and closing user records.

The idea of managing print templates in a manner similar to Permissions, where templates could have their own sidebar and administrators could add multiple logins at once, would be a meaningful improvement.

One additional enhancement that could further streamline administration would be to leverage the existing Import functionality when creating or modifying user accounts.

For example:

An administrator could create a “Template” user account configured with the desired print templates.

When creating or editing another user, the administrator could select Import, choose the Template user, and import the relevant configuration.

This could be even more useful if the Settings section were broken into selectable components, similar to how Permissions are structured today. For instance:

- Settings
-- Print Templates
-- Macros
-- Record Templates
-- Other Settings categories

This would allow administrators to import only the Print Templates, or combine them with other settings if desired.

A similar case could be made for Macros and Record Templates, which are also bundled within the Settings section and often require repeated configuration when onboarding staff or setting up accounts for new locations. Allowing administrators to selectively import or assign these elements would significantly reduce repetitive work and help ensure greater consistency across staff accounts.

Together, these improvements would make configuration tasks far more efficient and scalable for system administrators managing Sierra environments.

This is a great idea!

Good point, Jeremy. I should have been more clear that my proposal relates the admin app method of adding print templates to logins. I imagine the SDA way staying the same, that way more savvy library staff can still import, export, and assign print templates to their login.

I like this idea for many of the templates but not universally. Spine labels in particular need to be something that end users can work with on the client side of things and shouldn't be walled off to admins, though for most other use cases I can see this proposal working decently well.