Merge branch 'current' into nfiann-gear2acct

website/docs/docs/build/custom-target-names.md

@@ -24,6 +24,6 @@ To set a custom target name for a job in dbt Cloud, configure the **Target Name*
 <Lightbox src="/img/docs/dbt-cloud/using-dbt-cloud/jobs-settings-target-name.png" title="Overriding the target name to 'prod'"/>
 
 ## dbt Cloud IDE
-When developing in dbt Cloud, you can set a custom target name in your development credentials. Go to your account (from the gear menu in the top right hand corner), select the project under **Credentials**, and update the target name.
+When developing in dbt Cloud, you can set a custom target name in your development credentials. Click your account name above the profile icon in the left panel, select **Account settings**, then go to **Credentials**. Choose the project to update the target name.
 
 <Lightbox src="/img/docs/dbt-cloud/using-dbt-cloud/development-credentials.png" title="Overriding the target name to 'dev'"/>

website/docs/docs/cloud-integrations/set-up-snowflake-native-app.md

@@ -45,7 +45,8 @@ The following are the prerequisites for dbt Cloud and Snowflake.
 Configure dbt Cloud and Snowflake Cortex to power the **Ask dbt** chatbot.
 
 1. In dbt Cloud, browse to your Semantic Layer configurations. 
-    1. From the gear menu, select **Account settings**. In the left sidebar, select **Projects** and choose your dbt project from the project list. 
+    1. Navigate to the left hand side panel and click your account name. From there, select **Account settings**. 
+    1. In the left sidebar, select **Projects** and choose your dbt project from the project list. 
     1. In the **Project details** panel, click the **Edit Semantic Layer Configuration** link (which is below the **GraphQL URL** option). 
 1. In the **Semantic Layer Configuration Details** panel, identify the Snowflake credentials (which you'll use to access Snowflake Cortex) and the environment against which the Semantic Layer is run. Save the username, role, and the environment in a temporary location to use later on. 
 

website/docs/docs/cloud/manage-access/environment-permissions-setup.md

@@ -15,7 +15,7 @@ Environment-level permissions are not the same as account-level [role-based acce
 
 In your dbt Cloud account:
 
-1. Open the **gear menu** and select **Account settings**. From the left-side menu, select **Groups & Licenses**. While you can edit existing groups, we recommend not altering the default `Everyone`, `Member`, and `Owner` groups.
+1. Click your account name, above your profile icon on the left side panel, then select **Account settings**. From there, select **Groups & Licenses**. While you can edit existing groups, we recommend not altering the default `Everyone`, `Member`, and `Owner` groups.
 
 <Lightbox src="/img/docs/dbt-cloud/groups-and-licenses.png" width="80%" title="Groups & Licenses page in dbt Cloud with the default groups highlighted."/>
 

website/docs/docs/cloud/manage-access/set-up-bigquery-oauth.md

@@ -25,13 +25,14 @@ To use BigQuery in the dbt Cloud IDE, all developers must:
 
 ### Locate the redirect URI value
 To get started, locate the connection's redirect URI for configuring BigQuery OAuth. To do so:
- - Select the gear menu in the upper left corner and choose **Account settings**
+ - Navigate to your account name, above your profile icon on the left side panel  
+ - Select **Account settings** from the menu 
  - From the left sidebar, select **Projects** 
  - Choose the project from the list
  - Select **Connection** to edit the connection details
  - Locate the **Redirect URI** field under the **OAuth 2.0 Settings** section. Copy this value to your clipboard to use later on.
 
-<Lightbox src="/img/docs/dbt-cloud/using-dbt-cloud/dbt-cloud-enterprise/BQ-auth/dbt-cloud-bq-id-secret-02.gif" title="Accessing the BigQuery OAuth configuration in dbt Cloud" />
+<Lightbox src="/img/docs/dbt-cloud/using-dbt-cloud/dbt-cloud-enterprise/BQ-auth/dbt-cloud-bq-id-secret-02.png" title="Accessing the BigQuery OAuth configuration in dbt Cloud" />
 
 ### Creating a BigQuery OAuth 2.0 client ID and secret
 To get started, you need to create a client ID and secret for [authentication](https://cloud.google.com/bigquery/docs/authentication) with BigQuery. This client ID and secret will be stored in dbt Cloud to manage the OAuth connection between dbt Cloud users and BigQuery.
@@ -64,10 +65,12 @@ Now that you have an OAuth app set up in BigQuery, you'll need to add the client
 ### Authenticating to BigQuery
 Once the BigQuery OAuth app is set up for a dbt Cloud project, each dbt Cloud user will need to authenticate with BigQuery in order to use the IDE. To do so:
 
-- Select the gear menu in the upper left corner and choose **Profile settings**
+- Navigate to your account name, above your profile icon on the left side panel
+- Select **Account settings** from the menu
 - From the left sidebar, select **Credentials**
 - Choose the project from the list
 - Select **Authenticate BigQuery Account**
+
 <Lightbox src="/img/docs/dbt-cloud/using-dbt-cloud/dbt-cloud-enterprise/developer-bq-auth.gif" title="Authenticating to BigQuery" />
 
 You will then be redirected to BigQuery and asked to approve the drive, cloud platform, and BigQuery scopes, unless the connection is less privileged.