Safe Use in Front End Group Reservation Booking Application

[CKMacLeod]

For a website that puts on workshops and other events and needs to have specific attendee lists (sign-in sheets), based on tickets sold via a WooCommerce ticketing/booking add-on that has not yet been able to develop group buying of this general type (useful for educators, hotels, any business with name-linked reservations that can be purchased in bulk):

1. Create special class of WP user - Group Buyer - empowered with narrow/defined privileges to create other users - Group Members - and User Groups - and with no other admin or other privileges other than to edit own profiles and place orders like any other Customer (i.e., lowest level permissions)
2. Group Members have only lowest level account: They are entered into user database strictly for use by the GB, though nothing prevents their accounts from later being converted into higher level accounts.
3. Group Buyers (GBs) create a list of GMs in the new Group. List can be form or (possibly) flat file import or (possibly) editable list on file. Will rarely exceed 20 members, maybe 35 at most
4. Group identified by order-type/order-number
5. After finishing list, GB clicks button to initiate PHP script
6. Processed via this Front End-accessible version of Batch Process Helper
7. Group Members go to Attendee List (along with regular customers who book reservations one by one)
8. Total number in Group is saved for processing of "multiple item purchase" of associated WooCommerce product

Danger of malicious exploits reduced by upper limits on items to process and on processes per GB. What I'm not sure of is whether there are other dangers that ought to be considered, or other reasons why, with permission properly narrowed and defined, Batch Process Helper couldn't be run from the front end in some user-friendly way.