Repository: SimpleDataLabsInc/prophecy-docs
Pull request #607: 4.0 connections enrichment
Author: login: kathweinschenkprophecy
Created: 2025-04-07T19:03:54Z | Merged: 2025-04-15T18:41:25Z



---
- To see the specific tasks where the Asana app for GitHub is being used, see below:
  - https://app.asana.com/0/0/1209860046557489


Diff:
diff --git a/docs/Spark/gems/source-target/file/csv.md b/docs/Spark/gems/source-target/file/csv.md
index a6a53c5cba1..b5a8e0978ee 100644
--- a/docs/Spark/gems/source-target/file/csv.md
+++ b/docs/Spark/gems/source-target/file/csv.md
@@ -23,14 +23,14 @@ import Requirements from '@site/src/components/gem-requirements';
 | Location Type            | Dependency versions                                                                                                                                                                  | Spark compatibility                                                                      |
 | ------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | ---------------------------------------------------------------------------------------- |
 | File Location            | <Requirements python_package_name="ProphecySparkBasicsPython" python_package_version="0.0.1+" scala_package_name="ProphecySparkBasicsScala" scala_package_version="0.0.1+"/>         | <Requirements uc_single="14.3+" uc_shared="14.3+" livy="3.0.1+"/>                        |
-| Sharepoint (Python only) | <Requirements python_package_name="ProphecySparkBasicsPython" python_package_version="0.2.35+" scala_package_name="ProphecySparkBasicsScala" scala_package_version="Not Available"/> | <Requirements uc_single="Not Supported" uc_shared="Not Supported" livy="Not Supported"/> |
+| SharePoint (Python only) | <Requirements python_package_name="ProphecySparkBasicsPython" python_package_version="0.2.35+" scala_package_name="ProphecySparkBasicsScala" scala_package_version="Not Available"/> | <Requirements uc_single="Not Supported" uc_shared="Not Supported" livy="Not Supported"/> |
 | SFTP (Python only)       | <Requirements python_package_name="ProphecySparkBasicsPython" python_package_version="0.2.35+" scala_package_name="ProphecySparkBasicsScala" scala_package_version="Not Available"/> | <Requirements uc_single="14.3+" uc_shared="Not Supported" livy="Not Supported"/>         |
 
 ## Parameters
 
 | Parameter | Tab        | Description                                                                                                                                                                                     |
 | --------- | ---------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
-| Read From | Location   | Which platform to read the file from. <br/>Possible values are: `File Location`, `Sharepoint` (Python only), or `SFTP` (Python only).                                                           |
+| Read From | Location   | Which platform to read the file from. <br/>Possible values are: `File Location`, `SharePoint` (Python only), or `SFTP` (Python only).                                                           |
 | Write To  | Location   | Which platform to write the file to. <br/>You can only select `File Location`.                                                                                                                  |
 | Location  | Location   | File path to read from or write to the CSV file.                                                                                                                                                |
 | Schema    | Properties | Schema to apply on the loaded data.<br/>In the Source gem, you can define or edit the schema visually or in JSON code.<br/>In the Target gem, you can view the schema visually or as JSON code. |
diff --git a/docs/administration/fabrics/Spark-fabrics/databricks/UCShared.md b/docs/administration/fabrics/Spark-fabrics/databricks/UCShared.md
index 88930f219f5..01342e6362d 100644
--- a/docs/administration/fabrics/Spark-fabrics/databricks/UCShared.md
+++ b/docs/administration/fabrics/Spark-fabrics/databricks/UCShared.md
@@ -52,7 +52,7 @@ Minimum Prophecy Package version required to support Databricks Unity Catalog Sh
 | Avro                      | ProphecySparkBasicsPython   | 0.2.39        | 0.2.39           | 0.2.39           |
 | Csv (Only File Path)      | ProphecySparkBasicsPython   | 0.2.39        | 0.2.39           | 0.2.39           |
 | Csv (SFTP - Source)       | ProphecySparkBasicsPython   | Not Supported | 0.2.44           | 0.2.44           |
-| Csv (Sharepoint - Source) | ProphecySparkBasicsPython   | Not Supported | 0.2.44           | 0.2.44           |
+| Csv (SharePoint - Source) | ProphecySparkBasicsPython   | Not Supported | 0.2.44           | 0.2.44           |
 | Delta                     | ProphecySparkBasicsPython   | 0.2.39        | 0.2.39           | 0.2.39           |
 | Json                      | ProphecySparkBasicsPython   | 0.2.39        | 0.2.39           | 0.2.39           |
 | ORC                       | ProphecySparkBasicsPython   | 0.2.39        | 0.2.39           | 0.2.39           |
diff --git a/docs/administration/fabrics/prophecy-fabrics/connections/connections.md b/docs/administration/fabrics/prophecy-fabrics/connections/connections.md
index d3818f1fdb2..3ec87e88fdf 100644
--- a/docs/administration/fabrics/prophecy-fabrics/connections/connections.md
+++ b/docs/administration/fabrics/prophecy-fabrics/connections/connections.md
@@ -25,11 +25,9 @@ If you are using a Prophecy fabric, you can add the following connections. You w
 | ------------------------------------ | -------------------- |
 | [Databricks](./databricks)           | Cloud data warehouse |
 | [Snowflake](./snowflake)             | Cloud data warehouse |
-| Databricks volumes                   | File store           |
-| Snowflake stage                      | File store           |
 | [Amazon S3](./s3)                    | File store           |
 | [SFTP](./sftp)                       | File store           |
-| [Microsoft Sharepoint](./sharepoint) | File store           |
+| [Microsoft SharePoint](./sharepoint) | File store           |
 | [Smartsheet](./smartsheet)           | Web application      |
 | [MSSQL](./mssql)                     | Database             |
 | [MongoDB](./mongodb)                 | Database             |
diff --git a/docs/administration/fabrics/prophecy-fabrics/connections/databricks.md b/docs/administration/fabrics/prophecy-fabrics/connections/databricks.md
index 33f1a43e69d..3f58994f847 100644
--- a/docs/administration/fabrics/prophecy-fabrics/connections/databricks.md
+++ b/docs/administration/fabrics/prophecy-fabrics/connections/databricks.md
@@ -8,6 +8,20 @@ tags:
   - databricks
 ---
 
+A Databricks connection lets you access your cloud data warehouse. It’s optimized for analytics and built to support modern data warehousing workloads with high performance and scalability.
+
+## Feature support
+
+The table below outlines whether the connection supports certain Prophecy features.
+
+| Feature                                                       | Supported |
+| ------------------------------------------------------------- | --------- |
+| Read data with a [Source gem](/analysts/source-target)        | Yes       |
+| Write data with a [Target gem](/analysts/source-target)       | Yes       |
+| Browse data in the [Environment browser](/analysts/pipelines) | Yes       |
+
+## Parameters
+
 To create a connection with Databricks, enter the following parameters:
 
 | Parameter             | Description                                          |
@@ -24,4 +38,50 @@ You can configure your Databricks connection with one of three authentication me
 
 - **Databricks [OAuth](docs/administration/authentication/databricks-oauth.md).** Prophecy prompts you to sign in with Databricks.
 - **Personal Access Token (PAT).** Use a [secret](docs/administration/secrets/secrets.md) to enter your PAT.
-- **Client Credentials.** Enter your Client ID and Client Secret (secret required) for authentication.
+
+## Databricks permissions
+
+When you create an Databricks connection in Prophecy, access permissions are tied to the credentials you use. This is because Prophecy uses your credentials to execute all data operations, such as reading from or writing to tables.
+
+To fully leverage a Databricks connection in Prophecy, you need the following Databricks permissions:
+
+- Create Schema
+- Create or Replace Table
+- Drop Table
+- Insert Into
+- Create Volume `PROPHECY_ORCHESTRATOR_VOLUME`
+- Access to `/Volumes/<catalog>/<schema>/PROPHECY_ORCHESTRATOR_VOLUME`
+- Remove File permission inside the volume
+- Copy Into (from the volume)
+
+## Sharing connections within teams
+
+Connections are stored inside fabrics, which are assigned to certain teams. The way Prophecy manages how Databricks connections are shared within teams depends on the authentication method used to configure the connection.
+
+### OAuth
+
+When you create a Databricks connection with OAuth:
+
+- Team members who use the connection will have to sign in with OAuth using their personal credentials.
+- Permissions will be inherited from their personal credentials.
+
+### Personal Access Token (PAT)
+
+When you create a Databricks connection using a PAT:
+
+- All team members that have access to the fabric can use the connection in their projects.
+- No additional authentication is required. Team members automatically inherit the access and permissions of the original connection.
+
+:::caution
+Be mindful of the access level granted by the stored credentials. Anyone on the team will have the same permissions—including access to sensitive data if allowed.
+
+To manage this securely, consider creating a dedicated fabric and team for high-sensitivity connections. This way, only approved users have access to those credentials.
+:::
+
+## Fetching data
+
+Prophecy fetches data from Databricks connections in the following ways:
+
+- When you browse an Databricks connection in the [Environment browser](/analysts/pipelines), Prophecy fetches data on demand as you expand folders. You can manually refresh the Environment browser to see updated files.
+
+- When a pipeline runs, Source gems will read the latest available version of the data. If the schema of your data in Databricks changes, Prophecy will automatically use the new schema.
diff --git a/docs/administration/fabrics/prophecy-fabrics/connections/img/smartsheet-duplicates.png b/docs/administration/fabrics/prophecy-fabrics/connections/img/smartsheet-duplicates.png
new file mode 100644
index 00000000000..3c3c3d6eb9d
Binary files /dev/null and b/docs/administration/fabrics/prophecy-fabrics/connections/img/smartsheet-duplicates.png differ
diff --git a/docs/administration/fabrics/prophecy-fabrics/connections/mongodb.md b/docs/administration/fabrics/prophecy-fabrics/connections/mongodb.md
index edfe27962f5..cebbc8793f8 100644
--- a/docs/administration/fabrics/prophecy-fabrics/connections/mongodb.md
+++ b/docs/administration/fabrics/prophecy-fabrics/connections/mongodb.md
@@ -7,6 +7,20 @@ tags:
   - mongodb
 ---
 
+MongoDB is a NoSQL database designed to store and retrieve unstructured or semi-structured data using BSON documents.
+
+## Feature support
+
+The table below outlines whether the connection supports certain Prophecy features.
+
+| Feature                                                       | Supported |
+| ------------------------------------------------------------- | --------- |
+| Read data with a [Source gem](/analysts/source-target)        | Yes       |
+| Write data with a [Target gem](/analysts/source-target)       | Yes       |
+| Browse data in the [Environment browser](/analysts/pipelines) | Yes       |
+
+## Parameters
+
 To create a connection with MongoDB, enter the following parameters:
 
 | Parameter                                                            | Description                                    |
@@ -18,3 +32,30 @@ To create a connection with MongoDB, enter the following parameters:
 | Password ([Secret required](docs/administration/secrets/secrets.md)) | Password for your MongoDB instance             |
 | Database                                                             | Default database for reading and writing data  |
 | Collection                                                           | Collection to use for the connection           |
