Part 107 UAS pilot reported conducting a training flight where they exceeded some of their LAANC authorization parameters.

Narrative

While doing some photography (that may or may not get used commercially); teaching recreational pilots (aka; flying with family members who are only TRUST [Certified]); and doing some general flying; we may have violated our LAANC approval.We had; in total; 3 LAANC authorizations.During this time; the following may have happened: - The drone may have gone slightly above the approved 50ft while being controlled by learning recreational pilot (no more than a high of 65ft AGL).- Flights may have exceeded the authorization time (bringing the drone in at XB:04 local which may have been 1-4 minutes after the LAANC for the area ended).- Flying outside of the filed LAANC (not in the right spot along the beach vs. where we were expecting to be).- Flight may have gone over people or vehicles.The following would be contributing or causing factors:- Part 107 operator misread the chart supplement - they accounted for Zulu time but missed the symbol meaning to adjust back an hour for daylight savings and thought a LAANC would not be needed before XB:00 AM local (would need to be XA:00 AM local). The LAANC was still filed appropriately as a precaution.- The DJI Fly controller app was not allowing max altitude be set below 65 ft when connected to the aircraft (DJI Air 3) even though LAANC was only good up to 50 ft. The same app limitation prevents auto Return to Home to be set below 65 ft. This meant when one of the inexperienced pilots was at the controls; they occasionally went above the 50 feet clearance as they were more focused on working the control sticks and keeping visual on the drone than checking the altitude reading on the screen. - The DJI Fly controller app for the drone bases all calculations on meters and does therefore settings are often more difficult to set using imperial units even when imperial is selected. For example; it is difficult to set to '100 ft' and instead skips to '98 ft' when dialing in settings.- Using the Aloft Air Control software to request the LAANC; it is difficult to move the requested area and it is not possible to modify a request once sent. This resulted in multiple LAANC requests that may have been confusing; covering different areas and times.- Individuals / vehicles moving in a direction / area where the drone or operator would not be able to see or carefully watching (such as when doing a pan backwards).Suggestions:- Make LAANC valid in 15 minute increments instead of to the minute (an XB:01 am end time should be advanced to XB:15 am unless there are extenuating circumstances).- Make DJI Fly app allow lower limitations such as 50 ft max altitude as that is common in the FAA grid.- Make DJI Fly app snap to common imperial values when set to imperial measurements.- Have Aloft Air Control and other LAANC software make bigger recommendations for covered area (to give people not only more room to fly but also walk around and fly) and suggest wider time bands; particularly in areas that are less critical to nearby traffic (aka; more than .5 nm from an airport; not in the direct runway approach; etc.).- Adjust rules for small drones so that 'flying over people' means 'groups of people' (like 5 or more) rather than having to weave around to try and not be over individuals). - Create better ways for drones to detect if / when they may be over people / vehicles with omnidirectional sensing. - Have some defined / suggested areas to go flying (besides controlled community based organizations with their own airspace) that are pre-scouted and give pilots suggestions for where to fly; obstacles to consider; etc. specific for that area and its enjoyment (kind of parks do) and maybe add signs and warnings to the area; give walking trails; etc. so that way pilots have more knowledge of the area and the non-flying public is more aware.