This is an old revision of the document!

Lot configuration

Linkage of lot to Vigilant location

The key to linking a Ranger lot to a Vigilant location is the Vig loc name as shown below on the Lot spreadsheet screen above
The value in the Name column is irrelevant
The value in Vig loc name must EXACTLY match the value in the Location name as shown below in the Vigilant client portal Locations screen

After the Ranger lot is configured with a Vigilant location name, the unified authorized list source will become available AFTER the first FTP upload after the configuration. It will be named something like Unified- and location, such as the example shown below (e.g., Unified-Downtown)
If the Diff upload? flag is checked on a lot, the differential authorized list source will become available ONLY AFTER THE FIRST PERMIT FOR THE LOT IS ENTERED AND UPLOADED. It will be named something like Differential- and company ID and location, such as the example shown below (e.g., Differential-6621-Downtown)

Communications that are disabled if checked:
- Unpaid ticket reminders
- Tow notices

	Email	Text message
Non-P2P permit receipt	Always	Never
P2P permit receipt	Always	Always
Guest permit receipt	Always	Property flag
Ticket paid receipt	Always	Never
Approval invitations, first time	Lot permit comms flag	Property flag
Approval invitations, ongoing	Lot permit comms flag	Never
Unpaid permit	Lot permit comms flag	Never
Transfer confirmation	Lot permit comms flag	Never
Permit nearing expiration (non-P2P permits)	Lot permit comms flag	Never
Permit nearing expiration one-time (P2P permits)	Always	Always
Permit approval extension	Lot permit comms flag	Never
Unpaid ticket	Lot violation comms flag	Never
Tow notice	Lot violation comms flag	Never

This is intended to control Property Portal and prevent the setting of future expiration date of an approval
It is intended for use at properties such as university parking lots, for which an approval should be created for each new period (e.g., semester)