+
+## MongoDB permissions
+
+When you create an MongoDB connection in Prophecy, access permissions are tied to the credentials you use. This is because Prophecy uses your credentials to execute all data operations, such as reading from or writing to collections.
+
+To fully leverage a MongoDB connection in Prophecy, you need the following MongoDB permissions:
+
+- `Read` from the collection defined in the connection
+- `Write` to the collection defined in the connection
+
+## Sharing connections within teams
+
+Connections in Prophecy are stored within [fabrics](docs/administration/fabrics/prophecy-fabrics/prophecy-fabrics.md), which are assigned to specific teams. Once a MongoDB connection is added to a fabric, all team members that have access to the fabric can use the connection in their projects. No additional authentication is required—team members automatically inherit the access and permissions of the original connection.
+
+:::caution
+Be mindful of the access level granted by the stored credentials. Anyone on the team will have the same permissions—including access to sensitive data if allowed.
+
+To manage this securely, consider creating a dedicated fabric and team for high-sensitivity connections. This way, only approved users have access to those credentials.
+:::
+
+## Fetching data
+
+Prophecy fetches data from MongoDB connections in the following ways:
+
+- When you browse an MongoDB connection in the [Environment browser](/analysts/pipelines), Prophecy fetches data on demand as you expand folders. You can manually refresh the Environment browser to see updated files.
+
+- When a pipeline runs, Source gems will read the latest available version of the data. Keep in mind that schema evolution may or may not be picked up automatically depending on the type of Source gem used.
diff --git a/docs/administration/fabrics/prophecy-fabrics/connections/mssql.md b/docs/administration/fabrics/prophecy-fabrics/connections/mssql.md
index b1c404618e8..6503e3fe975 100644
--- a/docs/administration/fabrics/prophecy-fabrics/connections/mssql.md
+++ b/docs/administration/fabrics/prophecy-fabrics/connections/mssql.md
@@ -7,6 +7,20 @@ tags:
   - msssql
 ---
 
+Use this connection to integrate with Microsoft SQL Server (MSSQL)—a relational database used for storing and querying structured data, with strong support for transactions, security, and complex SQL.
+
+## Feature support
+
+The table below outlines whether the connection supports certain Prophecy features.
+
+| Feature                                                       | Supported |
+| ------------------------------------------------------------- | --------- |
+| Read data with a [Source gem](/analysts/source-target)        | Yes       |
+| Write data with a [Target gem](/analysts/source-target)       | Yes       |
+| Browse data in the [Environment browser](/analysts/pipelines) | Yes       |
+
+## Parameters
+
 To create a connection with Microsoft SQL Server, enter the following parameters:
 
 | Parameter                                                            | Description                                     |
@@ -16,3 +30,25 @@ To create a connection with Microsoft SQL Server, enter the following parameters
 | Port                                                                 | Port to use for the connection                  |
 | Username                                                             | Username for your Microsoft SQL Server instance |
 | Password ([Secret required](docs/administration/secrets/secrets.md)) | Password for your Microsoft SQL Server instance |
+
+## MSSQL permissions
+
+When you create an MSSQL connection in Prophecy, access permissions are tied to the credentials you use. This is because Prophecy uses your credentials to execute all data operations, such as reading from or writing to tables. To fully leverage an MSSQL connection in Prophecy, you need read and write access to the tables you use.
+
+## Sharing connections within teams
+
+Connections in Prophecy are stored within [fabrics](docs/administration/fabrics/prophecy-fabrics/prophecy-fabrics.md), which are assigned to specific teams. Once a MSSQL connection is added to a fabric, all team members that have access to the fabric can use the connection in their projects. No additional authentication is required—team members automatically inherit the access and permissions of the original connection.
+
+:::caution
+Be mindful of the access level granted by the stored credentials. Anyone on the team will have the same permissions—including access to sensitive data if allowed.
+
+To manage this securely, consider creating a dedicated fabric and team for high-sensitivity connections. This way, only approved users have access to those credentials.
+:::
+
+## Fetching data
+
+Prophecy fetches data from MSSQL connections in the following ways:
+
+- When you browse a MSSQL connection in the [Environment browser](/analysts/pipelines), Prophecy fetches data on demand as you expand folders. You can manually refresh the Environment browser to see updated files.
+
+- When a pipeline runs, Source gems will read the latest available version of the data. If the schema of your data in MSSQL changes, Prophecy will automatically use the new schema.
diff --git a/docs/administration/fabrics/prophecy-fabrics/connections/s3.md b/docs/administration/fabrics/prophecy-fabrics/connections/s3.md
index 4810300a4ef..976a0add0d0 100644
--- a/docs/administration/fabrics/prophecy-fabrics/connections/s3.md
+++ b/docs/administration/fabrics/prophecy-fabrics/connections/s3.md
@@ -7,6 +7,20 @@ tags:
   - s3
 ---
 
+The S3 (Amazon Simple Storage Service) connection in Prophecy enables you to integrate with AWS S3, which is a scalable object storage service for storing and retrieving any amount of data.
+
+## Feature support
+
+The table below outlines whether the connection supports certain Prophecy features.
+
+| Feature                                                       | Supported |
+| ------------------------------------------------------------- | --------- |
+| Read data with a [Source gem](/analysts/source-target)        | Yes       |
+| Write data with a [Target gem](/analysts/source-target)       | Yes       |
+| Browse data in the [Environment browser](/analysts/pipelines) | Yes       |
+
+## Parameters
+
 To create a connection with your Amazon S3 buckets, enter the following parameters:
 
 | Parameter                                                                     | Description                                                    |
@@ -16,3 +30,30 @@ To create a connection with your Amazon S3 buckets, enter the following paramete
 | Secret Access Key ([Secret required](docs/administration/secrets/secrets.md)) | Your AWS secret access key                                     |
 | Region                                                                        | AWS region where your S3 bucket is located (e.g., `us-east-1`) |
 | Bucket Name                                                                   | Name of your S3 bucket                                         |
+
+## S3 permissions
+
+When you create an S3 connection in Prophecy, access permissions are tied to the AWS credentials you use. This is because Prophecy uses your credentials to execute all data operations, such as reading or writing files.
+
+To fully leverage an S3 connection in Prophecy, you need the following permissions:
+
+- For a bucket: `List`, `Write`
+- For an object/file: `Read`, `Write`
+
+## Sharing connections within teams
+
+Connections in Prophecy are stored within [fabrics](docs/administration/fabrics/prophecy-fabrics/prophecy-fabrics.md), which are assigned to specific teams. Once an S3 connection is added to a fabric, all team members that have access to the fabric can use the connection in their projects. No additional authentication is required—team members automatically inherit the access and permissions of the original connection.
+
+:::caution
+Be mindful of the access level granted by the stored credentials. Anyone on the team will have the same permissions—including access to sensitive data if allowed.
+
+To manage this securely, consider creating a dedicated fabric and team for high-sensitivity connections. This way, only approved users have access to those credentials.
+:::
+
+## Fetching data
+
+Prophecy fetches data from S3 connections in the following ways:
+
+- When you browse an S3 connection in the [Environment browser](/analysts/pipelines), Prophecy fetches data on demand as you expand folders. You can manually refresh the Environment browser to see updated files.
+
+- When a pipeline runs, Source gems will read the latest available version of the data. If the schema of the data stored in S3 changes, you will need to re-infer the schema in Prophecy.
diff --git a/docs/administration/fabrics/prophecy-fabrics/connections/sftp.md b/docs/administration/fabrics/prophecy-fabrics/connections/sftp.md
index 59f175e76b7..af06f8205ae 100644
--- a/docs/administration/fabrics/prophecy-fabrics/connections/sftp.md
+++ b/docs/administration/fabrics/prophecy-fabrics/connections/sftp.md
@@ -7,6 +7,30 @@ tags:
   - sftp
 ---
 
+SFTP (Secure File Transfer Protocol) is a secure way to transfer files over the internet using an encrypted connection between a client and a server. It’s commonly used to exchange data between systems, especially in enterprise environments where security and reliability are critical.
+
+In Prophecy, you can use an SFTP connection to read from and write to remote file systems directly in your data pipelines. This is useful when your data is stored outside cloud storage or databases, such as in on-premise servers or partner systems.
+
+## Feature support
+
+The table below outlines whether the connection supports certain Prophecy features.
+
+| Feature                                                       | Supported |
+| ------------------------------------------------------------- | --------- |
+| Read data with a [Source gem](/analysts/source-target)        | Yes       |
+| Write data with a [Target gem](/analysts/source-target)       | Yes       |
+| Browse data in the [Environment browser](/analysts/pipelines) | Yes       |
+
+## Limitations
+
+Keep in mind the following limitations when using an SFTP connection.
+
+- **Simultaneous writes can cause file corruption.** If multiple processes—such as different Prophecy jobs—try to write to the same file at the same time using the same SFTP connection details, it can result in race conditions or corrupted files. This happens because the connector doesn't perform any client-side locking to coordinate access.
+
+- **Network latency affects transfer performance.** The speed and reliability of SFTP transfers depend on the physical distance between the SFTP server and Prophecy’s infrastructure. Servers that are geographically closer to your Prophecy environment will generally provide faster, more stable performance. Servers located farther away may introduce higher latency, leading to slower or less consistent data transfers. For best results, use SFTP servers in the same region as your Prophecy environment.
+
+## Parameters
+
 To configure an SFTP connection in Prophecy, enter the following parameters:
 
 | Parameter             | Description                                                   |
@@ -23,3 +47,25 @@ You can configure your SFTP connection with one of the following authentication
 
 - **Password.** Use a [secret](docs/administration/secrets/secrets.md) to enter your SFTP password.
 - **Private key**. Upload a file that contains your SFTP private key.
+
+## SFTP permissions
+
+When you use an SFTP connection in Prophecy, permissions depend on the underlying SSH server and filesystem permissions on the server.
+
+## Sharing connections within teams
+
+Connections in Prophecy are stored within [fabrics](docs/administration/fabrics/prophecy-fabrics/prophecy-fabrics.md), which are assigned to specific teams. Once an SFTP connection is added to a fabric, all team members that have access to the fabric can use the connection in their projects. No additional authentication is required—team members automatically inherit the access and permissions of the original connection.
+
+:::caution
+Be mindful of the access level granted by the stored credentials. Anyone on the team will have the same permissions—including access to sensitive data if allowed.
+
+To manage this securely, consider creating a dedicated fabric and team for high-sensitivity connections. This way, only approved users have access to those credentials.
+:::
+
+## Fetching data
+
+Prophecy fetches data from SFTP connections in the following ways:
+
+- When you browse an SFTP connection in the [Environment browser](/analysts/pipelines), Prophecy fetches data on demand as you expand folders. You can manually refresh the Environment browser to see updated files.
+
+- When a pipeline runs, Source gems will read the latest available version of the data. If the schema changes in the external connection, you will need to re-infer the schema in Prophecy.
diff --git a/docs/administration/fabrics/prophecy-fabrics/connections/sharepoint.md b/docs/administration/fabrics/prophecy-fabrics/connections/sharepoint.md
index 4fe81f86c12..271bb77c85b 100644
--- a/docs/administration/fabrics/prophecy-fabrics/connections/sharepoint.md
+++ b/docs/administration/fabrics/prophecy-fabrics/connections/sharepoint.md
@@ -1,13 +1,38 @@
 ---
-title: Microsoft Sharepoint
+title: Microsoft SharePoint
 id: sharepoint
-description: Learn how to connect with Sharepoint
+description: Learn how to connect with SharePoint
 tags:
   - connections
   - sharepoint
 ---
 
