Locations

Locations are the physical sites, buildings, or areas where your equipment lives. Tagging tickets and equipment with locations makes filtering by "everything happening in Building B" trivial.

Enabling the module

Admins go to Settings → Modules and enable Locations. Locations then appears in the sidebar.

Adding a location

1. Sidebar → Locations → New location.
2. Fill in:
   • Name— "Main warehouse", "Hangar 2", "3rd floor east".
   • Address (optional) — physical address. Useful for vendors or off-site techs.
   • Notes (optional) — anything site-specific (gate code, parking instructions, contact person).
3. Save.

Using locations

Once you have locations:

• On equipment — assign a location to each piece of equipment so location filtering on tickets is automatic.
• On tickets— manually pick a location when filing if the ticket doesn't have an asset, or if the asset spans multiple locations.
• Filtering — the All issues page lets you filter by location.

How granular should locations be?

Match the level you naturally talk about with your team. If you say "the freezer in the back kitchen" out loud, the location is "Back kitchen" — not the whole building, not down to the specific shelf. One per area that has its own set of equipment is usually right.

Snippath doesn't currently support nested locations (e.g. Building → Floor → Room). If you need that, encode it in the name: "Bldg A / 3rd floor / Kitchen". A nested model is on the roadmap.

Archiving a location

Use Archive if you close a site. Archived locations keep their history and stop appearing in pickers for new tickets/equipment.