TOPIC: Field limits on backend

I am using DT register for a conference registration. In the conference we have 6 breakout sessions. Each session has 6 options. Each option can only accept 90 people.

I have breakout options where the front end is showing them as closed once they hit their limits. That is good.

BUT on the back end, my administrator has no idea that a breakout option is closed. She has been registering people for closed option because the limits aren't stopping her.

How do I stop her from registering mail-order people through the back end into breakout options that are closed? Is there a setting that will not allow her to choose those options? Last year (an older version), I thought the options were no longer a choice on the backend as well as the front end when they were full.

Thank you.

Sorry, but selection limits were purposely removed from admin side manual registrations because many people complained about that. They felt that as an admin they should be able to register any options and override limits seen by users. There is no setting to change this. You might consider having them just do the registrations on the frontend. If there is a payment, have a discount code that makes if free so they do not have to process a payment. Just an idea. Otherwise, if they want to use the backend and this is a concern, they'll just have to be aware of current registration status and what is and is not available. They can run CSV exports, etc to have that info.

Some type of visual notification that you are exceeding a defined limit would be nice here... perhaps I will add that to the wish list. If the registration requires member registration, I can see this being a problem if you are modifying an existing registration to add an option that previously was not selected... because then you only have the backend unless you change their password. I am glad this was posted as I know we will run into this. I guess the other option is to write a SQL query outside of the DT interface so that you can run it each time before modifying/adding the options.

So for those that complained about having the right to exceed the selection limits as an Admin... could they not just elevate the actual limit before adding? Or does this do something bad?