> ## Documentation Index
> Fetch the complete documentation index at: https://docs.arterial.us/llms.txt
> Use this file to discover all available pages before exploring further.

# GIS Connections

> Add map data connections, test them, and manage layers for your workspace.

<Warning>
  These tasks are for **workspace administrators**. If you do not see **GIS
  Connections** on Settings, ask your workspace administrator.
</Warning>

The Settings card is **GIS Connections**. The full page title is **GIS Connections**. It **manages map data sources and layer configurations**.

## What success looks like

For a reader who is not an engineer:

* A **connection** is a saved link to your organization’s map server or similar source.
* **Testing** a connection means the dashboard checks that it can reach the server with the details you entered.
* **Layers** are the individual map overlays (streets, parcels, utilities, and so on) that you turn on for users on the Pin, Heat, and Coverage maps.

Success means hazards and reference layers appear on the map without repeated errors. If testing fails, the screen usually shows a short error message you can share with support.

## Guided tour

A guided tour is available on this page to walk you through the connection wizard, saved connections, layer discovery, and configuration. The tour uses demo values so nothing is submitted to your server. Look for the tour trigger at the top of the page. See [Guided tours](/support/help#guided-tours) for more about tours.

## Typical workflow

1. Open **Settings**, then **Open Connections** (or go straight to the connections URL from your bookmark).
2. Use **add** or **wizard** controls (exact labels on the page) to create a new connection. Fill in the name, server address, and any credentials your IT team provided. The form validates each field before you can continue, so fix any highlighted errors before saving.
3. **Save**, then use **Test** or **Discover** style actions the page offers. **Discover** finds layers the server exposes.
4. Add layers you want end users to see. Enable or rename them as your process requires.
5. Confirm layers appear under **Layers** on the map pages for a normal user account.

## Editing and removing

Select a connection or layer to **edit** details or **remove** items you no longer need. Be careful removing layers that staff rely on for context.

## If something fails

See [Troubleshooting](/support/troubleshooting). Your workspace administrator or GIS staff usually fixes connection URLs, credentials, or firewall rules.

***

## Related topics

* [Pin Map](/maps/pin-map)
* [Settings overview](/settings/overview)
