Most of the time, locations shouldn't have two things happening at once. But some locations are special and represent open spaces or abstractions where an unlimited number of events could take place at the same time. For example:
WEST FIELD, a grassy space where any number of student organizations can hold booths at once
OFF CAMPUS, for any event that happens in the wider world outside your institution
RESEARCH HOSPITAL, a separate facility for medical instruction that holds multiple classes at once
TBA, a placeholder "location" that doesn't exist but is assigned to events for workflow purposes
In these cases you don't care about double bookings, so you don't want conflict warnings to prevent you from assigning anything. To prevent 25Live and LYNX from giving you warnings, enable the location as permanently shared.
Begin typing the name of a location. The text box will auto-complete with suggestions from 25Live.
Click Add New Value to share additional locations.
Click the X next to any location's name to remove it from the list.
Changes to the list are automatically saved as soon as you make them.
Image: Shared Locations in LYNX
Sharing in 25Live
Marking a location as "always shared" in 25Live will affect all events where the location is assigned, past and future. Any time availability is checked for a location, a user will be told that there is no conflict. This applies even if the user does not normally have permission to share location assignments on individual events via the event form.
For example, if your student union can support 25 separate presenters during a tabling event, you could create 25 separate locations as subdivisions of the student union space and title them "SU Table #1" etc. This allows you to set aside a unique location for each reservation while still using the student union's availability.