feat: update OAuth scopes for Confluence, Gmail, Google Calendar, Google Drive, and Jira connectors

surfsense_web/content/docs/connectors/confluence.mdx

@@ -79,6 +79,8 @@ Select the **"Granular scopes"** tab and enable:
 | View pages | `read:page:confluence` | View page content |
 | View comments | `read:comment:confluence` | View comments on pages or blogposts |
 | View spaces | `read:space:confluence` | View space details |
+| Write pages | `write:page:confluence` | Create and update page content |
+| Delete pages | `delete:page:confluence` | Delete pages |
 
 4. Click **"Save"**
 

surfsense_web/content/docs/connectors/gmail.mdx

@@ -37,10 +37,16 @@ This guide walks you through setting up a Google OAuth 2.0 integration for SurfS
 
 1. Click **Add or Remove Scopes**
 2. Add the following scopes:
-   - `https://www.googleapis.com/auth/gmail.readonly` - Read Gmail messages
+   - `https://www.googleapis.com/auth/gmail.modify` - Read, compose, send, and permanently delete Gmail messages
    - `https://www.googleapis.com/auth/userinfo.email` - View user email address
+   - `https://www.googleapis.com/auth/userinfo.profile` - View user profile info
+   - `openid` - OpenID Connect authentication
 3. Click **Update** and then **Save and Continue**
 
+<Callout type="info">
+  The `gmail.modify` scope is required for HITL (Human-in-the-Loop) tools like sending emails, creating drafts, and trashing messages. If you only need read access, you can use `gmail.readonly` instead, but HITL tools will not work.
+</Callout>
+
 ## Step 4: Create OAuth Client ID
 
 1. Go to **APIs & Services** > **Credentials**

surfsense_web/content/docs/connectors/google-calendar.mdx

@@ -37,9 +37,13 @@ This guide walks you through setting up a Google OAuth 2.0 integration for SurfS
 
 1. Click **Add or Remove Scopes**
 2. Add the following scope:
-   - `https://www.googleapis.com/auth/calendar.readonly` - Read Google Calendar events
+   - `https://www.googleapis.com/auth/calendar.events` - Read, create, update, and delete Google Calendar events
 3. Click **Update** and then **Save and Continue**
 
+<Callout type="info">
+  The `calendar.events` scope is required for HITL (Human-in-the-Loop) tools like creating, updating, and deleting calendar events. If you only need read access, you can use `calendar.readonly` instead, but HITL tools will not work.
+</Callout>
+
 ## Step 4: Create OAuth Client ID
 
 1. Go to **APIs & Services** > **Credentials**

surfsense_web/content/docs/connectors/google-drive.mdx

@@ -37,10 +37,16 @@ This guide walks you through setting up a Google OAuth 2.0 integration for SurfS
 
 1. Click **Add or Remove Scopes**
 2. Add the following scopes:
-   - `https://www.googleapis.com/auth/drive.readonly` - Read-only access to Google Drive
+   - `https://www.googleapis.com/auth/drive` - Full access to Google Drive (read, create, and trash files)
    - `https://www.googleapis.com/auth/userinfo.email` - View user email address
+   - `https://www.googleapis.com/auth/userinfo.profile` - View user profile info
+   - `openid` - OpenID Connect authentication
 3. Click **Update** and then **Save and Continue**
 
+<Callout type="info">
+  The `drive` scope is required for HITL (Human-in-the-Loop) tools like creating and trashing files. If you only need read access, you can use `drive.readonly` instead, but HITL tools will not work.
+</Callout>
+
 ## Step 4: Create OAuth Client ID
 
 1. Go to **APIs & Services** > **Credentials**

surfsense_web/content/docs/connectors/jira.mdx

@@ -66,6 +66,7 @@ This guide walks you through setting up an Atlassian OAuth 2.0 (3LO) integration
 |------------|------|-------------|
 | View Jira issue data | `read:jira-work` | Read Jira project and issue data, search for issues, and objects associated with issues like attachments and worklogs |
 | View user profiles | `read:jira-user` | View user information in Jira that the user has access to, including usernames, email addresses, and avatars |
+| Create and manage issues | `write:jira-work` | Create, edit, and delete issues, comments, worklogs, and other Jira data the user has access to |
 
 4. Click **"Save"**