Merge branch 'current' into permissions

website/docs/docs/build/metrics-overview.md

@@ -9,7 +9,7 @@ pagination_next: "docs/build/cumulative"
 
 After building [semantic models](/docs/build/semantic-models), it's time to start adding metrics. This page explains the different supported metric types you can add to your dbt project
 
-Metrics can be defined in the same YAML files as your semantic models, or defined in their dedicated separate YAML files located in any subdirectories within the same dbt project repository.
+Metrics must be defined in a YAML file — either within the same file as your semantic models or in a separate YAML file in a subdirectory of your dbt project. They shouldn't be defined in a `config` block on a model.
 
 The keys for metrics definitions are:
 

website/docs/docs/cloud-integrations/configure-auto-exposures.md

@@ -80,3 +80,8 @@ dbt Cloud imports everything in the collection(s) and you can continue to view t
 :::info Coming soon
 Soon, you’ll also be able to use auto-exposures to trigger the refresh of the data used in your Tableau dashboards from within dbt Cloud. Stay tuned for more on this soon!
 :::
+
+## Considerations
+import ConsiderationsTableau from '/snippets/_auto-exposures-considerations-tb.md';
+
+<ConsiderationsTableau/>

website/docs/docs/cloud/connect-data-platform/connect-snowflake.md

@@ -7,7 +7,7 @@ sidebar_label: "Connect Snowflake"
 
 :::note
 
-dbt Cloud connections and credentials inherit the permissions of the accounts configured. You can customize roles and associated permissions in Snowflake to fit your company's requirements and fine-tune access to database objects in your account. See [Snowflake permissions](/reference/database-permissions/snowflake-permissions) for more information about customizing roles in Snowflake.
+dbt Cloud connections and credentials inherit the permissions of the accounts configured. You can customize roles and associated permissions in Snowflake to fit your company's requirements and fine-tune access to database objects in your account.
 
 Refer to [Snowflake permissions](/reference/database-permissions/snowflake-permissions) for more information about customizing roles in Snowflake.
 

website/docs/docs/collaborate/auto-exposures.md

@@ -25,3 +25,8 @@ For more information on how to set up auto-exposures, prerequisites, and more &m
 import ViewExposures from '/snippets/_auto-exposures-view.md';
 
 <ViewExposures/>
+
+## Considerations
+import ConsiderationsTableau from '/snippets/_auto-exposures-considerations-tb.md';
+
+<ConsiderationsTableau/>

website/docs/guides/set-up-ci.md

@@ -117,7 +117,14 @@ If you create a seed to exclude groups of models from a specific test, remember
 
 By [linting](/docs/cloud/dbt-cloud-ide/lint-format#lint) your project during CI, you can ensure that code styling standards are consistently enforced, without spending human time nitpicking comma placement.
 
-The steps below create an action/pipeline which uses [SQLFluff](https://docs.sqlfluff.com/en/stable/) to scan your code and look for linting errors. If you don't already have SQLFluff rules defined, check out [our recommended config file](/best-practices/how-we-style/2-how-we-style-our-sql).
+Seamlessly enable [SQL linting for your CI job](/docs/deploy/continuous-integration#sql-linting) in dbt Cloud to invoke [SQLFluff](https://docs.sqlfluff.com/en/stable/), a modular and configurable SQL linter that warns you of complex functions, syntax, formatting, and compilation errors.
+
+SQL linting in CI lints all the changed SQL files in your project (compared to the last deferred production state). Available on dbt Cloud [Team or Enterprise accounts](https://www.getdbt.com/pricing) using [release tracks]((/docs/dbt-versions/cloud-release-tracks). 
+
+
+### Manually set up SQL linting in CI
+
+You can run SQLFluff as part of your pipeline even if you don't have access to [SQL linting in CI](/docs/deploy/continuous-integration#sql-linting). The following steps walk you through setting up a CI job using SQLFluff to scan your code for linting errors. If you're new to SQLFluff rules in dbt Cloud, check out [our recommended config file](/best-practices/how-we-style/2-how-we-style-our-sql).
 
 ### 1. Create a YAML file to define your pipeline
 

website/snippets/_auto-exposures-considerations-tb.md

@@ -0,0 +1,6 @@
+Auto-exposures with Tableau have the following considerations:
+
+- You can only connect to a single Tableau site on the same server.
+- If you're using Tableau Server, you need to [allowlist dbt Cloud's IP addresses](/docs/cloud/about-cloud/access-regions-ip-addresses) for your dbt Cloud region.
+- Tableau dashboards built using custom SQL queries aren't supported.
+- Auto-exposures sync automatically _once per day_ or when a user updates the selected collections.

website/snippets/_enterprise-permissions-table.md

@@ -104,8 +104,8 @@ Key:
 {`
 |Project-level permission  | Admin | Analyst | Database admin | Developer | Git Admin | Job admin | Job runner  | Job viewer  | Metadata (Discovery API only) | Semantic Layer | Stakeholder | Team admin | Webhook |
 |--------------------------|:-----:|:-------:|:--------------:|:---------:|:---------:|:---------:|:-----------:|:-----------:|:---------------------------------------:|:--------------:|:-----------:|:----------:|:-------:|  
-| Environment credentials  |   W  |    W     |       W        |     W     |     R     |     W     |    -        |      -      |                  -                      |        -       |     R       |     R      |   -     |
-| Custom env. variables    |   W  |    W     |       W        |     W     |     W     |     W     |     -       |      R      |                  -                      |        -       |     R       |     W      |   -     |
+| Environment credentials  |   W   |    W    |       W        |     W     |     R     |     W     |    -        |      -      |                  -                      |        -       |     R       |     R      |   -     |
+| Custom env. variables    |   W   |    W#  |       W         |     W#   |     W     |     W     |     -       |      R      |                  -                      |        -       |     R       |     W      |   -     |
 | Data platform configs    |   W   |    W    |       W        |     W     |     R     |     W     |     -       |      -      |                  -                      |       -        |     R       |     R      |    -    |
 | Develop (IDE or CLI)     |   W   |    W    |       -        |     W     |     -     |     -     |     -       |      -      |                  -                      |       -        |     -       |      -     |    -    |
 | Environments             |   W   |    R    |       R        |     R     |     R     |     W     |      -      |      R      |                  -                      |       -        |     R       |     R      |    -    |
@@ -122,3 +122,5 @@ Key:
 </SortableTable>
 
 \* These permissions are `R`ead-only by default, but may be changed to `W`rite with [environment permissions](/docs/cloud/manage-access/environment-permissions#environments-and-roles).
+
+\# Custom env. variables for the `Developer` and `Analyst` roles are set in the **Credentials** section of **Account settings**.