> 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.md).
# Data sources
Browse and share data sources in Felt, from databases and buckets to Felt Servers. Preview datasets before adding them to a map.
A data source holds datasets your workspace can browse, preview, and add to maps. Sources include Felt Servers, web services, databases, buckets, and STAC catalogs. To connect one, see [Add a source](/upload-anything/data-sources/add-a-source.md).
## Sources on each plan
| Source | Plans |
| ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ------------------------------ |
| Web services: [ArcGIS services](/upload-anything/arcgis-services.md), [WMS / WMTS](/upload-anything/data-sources/wms-wmts.md), and [WFS](/upload-anything/data-sources/web-feature-service-wfs.md) | Team, Business, and Enterprise |
| Databases: [Postgres / PostGIS](/upload-anything/data-sources/postgres-postgis.md), [Microsoft SQL Server](/upload-anything/data-sources/microsoft-sql-server.md), [Amazon Redshift](/upload-anything/data-sources/amazon-redshift.md), [BigQuery](/upload-anything/data-sources/bigquery.md), [Snowflake](/upload-anything/data-sources/snowflake.md), [Databricks](/upload-anything/data-sources/databricks.md), and [Wherobots](/upload-anything/data-sources/wherobots.md) | Business and Enterprise |
| Buckets: [Amazon S3](/upload-anything/data-sources/amazon-s3.md), [Google Cloud Storage](/upload-anything/data-sources/google-cloud-storage.md), and [Azure Blob Storage](/upload-anything/data-sources/azure-blob-storage.md) | Business and Enterprise |
| [STAC](/upload-anything/data-sources/stac.md) catalogs | Business and Enterprise |
| [Felt Servers](/upload-anything/felt-servers.md) | Business and Enterprise |
The number of database and bucket sources, and of Felt Servers, depends on the plan. See the [Felt pricing page](https://felt.com/pricing). The [Global Library](/upload-anything/global-library.md) is on every plan.
## Browse data sources
The **Data sources** dialog lists every source you have access to, plus the Global Library. Private sources you haven't been invited to don't appear. In a map, click **Data sources**  in the center of the toolbar at the top of the map, or press **Shift+L**. On the workspace home page, the same list is in the **Data sources** section of the sidebar.
* The search bar at the top of the dialog searches the open tab: **Recent data** searches every source at once, and a source's tab searches only that source.
* The **Recent data** tab lists datasets you recently previewed, added to a map, or published.
Select a dataset to preview it in the **Map**, **Table**, and **Metadata** tabs. To add it to the current map, click **Create layer** for a dataset from a database, bucket, or web service, or **Add to map** for a Felt Server layer. The layer appears in the legend. On the home page, click **Create map** to start a new map with the dataset.
A layer from a database or bucket is a copy: Felt reads the data when you create the layer, stores it for fast display, and reads it again at each refresh. Cloud Optimized GeoTIFFs (COGs) streamed from a bucket or STAC catalog aren't copied. See [Refresh data](/upload-anything/refresh-data.md) and [Stream large rasters](/upload-anything/stream-large-rasters.md).
The **Data sources** dialog, formerly the Library, also includes the Global Library, Felt's collection of public datasets. The Global Library isn't a source: every workspace can use it, and it has no sharing settings. See [Global Library](/upload-anything/global-library.md).
To add a file, a URL, or a spreadsheet to one map, you don't need a source. See [Upload files](/upload-anything/files.md) and [Add data from URLs](/upload-anything/urls.md).
## Sharing and permissions
Each data source has its own access settings, separate from those of maps that use its data. A source can be open to the workspace (the Workspace setting) or private to invited people. Its access levels are View, Edit, and Source admin. The person who adds the source gets Source admin access. See [Permissions](/administration/permissions.md#data-source-level-permissions).
### Change who can access a source
Changing a source's workspace access needs Source admin access.
1. Open the source and click **Share**.
2. In the workspace access list, select **View** or **Edit** to open the source to the workspace at that level, or select **None (make private)**.
3. If you're switching the source between open and private, click **Make private** or **Open to workspace** to confirm.
### Invite people to a source
{% hint style="success" %}
Available on the Business and Enterprise plans. [Compare plans](https://felt.com/pricing#compare)
{% endhint %}
Inviting people to a source needs Edit access to the source. An invitation gives people access to one source, including a private one.
1. Open the source and click **Share**.
2. Enter one or more email addresses and select an access level.
3. Click **Invite**. People who aren't workspace members get an email invitation.
To change or remove someone's access, open **Share** and select a new level next to their name.
---
# 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.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.
