# Cloud sources

<figure><img src="/files/n86MTIERrwJBV0Ywqg0f" alt="" width="563"><figcaption></figcaption></figure>

Directly connect your cloud sources to access your data in Felt as a live catalog of layers. With this integration you can add a layer directly from your database to a spatial dashboard and configure live map updates from the source automatically.

{% hint style="success" %}
This feature is only available to customers on the [Enterprise plan](https://felt.com/pricing). To upgrade, [contact sales](https://felt.com/sales).
{% endhint %}

## Best Practices

1. Create a new database user for Felt access. Felt does run queries on the db, although we keep these at a minimum. This insures easier audit for your IT team.
2. Maintain only 1 connection per database source. Adding multiple connections to the same database will increase the query load on your database unnecessarily.
3. In case you see an error with the connection
   1. If your connection details have not changed, try hitting refresh to retry the connection
   2. If you need to change the connection click on **`Fix`** or the settings (cog wheel) to make & save changes to the connection details.
4. If your connection details are correct and you are still having issues, check the access logs for your database and send these in an email to <support@felt.com>.

## Felt IPs

When Felt connects to your data source, the traffic will come from one of the following IP addresses:

```
44.223.226.142
3.226.194.1
3.225.225.123
34.214.220.83
18.198.72.109
13.210.88.232
18.135.40.92
15.156.153.120
35.167.192.127
34.231.46.212
54.202.111.199
```

Limiting database access to a specific set of IP addresses enhances security by allowing connections only from pre-approved addresses while blocking all other connections at the firewall level.

## Syncing behaviors

#### Source syncs

Every 24 hours Felt will scan the connected Source to make updates to the data available in Felt. This includes making recently added tables or views available in Felt as well as reflecting any changes or updates to the Source schema. This cadence ensures that Felt matches your source of truth. These syncs do not impact any maps or layers on maps, so they do not contribute towards monthly data processing.

A Source-level sync is successful as long as there is at least one successful table sync. In the scenario that some tables or views are unavailable or fail to sync during a Source sync, those failing tables are skipped and Felt logs those skipped tables.

You can manually sync a source using the setting controls: [#settings-and-layout](#settings-and-layout "mention").

#### Layer syncs

When creating a map layer from a Source, the layers will be **Live** by default. Live data will refresh on the map directly from the source based on a frequency set in Felt.

You can control the Live and Frequency settings in the `Create layer` dropdown:

<figure><img src="/files/IK0z8yFLTsyXKapSaYO9" alt="" width="307"><figcaption></figcaption></figure>

Live data refreshes will contribute towards your monthly data processing limits. For more information see [Refreshing data](/layers/refreshing-data.md).

## Settings and layout

Access source-level controls in the top-right corner of any Source connection window

<figure><img src="/files/HyBZHOCLAF2XC9jtJYTG" alt=""><figcaption></figcaption></figure>

* **Sync Source:** triggers a manual sync for all tables and views in the source
  * *Does not sync map layers or impact data processing*
* **Settings:** review and make changes to source connection details, including authentication
* **Layout view:** choose between List view and Grid view

<figure><img src="/files/Bc3HRqC9w8Jp86MuMbHv" alt=""><figcaption><p>List view</p></figcaption></figure>

<figure><img src="/files/6Qm8i0FZC3SYlbMydHPg" alt=""><figcaption><p>Grid view</p></figcaption></figure>

## Access

Every cloud source has its own set of permissions. Invite members by email, pick a role (**View**, **Edit**, or **Source admin**), and set a workspace-default role from the **Share** dialog in the source's header. Private sources are hidden from members without access.

See [Permissions](/administration/felt-permissions.md#data-source-level-permissions) for the full model.

## Handling edits

[Editing layers](/layers/editing-layers.md) added from sources requires disabling live syncing from the original source. This is to prevent edits in Felt from being overwritten by the source when the layer refreshes. To proceed, add your edits to the layer (edit attribute, add feature, delete feature, etc) and then select **`Edit anyway`** from the popup.

<figure><img src="/files/Z4VQcAGN6jMch5FXDwMt" alt="" width="375"><figcaption></figcaption></figure>


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://help.felt.com/data-sources/cloud-sources.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
