Site Configuration
Location-level infrastructure, credentials, checklists, and documents in the same platform your team already uses.
The value is cleaner handoff at the site level: infrastructure records, credentials, checklists, and documents stay with the same customer and location model used for service work instead of living in a separate documentation stack.
- Technicians can open network, firewall, ISP, and checklist context without leaving the customer record.
- Site-level documents and break-glass details stay close to tickets, devices, and backups.
Before / After
Site knowledge becomes part of the work instead of a lookup chore.
Before: technicians bounce between a ticket, a separate documentation tool, and a vault just to recover one site’s firewall, ISP, circuit, and checklist context. After: the location record, the documents, and the service workflow are tied to the same customer model.
- Review network, firewall, ISP, static IP, and document context without breaking the service flow
- Keep onboarding and audit checklists close to the same site record technicians already use
- Reduce handoff loss when another technician needs to step into the customer site history quickly
What the site configuration surface covers
Overview Infrastructure summary for every location Customer-site context stays available where the service team already works.
Overview data gives technicians a faster starting point during incident work, onboarding, and routine maintenance.
Network Networks, firewalls, and static IPs Track subnets, gateways, DHCP ranges, firewalls, serials, MACs, and static IP allocations.
Network and firewall records stay attached to the same site model used for day-to-day service work.
ISP Provider details and uplink records Keep ISP details, circuit IDs, uplink data, and support numbers tied to the right site.
Useful when service teams need provider context during outages and escalation.
Credential Break-glass credentials and sensitive access records Location-level credential context stays close to the rest of the site record.
Break-glass access is easier to handle cleanly when it lives inside the broader platform, not a separate documentation silo.
Checklist Checklists, custom fields, and repeatable steps Store site-specific notes, onboarding sequences, and audit tasks where technicians can actually use them.
Structured fields and checklists help keep customer-specific process details from falling through the cracks.
Docs Documents and knowledge alongside site records Operational docs become more useful when they sit inside the operating flow instead of beside it.
The wider product also includes PSA knowledge-base capabilities, so operational knowledge does not have to live outside the platform even when some information is site-specific.
See how site configuration fits your current documentation stack.
Book a walkthrough if you want to compare your current documentation and site-record process against VexylCloud’s location-aware operating model.