> For the complete documentation index, see [llms.txt](https://help.felt.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.felt.com/upload-anything/data-sources/add-a-source.md).
# Add a source
Connect databases, buckets, STAC catalogs, and web services to Felt. Check supported sources and allow Felt's IP addresses.
Connect a source so your workspace can browse its tables, files, or layers and add them to maps. Each source's page covers its setup fields.
For the sources you can connect and the plans they're on, see [Sources on each plan](/upload-anything/data-sources.md#sources-on-each-plan).
A Felt Server is also listed in **Data sources**, but you create it instead of connecting it, and fill it by publishing or uploading layers. See [Felt Servers](/upload-anything/felt-servers.md).
## Connect a source
We recommend connecting with a dedicated read-only database user or service account for Felt.
1. In a map, click **Data sources** in the center of the toolbar at the top of the map, then click **New source**. On the workspace home page, you can instead click **+** next to **Data sources** in the sidebar.
2. Click the source type, such as **Snowflake**.
3. In **General**, enter a **Source name**. People see this name in **Data sources**. It can't be a URL or a connection string.
4. In **Connection**, fill in the fields listed on the source's connector page. For most databases, you can click **Autofill** and paste a connection string instead.
5. If the form has a **Credentials** section, select an **Authentication type** and fill in its fields.
6. In **Access**, select **Workspace** or **Private**. For **Workspace**, choose a **Default access** of **View** or **Edit** for workspace members. A **Private** source is visible only to invited people.
7. Click **Connect**. Felt lists the source's datasets with previews. If Felt can't read some tables, such as a broken view or a table the database user can't access, it skips them and lists the rest.
We recommend connecting each database once and sharing that source with the people who need it. Felt checks every source's tables each day, so duplicate sources for the same database add load to it. Connect a database again only when some people need different credentials, such as credentials limited to certain tables. See [Sharing and permissions](/upload-anything/data-sources.md#sharing-and-permissions).
To add a dataset to a map, select it and click **Create layer**. Layers from a source can refresh on a schedule. See [Refresh data](/upload-anything/refresh-data.md).
Felt only reads from a database, bucket, or web service, and never writes edits back to it. Editing a layer from one of these sources turns off **Live** for that layer. See [Edit features](/layers/edit-features.md#edits-and-the-original-data).
## Sources Felt doesn't support
Felt can't connect to other databases, such as MySQL, DuckDB, or MotherDuck. A REST API, such as a weather API, isn't a source type either. To use that data:
* Publish it as a supported file at a URL and add it with **Upload Anything** > **From URL**. A URL layer can refresh on a schedule. See [Add data from URLs](/upload-anything/urls.md).
* Export it to a supported file and upload it. An uploaded layer doesn't refresh on its own. See [Supported file types](/upload-anything/files/supported-file-types.md).
* Send it with the Felt REST API. See [developers.felt.com](https://developers.felt.com).
## Allow Felt's IP addresses
Felt connects to your sources from 11 IP addresses: seven in the US, and one each for the EU, the UK, Canada, and Australia. If your database, warehouse, or server accepts connections only from known addresses, allow all 11. The **US IP allowlist** on the right of the source form shows only the seven US addresses.
```
44.223.226.142
3.226.194.1
3.225.225.123
34.214.220.83
35.167.192.127
34.231.46.212
54.202.111.199
```
* EU: `18.198.72.109`
* UK: `18.135.40.92`
* Canada: `15.156.153.120`
* Australia: `13.210.88.232`
## Manage a source
Managing a source needs Edit access to the source. Open the source and use the controls at the top right.
* **Refresh source list**, the circular arrow icon, refreshes the source's list of tables, views, files, and service layers now. Felt also checks each database, bucket, and web service source for new and removed tables once a day. The refresh succeeds as long as Felt can read at least one table, and it skips the tables it can't read. Refreshing the list doesn't refresh layers on maps.
* **Settings**, the gear icon, opens the source form, where you can change the source's details and credentials, or click **Delete source**. Saved passwords, tokens, and keys stay hidden. To change one, enter a new value and click **Save**.
* **···** > **Copy source ID** copies the ID to use with the Felt REST API.
Changing workspace access or inviting Source admins needs Source admin access. See [Sharing and permissions](/upload-anything/data-sources.md#sharing-and-permissions).
## Troubleshooting sources
### Source shows "Not connected"
Felt couldn't reach the source, usually because its credentials changed, a firewall changed, or the database is offline. If nothing changed, click **Refresh source list** to try again. Otherwise, click **Fix** next to **Not connected**, update the details, and click **Save**. If the details are correct and Felt still can't connect, email your database's access logs to .
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://help.felt.com/upload-anything/data-sources/add-a-source.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
