Household vs. Property-Wide Bans in Gated Communities

When Someone Is No Longer Allowed Through the Gate

We've talked with property managers who have dealt with everything from custody disputes to former employees returning to a property after being terminated.

One manager told us that divorce and custody issues had resulted in several people being placed on the community's do-not-admit list.

Another described situations involving restraining orders.

"There's a guest, or, say, an occupant, and there's a restraining order, or something happens, and we just don't want that person allowed through the gate."

These situations aren't always straightforward.

A resident might not want a former partner visiting their home. That doesn't necessarily mean the individual should be prohibited from visiting every other household in the neighborhood.

But if management has determined that someone should no longer be allowed on the property, banning them from one household may not be enough.

Gate Sentry handles these situations through two types of bans.

Account-Level Bans

An account-level ban applies to a specific household.

Residents can restrict individuals from visiting their home without preventing them from visiting other residents.

If someone attempts to visit a household that has banned them, the guard receives a red alert during check-in.

If that same person is visiting another household that hasn't banned them, the guard receives an orange warning instead. The warning lets the guard know about the existing household restriction without automatically denying the current visit.

Property-Wide Bans

Property-wide bans are issued by authorized community administrators and apply across the entire community.

If someone has been prohibited from entering the property, the restriction applies regardless of which household they claim to be visiting.

When that individual attempts to check in at a staffed entrance, Gate Sentry displays a red alert notifying the guard of the restriction. At unmanned Sentry Solo entrances, a ban blocks the person's SoloPass and VirtualKeypad codes.

The appropriate restriction depends on the circumstances and the community's authority to enforce it. A restraining order, for example, must be handled according to its actual terms and applicable law.

A Terminated Employee Returns to the Property

One property manager told us about an incident that had happened the day before our conversation.

An employee had been terminated but returned to the property to collect some belongings. His wife drove him onto the property.

The manager explained how quickly that situation could become a problem.

It also brought up a question we've heard from other property managers: How do you restrict one individual without restricting everyone associated with them?

If a former employee is no longer authorized to enter, that doesn't automatically mean their spouse or other family members should be banned.

The same issue comes up with vendors.

Say a landscaping company services several homes in a gated community, but one employee is involved in an incident that results in a ban.

Management may still want the landscaping company to service its other customers. It just doesn't want that particular employee returning.

Gate Sentry allows administrators to distinguish between a vendor company and an individual vendor employee when creating restrictions.

Guards still need to verify who's entering the property, including passengers when required by the community's check-in procedures. A ban is only useful when the restricted person is correctly identified.

Guards Need to Know Why Someone Is Banned

During another conversation, a property manager asked whether Gate Sentry would show notes explaining why someone had been banned.

"This is very important to us," she said.

Consider a guard who's new to the community. Someone arrives at the gate, and the system shows that they're banned.

Was there a dispute with a resident? Was the person involved in an incident on the property? Is this someone management has specifically instructed security not to admit?

The guard needs enough information to identify the person and follow the appropriate procedure.

When administrators create a ban in Gate Sentry, they can select an incident reason and add supporting notes. They can also include:

• Date of birth and driver's license or ID information
• Vehicle make, model, color, and license plate
• Photos and supporting images
• The date the ban was created and the administrator who entered it

That information is especially useful when someone has a common name. A guard shouldn't deny entry to the wrong person because their name happens to match someone on the ban list.

Red and Orange Alerts

Gate Sentry uses color-coded notifications during visitor check-in.

Guards can see the restriction during check-in instead of having to remember every name on a ban list or rely on notes passed between shifts.

For how ban requests get lost between security shifts, see what happens when a security officer doesn't know someone is banned.

Managing Bans Through the Admin Portal

Gate Sentry's Community Ban List allows authorized administrators to manage active bans, review past restrictions, and see changes made to the list.

When creating a ban, management selects whether it applies to a household or the entire property. Administrators also identify whether the restriction involves a guest, vendor company, or individual vendor employee.

If the person has previously entered the community, the Search from Logs feature can pull up existing visitor information.

Management can then add the incident reason, supporting notes, identifying details, and up to five images. Once saved, the restriction becomes available to the community's guard stations.

Administrators can edit or remove bans when necessary. An account-level ban can also be changed to a property-wide restriction if the situation warrants it and management authorizes the change.

Creating property-wide bans requires administrative access. Guards and security personnel without those permissions cannot independently create them, so communities should have a process for reaching an authorized administrator when an urgent restriction is needed.

What Happens When a Banned Individual Returns?

If someone on the ban list attempts to enter again, management needs to know what happened at the gate.

Did the guard receive the alert? Was the individual denied entry? Did someone override the restriction?

Gate Sentry records ban-related activity and entry attempts, allowing administrators to review the interaction. If a guard overrides a restriction, that action can be associated with their user account.

These records can help management follow up on incidents, review security procedures, and answer questions from the HOA board.

They don't automatically establish criminal trespassing or make a ban legally enforceable. Communities are still responsible for following their governing documents, applicable law, court orders, and established procedures.

Does Your Community Have a Clear Process for Visitor Bans?

If your community has a staffed gate, there are a few things worth checking.

Can a resident ban someone from their household without affecting other homes? Can management restrict a specific individual across the property? And will a guard working a different shift know about the restriction?

We've heard these questions directly from property managers, particularly when they're dealing with situations that don't fit a simple banned-or-not-banned setting.

Gate Sentry allows communities to manage household and property-wide bans separately, document the reasons for restrictions, and notify guards during check-in.