-To create a connection with Sharepoint, enter the following parameters:
+The Microsoft SharePoint connection in Prophecy allows you to integrate SharePoint data into your workflows for analysis, transformation, and reporting. SharePoint is widely used for document management, collaboration, and storing structured or unstructured data.
+
+## Feature support
+
+The table below outlines whether the connection supports certain Prophecy features.
+
+| Feature                                                       | Supported |
+| ------------------------------------------------------------- | --------- |
+| Read data with a [Source gem](/analysts/source-target)        | Yes       |
+| Write data with a [Target gem](/analysts/source-target)       | Yes       |
+| Browse data in the [Environment browser](/analysts/pipelines) | Yes       |
+
+## Limitations
+
+Prophecy can only access files stored in the [document library](https://support.microsoft.com/en-us/office/what-is-a-document-library-3b5976dd-65cf-4c9e-bf5a-713c10ca2872) of your SharePoint site. Make sure any files you want to import are placed there.
+
+## Prerequisites
+
+To use a SharePoint connection, your Microsoft account admin needs to:
+
+- [Register Prophecy](https://learn.microsoft.com/en-us/entra/identity-platform/quickstart-register-app) as an application in Microsoft.
+- Grant the following application-level permission to the application: `Sites.Manage.All`.
+
+## Parameters
+
+To create a connection with SharePoint, enter the following parameters:
 
 | Parameter                                                                 | Description                                                                                     |
 | ------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------- |
@@ -16,3 +41,27 @@ To create a connection with Sharepoint, enter the following parameters:
 | Client ID                                                                 | Your SharePoint Client ID                                                                       |
 | Client Secret ([Secret required](docs/administration/secrets/secrets.md)) | Your SharePoint Client Secret                                                                   |
 | Site URL                                                                  | URL of the SharePoint site to connect (e.g., `https://yourcompany.sharepoint.com/sites/mysite`) |
+
+## SharePoint permissions
+
+When you create a SharePoint connection in Prophecy, access permissions are tied to the credentials you use. This is because Prophecy uses your credentials to execute all data operations, such as reading from or writing to your document library. For example, if you are a `Visitor` on a site, you won't be able to edit site content from Prophecy.
+
+To learn more about SharePoint permissions, [click here](https://support.microsoft.com/en-us/office/overview-site-governance-permission-and-sharing-for-site-owners-95e83c3d-e1b0-4aae-9d08-e94dcaa4942e).
+
+## Sharing connections within teams
+
+Connections in Prophecy are stored within [fabrics](docs/administration/fabrics/prophecy-fabrics/prophecy-fabrics.md), which are assigned to specific teams. Once a SharePoint connection is added to a fabric, all team members that have access to the fabric can use the connection in their projects. No additional authentication is required—team members automatically inherit the access and permissions of the original connection.
+
+:::caution
+Be mindful of the access level granted by the stored credentials. Anyone on the team will have the same permissions—including access to sensitive data if allowed.
+
+To manage this securely, consider creating a dedicated fabric and team for high-sensitivity connections. This way, only approved users have access to those credentials.
+:::
+
+## Fetching data
+
+Prophecy fetches data from SharePoint in the following ways:
+
+- When you browse a SharePoint connection in the [Environment browser](/analysts/pipelines), Prophecy fetches data on demand as you expand folders. You can manually refresh the Environment browser to see updated files.
+
+- When a pipeline runs, Source gems will read the latest available version of the data. If the schema of the data stored in SharePoint changes, you will need to re-infer the schema in Prophecy.
diff --git a/docs/administration/fabrics/prophecy-fabrics/connections/smartsheet.md b/docs/administration/fabrics/prophecy-fabrics/connections/smartsheet.md
index 28aff138886..11e3f8f88db 100644
--- a/docs/administration/fabrics/prophecy-fabrics/connections/smartsheet.md
+++ b/docs/administration/fabrics/prophecy-fabrics/connections/smartsheet.md
@@ -7,9 +7,61 @@ tags:
   - smartsheet
 ---
 
+Smartsheet manages tasks, projects, and workflows using a spreadsheet-like interface that can contain rows, columns, and cell data. Prophecy uses the [Smartsheet API](https://developers.smartsheet.com/api/smartsheet/introduction) to establish the connection.
+
+## Feature support
+
+The table below outlines whether the connection supports certain Prophecy features.
+
+| Feature                                                       | Supported |
+| ------------------------------------------------------------- | --------- |
+| Read data with a [Source gem](/analysts/source-target)        | Yes       |
+| Write data with a [Target gem](/analysts/source-target)       | Yes       |
+| Browse data in the [Environment browser](/analysts/pipelines) | Yes       |
+
+## Limitations
+
+Keep in mind the following limitations when using the Smartsheet connection.
+
+- Smartsheet defines capacity limits in their [Limitations](https://developers.smartsheet.com/api/smartsheet/guides/basics/limitations) documentation.
+
+- Smartsheet allows users to create sheets with the same name in the same file location. Prophecy handles this situation in the following ways:
+
+  - **Writing to Smartsheet when there are duplicate files.** In this case, the pipeline run will fail in Prophecy. Prophecy will not choose which file to overwrite with the Target gem.
+
+  - **Reading from Smartsheet when there are duplicate files.** In this case, Prophecy appends a `(n)` to the duplicate files for differentiation in Prophecy.
+
+  ![Duplicate Smartsheet file in Prophecy file browser](img/smartsheet-duplicates.png)
+
+## Parameters
+
 To create a connection with Smartsheet, enter the following parameters:
 
-| Parameter                                                                | Description                                                     |
-| ------------------------------------------------------------------------ | --------------------------------------------------------------- |
-| Connection Name                                                          | Unique name for the connection (e.g., `MySmartsheetConnection`) |
-| Access Token ([Secret required](docs/administration/secrets/secrets.md)) | Your Smartsheet API access token                                |
+| Parameter                                                                | Description                                                                                                                                   |
+| ------------------------------------------------------------------------ | --------------------------------------------------------------------------------------------------------------------------------------------- |
+| Connection Name                                                          | Unique name for the connection (e.g., `MySmartsheetConnection`)                                                                               |
+| Access Token ([Secret required](docs/administration/secrets/secrets.md)) | Your [Smartsheet API access token](https://developers.smartsheet.com/api/smartsheet/guides/basics/authentication#access-token-best-practices) |
+
+## Smartsheet permissions
+
+When you create a Smartsheet connection in Prophecy, access permissions are tied to the credentials you use. This is because Prophecy uses your credentials to execute all data operations, such as reading or writing sheets. For example, if you are a `Viewer` on a sheet, you won't be able to write data to that sheet with a Target gem.
+
+To learn more about Smartsheet permissions, visit [Sharing permission levels](https://help.smartsheet.com/articles/1155182-sharing-permission-levels).
+
+## Sharing connections within teams
+
+Connections in Prophecy are stored within [fabrics](docs/administration/fabrics/prophecy-fabrics/prophecy-fabrics.md), which are assigned to specific teams. Once a Smartsheet connection is added to a fabric, all team members that have access to the fabric can use the connection in their projects. No additional authentication is required—team members automatically inherit the access and permissions of the original connection.
+
+:::caution
+Be mindful of the access level granted by the stored credentials. Anyone on the team will have the same permissions—including access to sensitive data if allowed.
+
+To manage this securely, consider creating a dedicated fabric and team for high-sensitivity connections. This way, only approved users have access to those credentials.
+:::
+
+## Fetching data
+
+Prophecy fetches data from Smartsheet in the following ways:
+
+- When you browse a Smartsheet connection in the [Environment browser](/analysts/pipelines), Prophecy fetches data on demand as you expand folders. You can manually refresh the Environment browser to see updated files.
+
+- When a pipeline runs, Source gems will read the latest available version of the data. If the schema changes in Smartsheet, you will need to re-infer the schema in Prophecy.
diff --git a/docs/administration/fabrics/prophecy-fabrics/connections/smpt.md b/docs/administration/fabrics/prophecy-fabrics/connections/smpt.md
deleted file mode 100644
index 61e147db367..00000000000
--- a/docs/administration/fabrics/prophecy-fabrics/connections/smpt.md
+++ /dev/null
@@ -1,20 +0,0 @@
----
-title: SMTP
-id: smtp
-description: Learn how to configure an SMTP connection
-tags:
-  - connections
-  - smtp
----
-
-To create an SMTP connection, enter the following parameters:
-
-| Parameter                                                            | Description                                               |
-| -------------------------------------------------------------------- | --------------------------------------------------------- |
-| Connection Name                                                      | Unique name for the connection (e.g., `MySMTPConnection`) |
-| URL                                                                  | SMTP server URL (e.g., `smtp.gmail.com`)                  |
-| Port                                                                 | SMTP port. Port options may vary between SMTP services.   |
-| Username                                                             | Your SMTP username                                        |
-| Password ([Secret required](docs/administration/secrets/secrets.md)) | Your SMTP password                                        |
-
-<!-- You can leverage your SMTP connection to send emails with the [Email](docs/analysts/development/gems/report/email.md) gem. -->
diff --git a/docs/administration/fabrics/prophecy-fabrics/connections/smtp.md b/docs/administration/fabrics/prophecy-fabrics/connections/smtp.md
new file mode 100644
index 00000000000..4ee8c1d5748
--- /dev/null
+++ b/docs/administration/fabrics/prophecy-fabrics/connections/smtp.md
@@ -0,0 +1,42 @@
+---
+title: SMTP
+id: smtp
+description: Learn how to configure an SMTP connection
+tags:
+  - connections
+  - smtp
+---
+
+SMTP (Simple Mail Transfer Protocol) connections are used to send emails over the internet by allowing communication between email clients and servers. When you create an SMTP connection in Prophecy, the user credentials you provide are used to establish the connection. This user will always be the sender of an email when you use the Email gem with this connection.
+
+## Feature support
+
+The table below outlines whether the connection supports certain Prophecy features.
+
+| Feature                                                       | Supported |
+| ------------------------------------------------------------- | --------- |
+| Read data with a [Source gem](/analysts/source-target)        | No        |
+| Write data with a Report gem                                  | Yes       |
+| Browse data in the [Environment browser](/analysts/pipelines) | No        |
+
+## Limitations
+
+Only basic authentication is supported. The SMTP server must support plain username and password authentication. Prophecy does not currently support OAuth or other advanced authentication methods for SMTP connections.
+
+## Parameters
+
+To create an SMTP connection, enter the following parameters:
+
+| Parameter                                                            | Description                                               |
+| -------------------------------------------------------------------- | --------------------------------------------------------- |
+| Connection Name                                                      | Unique name for the connection (e.g., `MySMTPConnection`) |
+| URL                                                                  | SMTP server URL (e.g., `smtp.gmail.com`)                  |
+| Port                                                                 | SMTP port. Port options may vary between SMTP services.   |
+| Username                                                             | Your SMTP username                                        |
+| Password ([Secret required](docs/administration/secrets/secrets.md)) | Your SMTP password                                        |
+
+<!-- You can leverage your SMTP connection to send emails with the [Email](docs/analysts/development/gems/report/email.md) gem. -->
+
+## Sharing connections within teams
+
+Connections in Prophecy are stored within [fabrics](docs/administration/fabrics/prophecy-fabrics/prophecy-fabrics.md), which are assigned to specific teams. Once an SMTP connection is added to a fabric, anyone in the team can use that connection to send emails from a pipeline.
diff --git a/docs/administration/fabrics/prophecy-fabrics/connections/snowflake.md b/docs/administration/fabrics/prophecy-fabrics/connections/snowflake.md
index 9f9ce8d6cca..b770a2e7c34 100644
--- a/docs/administration/fabrics/prophecy-fabrics/connections/snowflake.md
+++ b/docs/administration/fabrics/prophecy-fabrics/connections/snowflake.md
@@ -8,6 +8,27 @@ tags:
   - snowflake
 ---
 
+Learn how to set up and use a Snowflake connection in Prophecy. With a Snowflake connection, you can read from and write to your Snowflake data warehouse using Source and Target gems, browse data in the Environment browser, and run pipelines that process Snowflake data.
+
+## Feature support
+
+The table below outlines whether the connection supports certain Prophecy features.
+
+| Feature                                                       | Supported |
+| ------------------------------------------------------------- | --------- |
+| Read data with a [Source gem](/analysts/source-target)        | Yes       |
+| Write data with a [Target gem](/analysts/source-target)       | Yes       |
+| Browse data in the [Environment browser](/analysts/pipelines) | Yes       |
+
+## Limitations
+
+There are a few limitations on the data types you can read from Snowflake:
+
+- Prophecy reads `Object`, `Array`, and `Variant` types as `String` type.
+- Prophecy does not support writing `Binary` type columns.
+
+## Parameters
+
 To create a connection with Snowflake, enter the following parameters:
 
 | Parameter             | Description                                                                                                          |
@@ -18,11 +39,51 @@ To create a connection with Snowflake, enter the following parameters:
 | Schema                | Default schema for reading and writing data                                                                          |
 | Warehouse             | Name of the SQL warehouse to use for the connection                                                                  |
 | Role                  | Snowflake [role](https://docs.snowflake.com/en/user-guide/security-access-control-overview) of the user to connect   |
-| Authentication method | How you want to authenticate your Snowflake account                                                                  |
+| Authentication method | Enter your Snowflake username and use a [secret](docs/administration/secrets/secrets.md) to enter your password.     |
 
-## Authentication methods
+<!-- ## Authentication methods
 
 You can configure your Snowflake connection with one of the following authentication methods:
 
 - **Snowflake [OAuth](docs/administration/authentication/databricks-oauth.md).** Prophecy prompts you to sign in with Snowflake.
-- **Password**. Enter your Snowflake username and use a [secret](docs/administration/secrets/secrets.md) to enter your password.
+- **Password**. Enter your Snowflake username and use a [secret](docs/administration/secrets/secrets.md) to enter your password. -->
+
+## Snowflake permissions
+
+When you create a Snowflake connection in Prophecy, all access is governed by the Snowflake credentials you provide. This is because Prophecy uses your credentials to execute all data operations, such as reading or writing files.
+
+To successfully use a Snowflake connection in Prophecy, make sure your Snowflake user has the following permissions:
+
+- **Read and write access to target tables**  
+  Your user must be able to `SELECT`, `INSERT`, `UPDATE`, and `DELETE` on the specific tables used in your Prophecy pipelines.
+
+- **Ownership of target tables**  
+  Prophecy may require full control of the table (including altering or replacing it). This means the role should have `OWNERSHIP` on the table.
+
+- **Create and use file formats**  
+  Prophecy writes data to Snowflake by first uploading Parquet files to a stage. You need:
+
+  - Permission to `CREATE FILE FORMAT` in the target schema
+
+  - `USAGE` on any existing file formats used for reading/writing Parquet
+
+- **Write access to a stage**  
+  Typically, Prophecy uses your **user stage** for uploading Parquet files, so your user needs permission to write to that stage.
+
+## Sharing connections within teams
+
+Connections in Prophecy are stored within [fabrics](docs/administration/fabrics/prophecy-fabrics/prophecy-fabrics.md), which are assigned to specific teams. Once a Snowflake connection is added to a fabric, all team members that have access to the fabric can use the connection in their projects. No additional authentication is required—team members automatically inherit the access and permissions of the original connection.
+
+:::caution
+Be mindful of the access level granted by the stored credentials. Anyone on the team will have the same permissions—including access to sensitive data if allowed.
+
+To manage this securely, consider creating a dedicated fabric and team for high-sensitivity connections. This way, only approved users have access to those credentials.
+:::
+
+## Fetching data
+
+Prophecy fetches data from Snowflake connections in the following ways:
+
+- When you browse a Snowflake connection in the [Environment browser](/analysts/pipelines), Prophecy fetches data on demand as you expand folders. You can manually refresh the Environment browser to see updated files.
+
+- When a pipeline runs, Source gems will read the latest available version of the data. If the schema of your data in Snowflake changes, Prophecy will automatically use the new schema.
diff --git a/docs/administration/fabrics/prophecy-fabrics/connections/tableau.md b/docs/administration/fabrics/prophecy-fabrics/connections/tableau.md
index 5928ed32b8f..59798b702ce 100644
--- a/docs/administration/fabrics/prophecy-fabrics/connections/tableau.md
+++ b/docs/administration/fabrics/prophecy-fabrics/connections/tableau.md
@@ -7,6 +7,28 @@ tags:
   - tableau
 ---
 
+Use a Tableau connection to publish and update data sources in your Tableau projects directly from Prophecy pipelines.
+
+Prophecy uses the [Tableau REST API](https://help.tableau.com/current/api/rest_api/en-us/REST/rest_api.htm) to perform actions like sign in, data upload, and data source publication. Your data is sent to Tableau as `Hyper` files (Tableau’s high-performance, in-memory format).
+
+## Feature support
+
+The table below outlines whether the connection supports certain Prophecy features.
+
+| Feature                                                       | Supported |
+| ------------------------------------------------------------- | --------- |
+| Read data with a [Source gem](/analysts/source-target)        | No        |
+| Write data with a Report gem                                  | Yes       |
+| Browse data in the [Environment browser](/analysts/pipelines) | No        |
+
+## Limitations
+
+Using Tableau Hyper files is a legacy approach that Prophecy supports mainly for backward compatibility. It helps users keep existing dashboards running smoothly while migrating from older systems.
+
+For a modern, cloud-native workflow, write pipeline outputs directly to a supported cloud data platform like Databricks, Snowflake, or BigQuery. Then connect Tableau to that platform to visualize the data—no need to set up a separate Tableau connection or perform extra export steps in Prophecy.
+
+## Parameters
+
 To create a connection with Tableau, enter the following parameters:
 
 | Parameter                                                                 | Description                                                      |
@@ -18,3 +40,13 @@ To create a connection with Tableau, enter the following parameters:
 | Tableau Site Name                                                         | Name of the Tableau site you're connecting to                    |
 
 <!-- You can leverage your Tableau connection with the [TableauWrite](docs/analysts/development/gems/report/tableau.md) gem. -->
+
+## Tableau permissions
+
+When you use a Tableau connection in Prophecy, permissions are determined by the credentials you provide. To use the connection to publish data, those credentials must have the **Publish** capability in Tableau for the project containing the target data source.
+
+For more details on Tableau permissions, see their documentation on [Permission Capabilities](https://help.tableau.com/current/server/en-us/permissions_capabilities.htm).
+
+## Sharing connections within teams
+
+Tableau connections are stored within [fabrics](docs/administration/fabrics/prophecy-fabrics/prophecy-fabrics.md), which are assigned to specific teams in Prophecy. Once a Tableau connection is added to a fabric, anyone on that team can use it to send data to Tableau from their pipelines. Everyone will inherit the permissions of the user authenticated during connection setup.
diff --git a/docs/analysts/development/connections.md b/docs/analysts/development/connections.md
index 71c6c10b6e2..c4ba37f5d24 100644
--- a/docs/analysts/development/connections.md
+++ b/docs/analysts/development/connections.md
@@ -16,6 +16,10 @@ As you build your pipelines, you'll be able to:
 - Browse data from established connections in the Environment browser.
 - Add data to your pipeline directly from the Environment browser.
 
+:::info
+See the [list of connections](docs/administration/fabrics/prophecy-fabrics/connections/connections.md) in the Administration section of the documentation to find all available connections.
+:::
+
 ## Connections in the Environment browser
 
 Connections allow Prophecy to access specific data from external providers using your credentials. The data will appear in the [Environment browser](docs/analysts/development/pipelines/pipelines.md#sidebar) of the project sidebar, allowing you to easily locate data, explore data, and add data to your pipeline canvas. Data access permissions are inherited from your external user account.
diff --git a/docs/analysts/development/gems/source-target/file/csv.md b/docs/analysts/development/gems/source-target/file/csv.md
index f4bfb7b8500..d4822aabc40 100644
--- a/docs/analysts/development/gems/source-target/file/csv.md
+++ b/docs/analysts/development/gems/source-target/file/csv.md
@@ -8,7 +8,7 @@ tags: []
 
 <span class="badge">Prophecy Automate</span><br/><br/>
 
-Read or write a CSV file from an S3, SFTP, Sharepoint, or Databricks connection.
+Read or write a CSV file from an S3, SFTP, SharePoint, or Databricks connection.
 
 :::info
 You can also use the [upload file](docs/analysts/development/gems/source-target/table/upload-files.md) feature to use CSV files. These will be stored in the SQL warehouse configured in your fabric.
diff --git a/docs/analysts/development/gems/source-target/file/excel.md b/docs/analysts/development/gems/source-target/file/excel.md
index d2bfde9e42a..eeabc4865eb 100644
--- a/docs/analysts/development/gems/source-target/file/excel.md
+++ b/docs/analysts/development/gems/source-target/file/excel.md
@@ -8,7 +8,7 @@ tags: []
 
 <span class="badge">Prophecy Automate</span><br/><br/>
 
-Read or write an Excel (XLSX) file from an S3, SFTP, Sharepoint, Smartsheet, or Databricks connection.
+Read or write an Excel (XLSX) file from an S3, SFTP, SharePoint, Smartsheet, or Databricks connection.
 
 :::info
 You can also use the [upload file](docs/analysts/development/gems/source-target/table/upload-files.md) feature to use Excel files. These will be stored in the SQL warehouse configured in your fabric.
diff --git a/docs/analysts/development/gems/source-target/file/json.md b/docs/analysts/development/gems/source-target/file/json.md
index 3419663b786..306cf6c9edd 100644
--- a/docs/analysts/development/gems/source-target/file/json.md
+++ b/docs/analysts/development/gems/source-target/file/json.md
@@ -8,7 +8,7 @@ tags: []
 
 <span class="badge">Prophecy Automate</span><br/><br/>
 
-Read or write a JSON file from an S3, SFTP, Sharepoint, or Databricks connection.
+Read or write a JSON file from an S3, SFTP, SharePoint, or Databricks connection.
 
 :::info
 You can also use the [upload file](docs/analysts/development/gems/source-target/table/upload-files.md) feature to use JSON files. These will be stored in the SQL warehouse configured in your fabric.
diff --git a/docs/analysts/development/gems/source-target/file/xml.md b/docs/analysts/development/gems/source-target/file/xml.md
index e817a0f190f..8edb07f7cc0 100644
--- a/docs/analysts/development/gems/source-target/file/xml.md
+++ b/docs/analysts/development/gems/source-target/file/xml.md
@@ -8,7 +8,7 @@ tags: []
 
 <span class="badge">Prophecy Automate</span><br/><br/>
 
-Read or write an XML file from an S3, SFTP, Sharepoint, or Databricks connection.
+Read or write an XML file from an S3, SFTP, SharePoint, or Databricks connection.
 
 :::info
 You can also use the [upload file](docs/analysts/development/gems/source-target/table/upload-files.md) feature to use XML files. These will be stored in the SQL warehouse configured in your fabric.
diff --git a/docs/analysts/development/gems/source-target/source-target.md b/docs/analysts/development/gems/source-target/source-target.md
index 7e166ca2f67..b0f8247cded 100644
--- a/docs/analysts/development/gems/source-target/source-target.md
+++ b/docs/analysts/development/gems/source-target/source-target.md
@@ -62,6 +62,6 @@ The following connections support file sources and targets.
 | --------------------------------------------------------------------------------------- | ---------------------- |
 | [Amazon S3](/administration/fabrics/prophecy-fabrics/connections/s3)                    | CSV, JSON, XLSX, XML   |
 | [SFTP](/administration/fabrics/prophecy-fabrics/connections/sftp)                       | CSV, JSON, XLSX, XML   |
-| [Microsoft Sharepoint](/administration/fabrics/prophecy-fabrics/connections/sharepoint) | CSV, JSON, XLSX, XML   |
+| [Microsoft SharePoint](/administration/fabrics/prophecy-fabrics/connections/sharepoint) | CSV, JSON, XLSX, XML   |
 | [Databricks](/administration/fabrics/prophecy-fabrics/connections/databricks)           | CSV, JSON, XLSX, XML   |
 | [Smartsheet](/administration/fabrics/prophecy-fabrics/connections/smartsheet)           | XLSX                   |


Reviews:
user: login: khagesh-patel
state: COMMENTED
author_association: NONE
submitted_at: 2025-04-11T13:02:33Z
user: login: tnmy44
state: COMMENTED
author_association: NONE
submitted_at: 2025-04-13T07:42:19Z
user: login: kathweinschenkprophecy
state: COMMENTED
author_association: CONTRIBUTOR
submitted_at: 2025-04-14T13:39:23Z
user: login: kathweinschenkprophecy
state: COMMENTED
author_association: CONTRIBUTOR
submitted_at: 2025-04-14T13:39:50Z
user: login: kathweinschenkprophecy
state: COMMENTED
author_association: CONTRIBUTOR
submitted_at: 2025-04-14T13:40:33Z
user: login: kailie-prophecy
body: Looks good overall -- just some wording suggestions/nits to consider before I approve :)
state: COMMENTED
author_association: CONTRIBUTOR
submitted_at: 2025-04-14T21:15:24Z
user: login: kathweinschenkprophecy
state: COMMENTED
author_association: CONTRIBUTOR
submitted_at: 2025-04-15T17:00:04Z
user: login: kathweinschenkprophecy
state: COMMENTED
author_association: CONTRIBUTOR
submitted_at: 2025-04-15T17:11:33Z
user: login: kathweinschenkprophecy
state: COMMENTED
author_association: CONTRIBUTOR
submitted_at: 2025-04-15T17:17:31Z
user: login: kathweinschenkprophecy
state: COMMENTED
author_association: CONTRIBUTOR
submitted_at: 2025-04-15T17:18:08Z
user: login: kathweinschenkprophecy
state: COMMENTED
author_association: CONTRIBUTOR
submitted_at: 2025-04-15T17:27:36Z
user: login: kathweinschenkprophecy
state: COMMENTED
author_association: CONTRIBUTOR
submitted_at: 2025-04-15T17:29:01Z
user: login: kathweinschenkprophecy
state: COMMENTED
author_association: CONTRIBUTOR
submitted_at: 2025-04-15T17:31:16Z
user: login: kailie-prophecy
body: Looks AMAZING 🤩 LGTM % moving limitations higher and a minor nit!
state: APPROVED
author_association: CONTRIBUTOR
submitted_at: 2025-04-15T18:19:31Z
user: login: kathweinschenkprophecy
state: COMMENTED
author_association: CONTRIBUTOR
submitted_at: 2025-04-15T18:38:17Z
user: login: kailie-prophecy
state: COMMENTED
author_association: CONTRIBUTOR
submitted_at: 2025-04-15T18:39:14Z

Review comments:
diff_hunk: @@ -18,3 +28,18 @@ To create a connection with Tableau, enter the following parameters:
 | Tableau Site Name                                                         | Name of the Tableau site you're connecting to                    |
 
 <!-- You can leverage your Tableau connection with the [TableauWrite](docs/analysts/development/gems/report/tableau.md) gem. -->
+
+## Tableau permissions
+
+When you create an Tableau connection in Prophecy, access permissions are tied to the credentials you use. To fully leverage an Tableau connection in Prophecy, you need the following Tableau permissions:
+
+- Example
+- Example
path: docs/administration/fabrics/prophecy-fabrics/connections/tableau.md
user: login: khagesh-patel
body: we can mention publish permission on the project
created_at: 2025-04-11T12:56:39Z
author_association: NONE
diff_hunk: @@ -16,3 +26,32 @@ To create a connection with your Amazon S3 buckets, enter the following paramete
 | Secret Access Key ([Secret required](docs/administration/secrets/secrets.md)) | Your AWS secret access key                                     |
 | Region                                                                        | AWS region where your S3 bucket is located (e.g., `us-east-1`) |
 | Bucket Name                                                                   | Name of your S3 bucket                                         |
+
+## S3 permissions
+
+When you create an S3 connection in Prophecy, access permissions are tied to the credentials you use. This means you will only see the files and folders your S3 credentials have permission to access. Any actions you perform—such as reading or writing files—are done using those credentials.
path: docs/administration/fabrics/prophecy-fabrics/connections/s3.md
user: login: tnmy44
body: Instead of "S3 credentials", let's call it "AWS Credentials" since they are tied to an AWS account
created_at: 2025-04-13T07:15:28Z
author_association: NONE
diff_hunk: @@ -16,3 +26,32 @@ To create a connection with your Amazon S3 buckets, enter the following paramete
 | Secret Access Key ([Secret required](docs/administration/secrets/secrets.md)) | Your AWS secret access key                                     |
 | Region                                                                        | AWS region where your S3 bucket is located (e.g., `us-east-1`) |
 | Bucket Name                                                                   | Name of your S3 bucket                                         |
+
+## S3 permissions
+
+When you create an S3 connection in Prophecy, access permissions are tied to the credentials you use. This means you will only see the files and folders your S3 credentials have permission to access. Any actions you perform—such as reading or writing files—are done using those credentials.
+
+To fully leverage an S3 connection in Prophecy, you need the following S3 permissions:
path: docs/administration/fabrics/prophecy-fabrics/connections/s3.md
user: login: tnmy44
body: A user needs these permissions:
- For a Bucket: List, Write
- For an object/file: Read, Write

Reference: https://docs.aws.amazon.com/AmazonS3/latest/userguide/acl-overview.html?icmpid=docs_amazons3_console

created_at: 2025-04-13T07:24:15Z
author_association: NONE
diff_hunk: @@ -16,3 +26,32 @@ To create a connection with your Amazon S3 buckets, enter the following paramete
 | Secret Access Key ([Secret required](docs/administration/secrets/secrets.md)) | Your AWS secret access key                                     |
 | Region                                                                        | AWS region where your S3 bucket is located (e.g., `us-east-1`) |
 | Bucket Name                                                                   | Name of your S3 bucket                                         |
+
+## S3 permissions
+
+When you create an S3 connection in Prophecy, access permissions are tied to the credentials you use. This means you will only see the files and folders your S3 credentials have permission to access. Any actions you perform—such as reading or writing files—are done using those credentials.
+
+To fully leverage an S3 connection in Prophecy, you need the following S3 permissions:
+
+- Example
+- Example
+
+## Sharing connections within teams
path: docs/administration/fabrics/prophecy-fabrics/connections/s3.md
user: login: tnmy44
body: Since this section is common across all connections? Do we need it separately in every connection's page? Would it make sense to put it in the top level page for connectors? 
created_at: 2025-04-13T07:26:54Z
author_association: NONE
diff_hunk: @@ -16,3 +26,32 @@ To create a connection with your Amazon S3 buckets, enter the following paramete
 | Secret Access Key ([Secret required](docs/administration/secrets/secrets.md)) | Your AWS secret access key                                     |
 | Region                                                                        | AWS region where your S3 bucket is located (e.g., `us-east-1`) |
 | Bucket Name                                                                   | Name of your S3 bucket                                         |
+
+## S3 permissions
+
+When you create an S3 connection in Prophecy, access permissions are tied to the credentials you use. This means you will only see the files and folders your S3 credentials have permission to access. Any actions you perform—such as reading or writing files—are done using those credentials.
+
+To fully leverage an S3 connection in Prophecy, you need the following S3 permissions:
+
+- Example
+- Example
+
+## Sharing connections within teams
+
+Connections in Prophecy are stored within [fabrics](docs/administration/fabrics/prophecy-fabrics/prophecy-fabrics.md), which are assigned to specific teams. Once an S3 connection is added to a fabric, all team members that have access to the fabric can use the connection in their projects. No additional authentication is required—team members automatically inherit the access and permissions of the original connection.
+
+:::caution
+Be mindful of the access level granted by the stored credentials. Anyone on the team will have the same permissions—including access to sensitive data if allowed.
+
+To manage this securely, consider creating a dedicated fabric and team for high-sensitivity connections. This way, only approved users have access to those credentials.
+:::
+
+## Sync connection
path: docs/administration/fabrics/prophecy-fabrics/connections/s3.md
user: login: tnmy44
body: Same with this, since this is common across all connectors, should this be moved to a common page?
created_at: 2025-04-13T07:27:50Z
author_association: NONE
diff_hunk: @@ -16,3 +26,32 @@ To create a connection with your Amazon S3 buckets, enter the following paramete
 | Secret Access Key ([Secret required](docs/administration/secrets/secrets.md)) | Your AWS secret access key                                     |
 | Region                                                                        | AWS region where your S3 bucket is located (e.g., `us-east-1`) |
 | Bucket Name                                                                   | Name of your S3 bucket                                         |
+
+## S3 permissions
+
+When you create an S3 connection in Prophecy, access permissions are tied to the credentials you use. This means you will only see the files and folders your S3 credentials have permission to access. Any actions you perform—such as reading or writing files—are done using those credentials.
+
+To fully leverage an S3 connection in Prophecy, you need the following S3 permissions:
+
+- Example
+- Example
+
+## Sharing connections within teams
+
+Connections in Prophecy are stored within [fabrics](docs/administration/fabrics/prophecy-fabrics/prophecy-fabrics.md), which are assigned to specific teams. Once an S3 connection is added to a fabric, all team members that have access to the fabric can use the connection in their projects. No additional authentication is required—team members automatically inherit the access and permissions of the original connection.
+
+:::caution
+Be mindful of the access level granted by the stored credentials. Anyone on the team will have the same permissions—including access to sensitive data if allowed.
+
+To manage this securely, consider creating a dedicated fabric and team for high-sensitivity connections. This way, only approved users have access to those credentials.
+:::
+
+## Sync connection
+
+Prophecy fetches data from S3 connections in the following ways:
+
+- When you browse an S3 connection in the [Environment browser](/analysts/pipelines), Prophecy fetches data on demand as you expand folders. You can manually refresh the Environment browser to see updated files.
+
+- When a pipeline runs, Source gems will read the latest available version of the data. Keep in mind that schema evolution may or may not be picked up automatically depending on the type of Source gem used.
path: docs/administration/fabrics/prophecy-fabrics/connections/s3.md
user: login: tnmy44
body: This last line seems a little vague and unhelpful. Maybe we can rephrase it to something like:  if the schema of the data stored in S3 was changed, you will need to do "Infer Schema" again from the Source gem to get the updated data.

Please rephrase as required
created_at: 2025-04-13T07:34:31Z
author_association: NONE
diff_hunk: @@ -16,3 +26,32 @@ To create a connection with your Amazon S3 buckets, enter the following paramete
 | Secret Access Key ([Secret required](docs/administration/secrets/secrets.md)) | Your AWS secret access key                                     |
 | Region                                                                        | AWS region where your S3 bucket is located (e.g., `us-east-1`) |
 | Bucket Name                                                                   | Name of your S3 bucket                                         |
+
+## S3 permissions
+
+When you create an S3 connection in Prophecy, access permissions are tied to the credentials you use. This means you will only see the files and folders your S3 credentials have permission to access. Any actions you perform—such as reading or writing files—are done using those credentials.
+
+To fully leverage an S3 connection in Prophecy, you need the following S3 permissions:
+
+- Example
+- Example
+
+## Sharing connections within teams
+
+Connections in Prophecy are stored within [fabrics](docs/administration/fabrics/prophecy-fabrics/prophecy-fabrics.md), which are assigned to specific teams. Once an S3 connection is added to a fabric, all team members that have access to the fabric can use the connection in their projects. No additional authentication is required—team members automatically inherit the access and permissions of the original connection.
+
+:::caution
+Be mindful of the access level granted by the stored credentials. Anyone on the team will have the same permissions—including access to sensitive data if allowed.
+
+To manage this securely, consider creating a dedicated fabric and team for high-sensitivity connections. This way, only approved users have access to those credentials.
+:::
+
+## Sync connection
+
+Prophecy fetches data from S3 connections in the following ways:
+
+- When you browse an S3 connection in the [Environment browser](/analysts/pipelines), Prophecy fetches data on demand as you expand folders. You can manually refresh the Environment browser to see updated files.
+
+- When a pipeline runs, Source gems will read the latest available version of the data. Keep in mind that schema evolution may or may not be picked up automatically depending on the type of Source gem used.
+
+## Limitations
path: docs/administration/fabrics/prophecy-fabrics/connections/s3.md
user: login: tnmy44
body: Can't think of any limitations as such
created_at: 2025-04-13T07:34:43Z
author_association: NONE
diff_hunk: @@ -16,3 +26,32 @@ To create a connection with Sharepoint, enter the following parameters:
 | Client ID                                                                 | Your SharePoint Client ID                                                                       |
 | Client Secret ([Secret required](docs/administration/secrets/secrets.md)) | Your SharePoint Client Secret                                                                   |
 | Site URL                                                                  | URL of the SharePoint site to connect (e.g., `https://yourcompany.sharepoint.com/sites/mysite`) |
+
+## Sharepoint permissions
+
+When you create a Sharepoint connection in Prophecy, access permissions are tied to the credentials you use. This means you will only see the files and folders your Sharepoint credentials have permission to access. Any actions you perform—such as reading or writing files—are done using those credentials.
path: docs/administration/fabrics/prophecy-fabrics/connections/sharepoint.md
user: login: tnmy44
body: The permission setup is kinda tricky for sharepoint. User needs to follow this doc to create Client ID and Client Secret: https://learn.microsoft.com/en-us/entra/identity-platform/quickstart-register-app

And then they need to make sure that their Microsoft account's admin grants this permission to the Application that they just created: "Sites.Manage.All"
created_at: 2025-04-13T07:40:58Z
author_association: NONE
diff_hunk: @@ -16,3 +26,32 @@ To create a connection with Sharepoint, enter the following parameters:
 | Client ID                                                                 | Your SharePoint Client ID                                                                       |
 | Client Secret ([Secret required](docs/administration/secrets/secrets.md)) | Your SharePoint Client Secret                                                                   |
 | Site URL                                                                  | URL of the SharePoint site to connect (e.g., `https://yourcompany.sharepoint.com/sites/mysite`) |
+
+## Sharepoint permissions
+
+When you create a Sharepoint connection in Prophecy, access permissions are tied to the credentials you use. This means you will only see the files and folders your Sharepoint credentials have permission to access. Any actions you perform—such as reading or writing files—are done using those credentials.
+
+To fully leverage a Sharepoint connection in Prophecy, you need the following Sharepoint permissions:
+
+- Example
+- Example
+
+## Sharing connections within teams
+
+Connections in Prophecy are stored within [fabrics](docs/administration/fabrics/prophecy-fabrics/prophecy-fabrics.md), which are assigned to specific teams. Once a Sharepoint connection is added to a fabric, all team members that have access to the fabric can use the connection in their projects. No additional authentication is required—team members automatically inherit the access and permissions of the original connection.
+
+:::caution
+Be mindful of the access level granted by the stored credentials. Anyone on the team will have the same permissions—including access to sensitive data if allowed.
+
+To manage this securely, consider creating a dedicated fabric and team for high-sensitivity connections. This way, only approved users have access to those credentials.
+:::
+
+## Sync connection
+
+Prophecy fetches data from Sharepoint in the following ways:
+
+- When you browse a Sharepoint connection in the [Environment browser](/analysts/pipelines), Prophecy fetches data on demand as you expand folders. You can manually refresh the Environment browser to see updated files.
+
+- When a pipeline runs, Source gems will read the latest available version of the data. Keep in mind that schema evolution may or may not be picked up automatically depending on the type of Source gem used.
+
+## Limitations
path: docs/administration/fabrics/prophecy-fabrics/connections/sharepoint.md
user: login: tnmy44
body: Users must put files that they want to be accessible from prophecy in the  "Document Library" folder in Sharepoint.
created_at: 2025-04-13T07:42:12Z
author_association: NONE
diff_hunk: @@ -16,3 +26,32 @@ To create a connection with your Amazon S3 buckets, enter the following paramete
 | Secret Access Key ([Secret required](docs/administration/secrets/secrets.md)) | Your AWS secret access key                                     |
 | Region                                                                        | AWS region where your S3 bucket is located (e.g., `us-east-1`) |
 | Bucket Name                                                                   | Name of your S3 bucket                                         |
+
+## S3 permissions
+
+When you create an S3 connection in Prophecy, access permissions are tied to the credentials you use. This means you will only see the files and folders your S3 credentials have permission to access. Any actions you perform—such as reading or writing files—are done using those credentials.
+
+To fully leverage an S3 connection in Prophecy, you need the following S3 permissions:
+
+- Example
+- Example
+
+## Sharing connections within teams
path: docs/administration/fabrics/prophecy-fabrics/connections/s3.md
user: login: kathweinschenkprophecy
body: My perspective: people are googling their connections. They won't read the parent page... they will only read the page related to their connection.
created_at: 2025-04-14T13:39:23Z
author_association: CONTRIBUTOR
diff_hunk: @@ -16,3 +26,32 @@ To create a connection with your Amazon S3 buckets, enter the following paramete
 | Secret Access Key ([Secret required](docs/administration/secrets/secrets.md)) | Your AWS secret access key                                     |
 | Region                                                                        | AWS region where your S3 bucket is located (e.g., `us-east-1`) |
 | Bucket Name                                                                   | Name of your S3 bucket                                         |
+
+## S3 permissions
+
+When you create an S3 connection in Prophecy, access permissions are tied to the credentials you use. This means you will only see the files and folders your S3 credentials have permission to access. Any actions you perform—such as reading or writing files—are done using those credentials.
+
+To fully leverage an S3 connection in Prophecy, you need the following S3 permissions:
+
+- Example
+- Example
+
+## Sharing connections within teams
+
+Connections in Prophecy are stored within [fabrics](docs/administration/fabrics/prophecy-fabrics/prophecy-fabrics.md), which are assigned to specific teams. Once an S3 connection is added to a fabric, all team members that have access to the fabric can use the connection in their projects. No additional authentication is required—team members automatically inherit the access and permissions of the original connection.
+
+:::caution
+Be mindful of the access level granted by the stored credentials. Anyone on the team will have the same permissions—including access to sensitive data if allowed.
+
+To manage this securely, consider creating a dedicated fabric and team for high-sensitivity connections. This way, only approved users have access to those credentials.
+:::
+
+## Sync connection
+
+Prophecy fetches data from S3 connections in the following ways:
+
+- When you browse an S3 connection in the [Environment browser](/analysts/pipelines), Prophecy fetches data on demand as you expand folders. You can manually refresh the Environment browser to see updated files.
+
+- When a pipeline runs, Source gems will read the latest available version of the data. Keep in mind that schema evolution may or may not be picked up automatically depending on the type of Source gem used.
path: docs/administration/fabrics/prophecy-fabrics/connections/s3.md
user: login: kathweinschenkprophecy
body: Yes I was replacing it per connection :) I will change this
created_at: 2025-04-14T13:39:50Z
author_association: CONTRIBUTOR
diff_hunk: @@ -16,3 +26,32 @@ To create a connection with your Amazon S3 buckets, enter the following paramete
 | Secret Access Key ([Secret required](docs/administration/secrets/secrets.md)) | Your AWS secret access key                                     |
 | Region                                                                        | AWS region where your S3 bucket is located (e.g., `us-east-1`) |
 | Bucket Name                                                                   | Name of your S3 bucket                                         |
+
+## S3 permissions
+
+When you create an S3 connection in Prophecy, access permissions are tied to the credentials you use. This means you will only see the files and folders your S3 credentials have permission to access. Any actions you perform—such as reading or writing files—are done using those credentials.
+
+To fully leverage an S3 connection in Prophecy, you need the following S3 permissions:
+
+- Example
+- Example
+
+## Sharing connections within teams
+
+Connections in Prophecy are stored within [fabrics](docs/administration/fabrics/prophecy-fabrics/prophecy-fabrics.md), which are assigned to specific teams. Once an S3 connection is added to a fabric, all team members that have access to the fabric can use the connection in their projects. No additional authentication is required—team members automatically inherit the access and permissions of the original connection.
+
+:::caution
+Be mindful of the access level granted by the stored credentials. Anyone on the team will have the same permissions—including access to sensitive data if allowed.
+
+To manage this securely, consider creating a dedicated fabric and team for high-sensitivity connections. This way, only approved users have access to those credentials.
+:::
+
+## Sync connection
path: docs/administration/fabrics/prophecy-fabrics/connections/s3.md
user: login: kathweinschenkprophecy
body: See previous
created_at: 2025-04-14T13:40:33Z
author_association: CONTRIBUTOR
diff_hunk: @@ -8,6 +8,16 @@ tags:
   - databricks
 ---
 
+A Databricks connection lets you access your cloud data warehouse. It’s optimized for analytics and built to support modern data warehousing workloads with high performance and scalability.
+
+| Feature                                                       | Supported |
path: docs/administration/fabrics/prophecy-fabrics/connections/databricks.md
user: login: kailie-prophecy
body: Nit/Suggestion: I understand that this table is to showcase the features Prophecy offers and to state whether the current connection supports it, but I think we should have an intro sentence stating that so users aren't wondering what this table is for, and/or putting it in its own section since it doesn't seem related to the intro.

So something like:
"The following table lists features you can perform in Prophecy and whether the Databricks connection supports them:"
created_at: 2025-04-14T20:21:13Z
author_association: CONTRIBUTOR
diff_hunk: @@ -24,4 +34,50 @@ You can configure your Databricks connection with one of three authentication me
 
 - **Databricks [OAuth](docs/administration/authentication/databricks-oauth.md).** Prophecy prompts you to sign in with Databricks.
 - **Personal Access Token (PAT).** Use a [secret](docs/administration/secrets/secrets.md) to enter your PAT.
-- **Client Credentials.** Enter your Client ID and Client Secret (secret required) for authentication.
+
+## Databricks permissions
+
+When you create an Databricks connection in Prophecy, access permissions are tied to the credentials you use. This means you will only see data your Databricks credentials have permission to access. Any data operations—such as reading from or writing to tables—are executed using your credentials.
+
+To fully leverage a Databricks connection in Prophecy, you need the following Databricks permissions:
+
+- Create Schema
+- Create or Replace Table
+- Drop Table
+- Insert Into
+- Create Volume `PROPHECY_ORCHESTRATOR_VOLUME`
+- Access to `/Volumes/<catalog>/<schema>/PROPHECY_ORCHESTRATOR_VOLUME`
+- Remove File permission inside the volume
+- Copy Into (from the volume)
+
+## Sharing connections within teams
+
+Connections are stored inside fabrics, which are assigned to certain teams. The way Databricks connections are shared depends on the authentication method used to configure the connection.
path: docs/administration/fabrics/prophecy-fabrics/connections/databricks.md
user: login: kailie-prophecy
body: ```suggestion
Connections are stored inside fabrics, which are assigned to certain teams. You can share Databricks connections depending on the authentication method to configure the connection.
```
created_at: 2025-04-14T20:25:47Z
author_association: CONTRIBUTOR
diff_hunk: @@ -7,6 +7,16 @@ tags:
   - mongodb
 ---
 
+MongoDB is a popular NoSQL database designed to store and retrieve unstructured or semi-structured data using flexible, JSON-like documents. It’s often used in modern applications where data structures can evolve over time.
path: docs/administration/fabrics/prophecy-fabrics/connections/mongodb.md
user: login: kailie-prophecy
body: ```suggestion
MongoDB is a NoSQL database designed to store and retrieve unstructured or semi-structured data using BSON documents. It’s often used in modern applications where data structures can evolve over time.
```
Nit: Remove adjective. Also, they store data using BSON documents lol. It's the binary version of the JSON and is more space effect that way.
created_at: 2025-04-14T20:32:55Z
author_association: CONTRIBUTOR
diff_hunk: @@ -7,6 +7,16 @@ tags:
   - msssql
 ---
 
+Microsoft SQL Server (MSSQL) is a reliable, enterprise-grade relational database used for storing and querying structured data, with strong support for transactions, security, and complex SQL. It’s a popular choice for organizations already invested in the Microsoft ecosystem or needing a stable on-prem or cloud-compatible data platform.
path: docs/administration/fabrics/prophecy-fabrics/connections/mssql.md
user: login: kailie-prophecy
body: Nit/Suggestion: I'm not sure if the second sentence here adds value -- it's almost like we're advertising for them here.
created_at: 2025-04-14T20:40:18Z
author_association: CONTRIBUTOR
diff_hunk: @@ -18,3 +28,30 @@ To create a connection with MongoDB, enter the following parameters:
 | Password ([Secret required](docs/administration/secrets/secrets.md)) | Password for your MongoDB instance             |
 | Database                                                             | Default database for reading and writing data  |
 | Collection                                                           | Collection to use for the connection           |
+
+## MongoDB permissions
+
+When you create an MongoDB connection in Prophecy, access permissions are tied to the credentials you use. This means you will only see the data your MongoDB credentials have permission to access. Any data operations—such as reading from or writing to tables—are executed using your credentials.
+
+To fully leverage a MongoDB connection in Prophecy, you need the following MongoDB permissions:
+
+- `Read` from the collection defined in the connection
+- `Write` to the collection defined in the connection
path: docs/administration/fabrics/prophecy-fabrics/connections/mongodb.md
user: login: kailie-prophecy
body: Nit/Suggestion: I saw you did a single sentence in the MSSQL page for pretty much the same requirement, so can this also be a single sentence?
created_at: 2025-04-14T20:41:33Z
author_association: CONTRIBUTOR
diff_hunk: @@ -16,3 +26,30 @@ To create a connection with your Amazon S3 buckets, enter the following paramete
 | Secret Access Key ([Secret required](docs/administration/secrets/secrets.md)) | Your AWS secret access key                                     |
 | Region                                                                        | AWS region where your S3 bucket is located (e.g., `us-east-1`) |
 | Bucket Name                                                                   | Name of your S3 bucket                                         |
+
+## S3 permissions
+
+When you create an S3 connection in Prophecy, access permissions are tied to the AWS credentials you use. This means you will only see the files and folders your these credentials have permission to access. Any data operations—such as reading from or writing to tables—are executed using your credentials.
path: docs/administration/fabrics/prophecy-fabrics/connections/s3.md
user: login: kailie-prophecy
body: ```suggestion
When you create an S3 connection in Prophecy, access permissions are tied to the AWS credentials you use. This means you only see the files and folders these credentials have permission to access. Your credentials execute all data operations, such as reading from or writing to tables.
```

Nit/Suggestion: I think this is clearer -- applies to all permission sections since they follow a similar format.
created_at: 2025-04-14T20:47:11Z
author_association: CONTRIBUTOR
diff_hunk: @@ -16,3 +26,30 @@ To create a connection with your Amazon S3 buckets, enter the following paramete
 | Secret Access Key ([Secret required](docs/administration/secrets/secrets.md)) | Your AWS secret access key                                     |
 | Region                                                                        | AWS region where your S3 bucket is located (e.g., `us-east-1`) |
 | Bucket Name                                                                   | Name of your S3 bucket                                         |
+
+## S3 permissions
+
+When you create an S3 connection in Prophecy, access permissions are tied to the AWS credentials you use. This means you will only see the files and folders your these credentials have permission to access. Any data operations—such as reading from or writing to tables—are executed using your credentials.
+
+To fully leverage an S3 connection in Prophecy, you need the following permissions:
+
+- For a bucket: `List`, `Write`
+- For an object/file: `Read`, `Write`
+
+## Sharing connections within teams
+
+Connections in Prophecy are stored within [fabrics](docs/administration/fabrics/prophecy-fabrics/prophecy-fabrics.md), which are assigned to specific teams. Once an S3 connection is added to a fabric, all team members that have access to the fabric can use the connection in their projects. No additional authentication is required—team members automatically inherit the access and permissions of the original connection.
path: docs/administration/fabrics/prophecy-fabrics/connections/s3.md
user: login: kailie-prophecy
body: ```suggestion
Prophecy stores connections within [fabrics](docs/administration/fabrics/prophecy-fabrics/prophecy-fabrics.md), which are assigned to specific teams. Once an S3 connection is added to a fabric, all team members that have access to the fabric can use the connection in their projects. No additional authentication is required, and team members automatically inherit the access and permissions of the original connection.
```
Nit/Suggestion: I think this is a bit clearer. Applies to all instances.
created_at: 2025-04-14T20:49:29Z
author_association: CONTRIBUTOR
diff_hunk: @@ -23,3 +35,33 @@ You can configure your SFTP connection with one of the following authentication
 
 - **Password.** Use a [secret](docs/administration/secrets/secrets.md) to enter your SFTP password.
 - **Private key**. Upload a file that contains your SFTP private key.
+
+## SFTP permissions
+
+When you use an SFTP connection in Prophecy, permissions depend on the underlying SSH server and filesystem permissions on the server.
+
+## Sharing connections within teams
+
+Connections in Prophecy are stored within [fabrics](docs/administration/fabrics/prophecy-fabrics/prophecy-fabrics.md), which are assigned to specific teams. Once an SFTP connection is added to a fabric, all team members that have access to the fabric can use the connection in their projects. No additional authentication is required—team members automatically inherit the access and permissions of the original connection.
+
+:::caution
+Be mindful of the access level granted by the stored credentials. Anyone on the team will have the same permissions—including access to sensitive data if allowed.
+
+To manage this securely, consider creating a dedicated fabric and team for high-sensitivity connections. This way, only approved users have access to those credentials.
+:::
+
+## Fetching data
+
+Prophecy fetches data from SFTP connections in the following ways:
+
+- When you browse an SFTP connection in the [Environment browser](/analysts/pipelines), Prophecy fetches data on demand as you expand folders. You can manually refresh the Environment browser to see updated files.
+
+- When a pipeline runs, Source gems will read the latest available version of the data. If the schema changes in the external connection, you will need to re-infer the schema in Prophecy.
+
+## Limitations
path: docs/administration/fabrics/prophecy-fabrics/connections/sftp.md
user: login: kailie-prophecy
body: Suggestion: I think Limitations should be at the very top because it's something users should know immediately, and not by the time they hit the end of the page.

Applies to all pages with a Limitations section.
created_at: 2025-04-14T20:55:29Z
author_association: CONTRIBUTOR
diff_hunk: @@ -7,9 +7,57 @@ tags:
   - smartsheet
 ---
 
+Smartsheet is used for managing tasks, projects, and workflows using a spreadsheet-like interface that can contain rows, columns, and cell data. Prophecy uses the [Smartsheet API](https://developers.smartsheet.com/api/smartsheet/introduction) to establish the connection.
path: docs/administration/fabrics/prophecy-fabrics/connections/smartsheet.md
user: login: kailie-prophecy
body: ```suggestion
Smartsheet manages tasks, projects, and workflows using a spreadsheet-like interface that can contain rows, columns, and cell data. Prophecy uses the [Smartsheet API](https://developers.smartsheet.com/api/smartsheet/introduction) to establish the connection.
```
created_at: 2025-04-14T21:03:34Z
author_association: CONTRIBUTOR
diff_hunk: @@ -0,0 +1,40 @@
+---
+title: SMTP
+id: smtp
+description: Learn how to configure an SMTP connection
+tags:
+  - connections
+  - smtp
+---
+
+SMTP (Simple Mail Transfer Protocol) connections are used to send emails over the internet by allowing communication between email clients and servers. When you create an SMTP connection in Prophecy, the user credentials you provide are used to establish the connection. This user will always be the sender of an email when you use the Email gem with this connection.
+
+| Feature                                                       | Supported |
+| ------------------------------------------------------------- | --------- |
+| Read data with a [Source gem](/analysts/source-target)        | No        |
+| Write data with a Report gem                                  | Yes       |
+| Browse data in the [Environment browser](/analysts/pipelines) | No        |
+
+## Parameters
+
+To create an SMTP connection, enter the following parameters:
+
+| Parameter                                                            | Description                                               |
+| -------------------------------------------------------------------- | --------------------------------------------------------- |
+| Connection Name                                                      | Unique name for the connection (e.g., `MySMTPConnection`) |
+| URL                                                                  | SMTP server URL (e.g., `smtp.gmail.com`)                  |
+| Port                                                                 | SMTP port. Port options may vary between SMTP services.   |
+| Username                                                             | Your SMTP username                                        |
+| Password ([Secret required](docs/administration/secrets/secrets.md)) | Your SMTP password                                        |
+
+<!-- You can leverage your SMTP connection to send emails with the [Email](docs/analysts/development/gems/report/email.md) gem. -->
+
+## Sharing connections within teams
+
+Connections in Prophecy are stored within [fabrics](docs/administration/fabrics/prophecy-fabrics/prophecy-fabrics.md), which are assigned to specific teams. Once an SMTP connection is added to a fabric, anyone in the team can use that connection to send emails from a pipeline.
+
+## Limitations
+
+Keep in mind the following limitations when using an SMTP connection.
path: docs/administration/fabrics/prophecy-fabrics/connections/smtp.md
user: login: kailie-prophecy
body: ```suggestion
## Limitation
```
Suggestion: Since there's only 1, the section should be singular, and the intro text is not needed.
created_at: 2025-04-14T21:10:13Z
author_association: CONTRIBUTOR
diff_hunk: @@ -24,5 +34,53 @@ To create a connection with Snowflake, enter the following parameters:
 
 You can configure your Snowflake connection with one of the following authentication methods:
path: docs/administration/fabrics/prophecy-fabrics/connections/snowflake.md
user: login: kailie-prophecy
body: ```suggestion
You can configure your Snowflake connection with the password authentication method where you enter your Snowflake username and use a [secret](docs/administration/secrets/secrets.md) to enter your password.
```
created_at: 2025-04-14T21:11:40Z
author_association: CONTRIBUTOR
diff_hunk: @@ -24,5 +34,53 @@ To create a connection with Snowflake, enter the following parameters:
 
 You can configure your Snowflake connection with one of the following authentication methods:
 
-- **Snowflake [OAuth](docs/administration/authentication/databricks-oauth.md).** Prophecy prompts you to sign in with Snowflake.
+<!-- - **Snowflake [OAuth](docs/administration/authentication/databricks-oauth.md).** Prophecy prompts you to sign in with Snowflake. -->
+
 - **Password**. Enter your Snowflake username and use a [secret](docs/administration/secrets/secrets.md) to enter your password.
path: docs/administration/fabrics/prophecy-fabrics/connections/snowflake.md
user: login: kailie-prophecy
body: ```suggestion
```
Suggestion, remove this bullet and incorporate it into the intro text since it's only one way
created_at: 2025-04-14T21:12:13Z
author_association: CONTRIBUTOR
diff_hunk: @@ -7,6 +7,18 @@ tags:
   - tableau
 ---
 
+A Tableau connection allows you to update data sources in Tableau projects. Use this integration to upload data from your pipeline as `Hyper` files (Tableau’s high-performance, in-memory database format).
path: docs/administration/fabrics/prophecy-fabrics/connections/tableau.md
user: login: kailie-prophecy
body: ```suggestion
A Tableau connection allows you to update data sources in Tableau projects and to upload data from your pipeline as `Hyper` files (Tableau’s high-performance, in-memory database format).
```
created_at: 2025-04-14T21:14:42Z
author_association: CONTRIBUTOR
diff_hunk: @@ -8,6 +8,16 @@ tags:
   - databricks
 ---
 
+A Databricks connection lets you access your cloud data warehouse. It’s optimized for analytics and built to support modern data warehousing workloads with high performance and scalability.
+
+| Feature                                                       | Supported |
path: docs/administration/fabrics/prophecy-fabrics/connections/databricks.md
user: login: kathweinschenkprophecy
body: agree
created_at: 2025-04-15T17:00:04Z
author_association: CONTRIBUTOR
diff_hunk: @@ -24,4 +34,50 @@ You can configure your Databricks connection with one of three authentication me
 
 - **Databricks [OAuth](docs/administration/authentication/databricks-oauth.md).** Prophecy prompts you to sign in with Databricks.
 - **Personal Access Token (PAT).** Use a [secret](docs/administration/secrets/secrets.md) to enter your PAT.
-- **Client Credentials.** Enter your Client ID and Client Secret (secret required) for authentication.
+
+## Databricks permissions
+
+When you create an Databricks connection in Prophecy, access permissions are tied to the credentials you use. This means you will only see data your Databricks credentials have permission to access. Any data operations—such as reading from or writing to tables—are executed using your credentials.
+
+To fully leverage a Databricks connection in Prophecy, you need the following Databricks permissions:
+
+- Create Schema
+- Create or Replace Table
+- Drop Table
+- Insert Into
+- Create Volume `PROPHECY_ORCHESTRATOR_VOLUME`
+- Access to `/Volumes/<catalog>/<schema>/PROPHECY_ORCHESTRATOR_VOLUME`
+- Remove File permission inside the volume
+- Copy Into (from the volume)
+
+## Sharing connections within teams
+
+Connections are stored inside fabrics, which are assigned to certain teams. The way Databricks connections are shared depends on the authentication method used to configure the connection.
path: docs/administration/fabrics/prophecy-fabrics/connections/databricks.md
user: login: kathweinschenkprophecy
body: The way *you* share the connection doesn't depend on the auth method. The way Prophecy manages connections inside fabrics does...so I'll clarify that.
created_at: 2025-04-15T17:11:33Z
author_association: CONTRIBUTOR
diff_hunk: @@ -7,6 +7,16 @@ tags:
   - msssql
 ---
 
+Microsoft SQL Server (MSSQL) is a reliable, enterprise-grade relational database used for storing and querying structured data, with strong support for transactions, security, and complex SQL. It’s a popular choice for organizations already invested in the Microsoft ecosystem or needing a stable on-prem or cloud-compatible data platform.
path: docs/administration/fabrics/prophecy-fabrics/connections/mssql.md
user: login: kathweinschenkprophecy
body: will fix
created_at: 2025-04-15T17:17:31Z
author_association: CONTRIBUTOR
diff_hunk: @@ -18,3 +28,30 @@ To create a connection with MongoDB, enter the following parameters:
 | Password ([Secret required](docs/administration/secrets/secrets.md)) | Password for your MongoDB instance             |
 | Database                                                             | Default database for reading and writing data  |
 | Collection                                                           | Collection to use for the connection           |
+
+## MongoDB permissions
+
+When you create an MongoDB connection in Prophecy, access permissions are tied to the credentials you use. This means you will only see the data your MongoDB credentials have permission to access. Any data operations—such as reading from or writing to tables—are executed using your credentials.
+
+To fully leverage a MongoDB connection in Prophecy, you need the following MongoDB permissions:
+
+- `Read` from the collection defined in the connection
+- `Write` to the collection defined in the connection
path: docs/administration/fabrics/prophecy-fabrics/connections/mongodb.md
user: login: kathweinschenkprophecy
body: The MSSQL is pending more detailed info. I might convert the MSSQL to bullet points later...
created_at: 2025-04-15T17:18:08Z
author_association: CONTRIBUTOR
diff_hunk: @@ -23,3 +35,33 @@ You can configure your SFTP connection with one of the following authentication
 
 - **Password.** Use a [secret](docs/administration/secrets/secrets.md) to enter your SFTP password.
 - **Private key**. Upload a file that contains your SFTP private key.
+
+## SFTP permissions
+
+When you use an SFTP connection in Prophecy, permissions depend on the underlying SSH server and filesystem permissions on the server.
+
+## Sharing connections within teams
+
+Connections in Prophecy are stored within [fabrics](docs/administration/fabrics/prophecy-fabrics/prophecy-fabrics.md), which are assigned to specific teams. Once an SFTP connection is added to a fabric, all team members that have access to the fabric can use the connection in their projects. No additional authentication is required—team members automatically inherit the access and permissions of the original connection.
+
+:::caution
+Be mindful of the access level granted by the stored credentials. Anyone on the team will have the same permissions—including access to sensitive data if allowed.
+
+To manage this securely, consider creating a dedicated fabric and team for high-sensitivity connections. This way, only approved users have access to those credentials.
+:::
+
+## Fetching data
+
+Prophecy fetches data from SFTP connections in the following ways:
+
+- When you browse an SFTP connection in the [Environment browser](/analysts/pipelines), Prophecy fetches data on demand as you expand folders. You can manually refresh the Environment browser to see updated files.
+
+- When a pipeline runs, Source gems will read the latest available version of the data. If the schema changes in the external connection, you will need to re-infer the schema in Prophecy.
+
+## Limitations
path: docs/administration/fabrics/prophecy-fabrics/connections/sftp.md
user: login: kathweinschenkprophecy
body: I don't think very top, but maybe after features? Like here https://docs.confluent.io/cloud/current/connectors/cc-mysql-source.html#limitations
created_at: 2025-04-15T17:27:36Z
author_association: CONTRIBUTOR
diff_hunk: @@ -24,5 +34,53 @@ To create a connection with Snowflake, enter the following parameters:
 
 You can configure your Snowflake connection with one of the following authentication methods:
path: docs/administration/fabrics/prophecy-fabrics/connections/snowflake.md
user: login: kathweinschenkprophecy
body: actually i'll comment out the whole section until oauth comes out
created_at: 2025-04-15T17:29:01Z
author_association: CONTRIBUTOR
diff_hunk: @@ -7,6 +7,18 @@ tags:
   - tableau
 ---
 
+A Tableau connection allows you to update data sources in Tableau projects. Use this integration to upload data from your pipeline as `Hyper` files (Tableau’s high-performance, in-memory database format).
path: docs/administration/fabrics/prophecy-fabrics/connections/tableau.md
user: login: kathweinschenkprophecy
body: update data sources = upload data from pipeline as hyper files

so it's less `and` and more `by`... I will fix
created_at: 2025-04-15T17:31:16Z
author_association: CONTRIBUTOR
diff_hunk: @@ -23,3 +35,33 @@ You can configure your SFTP connection with one of the following authentication
 
 - **Password.** Use a [secret](docs/administration/secrets/secrets.md) to enter your SFTP password.
 - **Private key**. Upload a file that contains your SFTP private key.
+
+## SFTP permissions
+
+When you use an SFTP connection in Prophecy, permissions depend on the underlying SSH server and filesystem permissions on the server.
+
+## Sharing connections within teams
+
+Connections in Prophecy are stored within [fabrics](docs/administration/fabrics/prophecy-fabrics/prophecy-fabrics.md), which are assigned to specific teams. Once an SFTP connection is added to a fabric, all team members that have access to the fabric can use the connection in their projects. No additional authentication is required—team members automatically inherit the access and permissions of the original connection.
+
+:::caution
+Be mindful of the access level granted by the stored credentials. Anyone on the team will have the same permissions—including access to sensitive data if allowed.
+
+To manage this securely, consider creating a dedicated fabric and team for high-sensitivity connections. This way, only approved users have access to those credentials.
+:::
+
+## Fetching data
+
+Prophecy fetches data from SFTP connections in the following ways:
+
+- When you browse an SFTP connection in the [Environment browser](/analysts/pipelines), Prophecy fetches data on demand as you expand folders. You can manually refresh the Environment browser to see updated files.
+
+- When a pipeline runs, Source gems will read the latest available version of the data. If the schema changes in the external connection, you will need to re-infer the schema in Prophecy.
+
+## Limitations
path: docs/administration/fabrics/prophecy-fabrics/connections/sftp.md
user: login: kailie-prophecy
body: Yea! I think after the feature support section would be great!
created_at: 2025-04-15T18:17:32Z
author_association: CONTRIBUTOR
diff_hunk: @@ -35,6 +39,4 @@ Connections in Prophecy are stored within [fabrics](docs/administration/fabrics/
 
 ## Limitations
path: docs/administration/fabrics/prophecy-fabrics/connections/smtp.md
user: login: kailie-prophecy
body: Nit: This and the Tableau page only have 1, so I'd make this singular.
created_at: 2025-04-15T18:19:06Z
author_association: CONTRIBUTOR
diff_hunk: @@ -35,6 +39,4 @@ Connections in Prophecy are stored within [fabrics](docs/administration/fabrics/
 
 ## Limitations
path: docs/administration/fabrics/prophecy-fabrics/connections/smtp.md
user: login: kathweinschenkprophecy
body: I'm not sure I agree, on the basis that "Limitation" sounds weird to me + it would be inconsistent? acccck
created_at: 2025-04-15T18:38:17Z
author_association: CONTRIBUTOR
diff_hunk: @@ -35,6 +39,4 @@ Connections in Prophecy are stored within [fabrics](docs/administration/fabrics/
 
 ## Limitations
path: docs/administration/fabrics/prophecy-fabrics/connections/smtp.md
user: login: kailie-prophecy
body: No worries then -- it was only a nit lol. Not a blocker to merge in :) 
created_at: 2025-04-15T18:39:13Z
author_association: CONTRIBUTOR

PR comments:
user: login: github-actions[bot]
created_at: 2025-04-07T19:06:42Z
body: 🚀 Staging preview available: [https://SimpleDataLabsInc.github.io/prophecy-docs-staging/preview/pr-607/](https://SimpleDataLabsInc.github.io/prophecy-docs-staging/preview/pr-607/)
author_association: NONE
user: login: github-actions[bot]
created_at: 2025-04-11T16:19:45Z
body: 🚀 Staging preview available: [https://SimpleDataLabsInc.github.io/prophecy-docs-staging/preview/pr-607/](https://SimpleDataLabsInc.github.io/prophecy-docs-staging/preview/pr-607/)
author_association: NONE
user: login: github-actions[bot]
created_at: 2025-04-14T16:20:23Z
body: 🚀 Staging preview available: [https://SimpleDataLabsInc.github.io/prophecy-docs-staging/preview/pr-607/](https://SimpleDataLabsInc.github.io/prophecy-docs-staging/preview/pr-607/)
author_association: NONE
user: login: github-actions[bot]
created_at: 2025-04-14T19:58:36Z
body: 🚀 Staging preview available: [https://SimpleDataLabsInc.github.io/prophecy-docs-staging/preview/pr-607/](https://SimpleDataLabsInc.github.io/prophecy-docs-staging/preview/pr-607/)
author_association: NONE
user: login: github-actions[bot]
created_at: 2025-04-15T17:53:12Z
body: 🚀 Staging preview available: [https://SimpleDataLabsInc.github.io/prophecy-docs-staging/preview/pr-607/](https://SimpleDataLabsInc.github.io/prophecy-docs-staging/preview/pr-607/)
author_association: NONE
user: login: github-actions[bot]
created_at: 2025-04-15T18:39:43Z
body: 🚀 Staging preview available: [https://SimpleDataLabsInc.github.io/prophecy-docs-staging/preview/pr-607/](https://SimpleDataLabsInc.github.io/prophecy-docs-staging/preview/pr-607/)
author_association: NONE
user: login: github-actions[bot]
created_at: 2025-04-15T18:42:11Z
body: :mag_right::speech_balloon: [Inkeep](https://inkeep.com) AI search and chat service is syncing content for source 'Prophecy Docs'
author_association: NONE