Indeed, put a Release Station (kiosk) device next to each target printer. In case multiple SavaPage server instances share the same target printer, add a Release Station Terminal definition at each server instance for the station device IP address and assign the related proxy printer as Single Printer Target.
Assuming each SavaPage User Web App instance has a unique URL, accessible from the Terminal device, you can inject an HTML snippet into the User Web App login screen of each server instance with (graphic) links to all of the SavaPage User Web App server instances.
Well, as a user arrives at the Release Station they must first click on the picture in the Login screen to select their domain (if not already selected). This will load the right User Web App instance, so they can authenticate with their domain credentials. You can optionally attach an NFC card Reader as alternative authentication. Tip: CSS customize the Web Apps of each server instance with a distinguishable look-and-feel.
N.B. set a value for Idle Seconds before auto logout. This will make the Web App return to the Login screen after x idle seconds, in case a user forgets to log out after printing is done.
The printer next to the terminal will be the only printer available in the User Web App. Currently, users must create and execute the print job in the User Web App on the Release Station on the spot. If other scenarios are required, we need to discuss how SavaPage could be adapted to accommodate that.