> ## Documentation Index
> Fetch the complete documentation index at: https://academy.pathfindr.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Administering Connectors

> Configure and govern connectors for ChatGPT Enterprise, including SharePoint, Drive, and GitHub.

<Info>
  **Audience:** IT administrators and workspace owners.

  **Goal:** Enable secure, governed access to enterprise data sources through ChatGPT connectors.
</Info>

<Info>
  **Connector security baseline**

  * Connectors are disabled by default on Enterprise plans.
  * Enable only required connectors and scope access by role or group.
  * Configure OAuth permissions and review scopes before rollout.
  * Monitor connector usage through User Analytics and Compliance API.
  * Schedule quarterly reviews to audit enabled connectors and access patterns.
</Info>

<Columns cols={3}>
  <Card title="SharePoint connector" icon="microsoft" href="#sharepoint-connector">
    Connect to SharePoint sites and document libraries with granular permissions.
  </Card>

  <Card title="Google Drive connector" icon="google" href="#google-drive-connector">
    Enable access to Drive files and folders with OAuth-based authentication.
  </Card>

  <Card title="GitHub connector" icon="github" href="#github-connector">
    Connect repositories for code review, documentation, and issue tracking.
  </Card>
</Columns>

***

## Connector administration overview

Connectors allow ChatGPT to access external data sources on behalf of users. Each connector requires explicit enablement, OAuth configuration, and RBAC scoping.

### Key principles

<Steps>
  <Step title="Default to off" icon="ban">
    All connectors are disabled by default. Enable only what teams need for validated use cases.
  </Step>

  <Step title="Scope by group" icon="users">
    Assign connector access to specific groups (e.g., Engineering, Marketing) rather than workspace-wide.
  </Step>

  <Step title="Review OAuth scopes" icon="shield-check">
    Understand what permissions each connector requests before authorizing.
  </Step>

  <Step title="Monitor usage" icon="chart-line">
    Track connector adoption and data access patterns through analytics and compliance logs.
  </Step>

  <Step title="Audit quarterly" icon="calendar">
    Review enabled connectors, group assignments, and usage patterns every 90 days.
  </Step>
</Steps>

***

## SharePoint connector

The SharePoint connector enables ChatGPT to read and reference documents from SharePoint Online sites and document libraries.

### Prerequisites

<Check>
  * SharePoint Online subscription (Microsoft 365)
  * Global Administrator or SharePoint Administrator role
  * Verified corporate domain in ChatGPT workspace
  * RBAC groups configured for connector access
</Check>

### Configuration steps

<Steps>
  <Step title="Enable the SharePoint connector" icon="toggle-on">
    Navigate to **Manage workspace → Connectors** and locate **SharePoint**. Toggle the connector to **Enabled**.
  </Step>

  <Step title="Configure OAuth permissions" icon="key">
    Click **Configure** and review the requested OAuth scopes:

    * `Sites.Read.All` — Read items in all site collections
    * `Files.Read.All` — Read all files the user can access
    * `User.Read` — Sign in and read user profile

    Approve the permissions in your Microsoft 365 admin center.
  </Step>

  <Step title="Assign to groups" icon="users">
    Under **Access control**, select which groups can use the SharePoint connector. Start with a pilot group (e.g., "Knowledge Workers Pilot") before expanding.
  </Step>

  <Step title="Test with pilot users" icon="flask">
    Have pilot users authenticate the connector in ChatGPT by clicking **Connect SharePoint** in a conversation. Verify they can access expected sites and documents.
  </Step>

  <Step title="Monitor and expand" icon="chart-line">
    Review usage in User Analytics. Once validated, expand access to additional groups as needed.
  </Step>
</Steps>

### SharePoint permissions model

The connector respects SharePoint's native permissions. Users can only access sites and documents they already have permission to view in SharePoint.

| SharePoint permission | Connector behavior                     |
| --------------------- | -------------------------------------- |
| Site member           | Can read all documents in the site     |
| Site visitor          | Can read documents they have access to |
| No access             | Cannot access site or documents        |

<Warning>
  The connector does **not** grant new permissions. It uses the authenticated user's existing SharePoint access rights.
</Warning>

### Common use cases

<AccordionGroup>
  <Accordion title="Knowledge base queries" icon="book">
    Allow teams to ask questions about internal documentation, policies, and procedures stored in SharePoint.
  </Accordion>

  <Accordion title="Document summarization" icon="file-lines">
    Summarize long reports, meeting notes, or project documentation without leaving ChatGPT.
  </Accordion>

  <Accordion title="Cross-site search" icon="magnifying-glass">
    Search across multiple SharePoint sites the user has access to in a single conversation.
  </Accordion>

  <Accordion title="Compliance document review" icon="shield-check">
    Reference compliance documentation, audit reports, and policy documents during conversations.
  </Accordion>
</AccordionGroup>

### Troubleshooting

<AccordionGroup>
  <Accordion title="Users can't see expected sites" icon="triangle-exclamation">
    **Cause:** User lacks SharePoint permissions or hasn't authenticated the connector.

    **Fix:** Verify SharePoint permissions in Microsoft 365 admin center. Have user disconnect and reconnect the SharePoint connector in ChatGPT.
  </Accordion>

  <Accordion title="OAuth consent fails" icon="xmark">
    **Cause:** Admin consent not granted or OAuth app not approved.

    **Fix:** In Microsoft 365 admin center, go to **Enterprise applications** and approve the ChatGPT connector app.
  </Accordion>

  <Accordion title="Connector not available to group" icon="users-slash">
    **Cause:** Group not assigned connector access in workspace settings.

    **Fix:** Go to **Manage workspace → Connectors → SharePoint → Access control** and add the group.
  </Accordion>
</AccordionGroup>

### Security considerations

<Warning>
  **Data handling**

  * Connector queries are logged in the Compliance API.
  * Document content accessed via connectors is subject to workspace retention policies.
  * Enterprise data is excluded from model training by default.
  * Apply Microsoft Purview DLP policies to monitor connector usage.
</Warning>

<Info>
  **Best practices**

  * Start with read-only access to non-sensitive SharePoint sites.
  * Create a dedicated pilot group for initial testing.
  * Document which sites and libraries are in scope for connector access.
  * Review connector usage monthly during pilot phase.
  * Integrate connector logs with your SIEM for anomaly detection.
</Info>

***

## Google Drive connector

The Google Drive connector enables access to files and folders stored in Google Workspace.

### Configuration steps

<Steps>
  <Step title="Enable the Drive connector" icon="toggle-on">
    Navigate to **Manage workspace → Connectors** and enable **Google Drive**.
  </Step>

  <Step title="Configure OAuth" icon="key">
    Review and approve OAuth scopes:

    * `drive.readonly` — Read-only access to Drive files
    * `userinfo.email` — User email address
  </Step>

  <Step title="Assign to groups" icon="users">
    Select which groups can use the Drive connector. Scope to teams with validated use cases.
  </Step>

  <Step title="Test and monitor" icon="chart-line">
    Pilot with a small group, verify access patterns, then expand.
  </Step>
</Steps>

<Info>
  The Drive connector respects Google Workspace sharing permissions. Users can only access files they already have permission to view.
</Info>

***

## GitHub connector

The GitHub connector enables access to repositories, issues, pull requests, and documentation.

### Configuration steps

<Steps>
  <Step title="Enable the GitHub connector" icon="toggle-on">
    Navigate to **Manage workspace → Connectors** and enable **GitHub**.
  </Step>

  <Step title="Configure OAuth" icon="key">
    Review and approve OAuth scopes:

    * `repo` — Access to private repositories (if needed)
    * `read:org` — Read organization membership
  </Step>

  <Step title="Assign to groups" icon="users">
    Scope to engineering and technical teams. Avoid workspace-wide access.
  </Step>

  <Step title="Test and monitor" icon="chart-line">
    Pilot with a small engineering team, verify repository access, then expand.
  </Step>
</Steps>

<Info>
  The GitHub connector respects repository permissions. Users can only access repositories they have been granted access to in GitHub.
</Info>

***

## Connector governance

### RBAC and group assignment

| Connector  | Recommended groups               | Rationale                                    |
| ---------- | -------------------------------- | -------------------------------------------- |
| SharePoint | Knowledge workers, all employees | Broad access to internal documentation       |
| Drive      | Marketing, operations            | Team-specific file access                    |
| GitHub     | Engineering, DevOps              | Code and technical documentation access      |
| Slack      | Customer success, support        | Historical conversation and knowledge search |

<Warning>
  Avoid assigning all connectors to all groups. Scope access based on business need and data sensitivity.
</Warning>

### Monitoring and compliance

<Tabs>
  <Tab title="User Analytics">
    Track connector adoption, usage frequency, and active users. Export CSVs for deeper analysis.
  </Tab>

  <Tab title="Compliance API">
    Export connector usage logs, including:

    * Connector authentication events
    * Data access patterns
    * User and group associations

    Integrate with your SIEM or data lake for anomaly detection.
  </Tab>

  <Tab title="Microsoft Purview">
    Apply DLP policies to monitor connector usage and flag sensitive data access. Enable Communication Compliance if required.
  </Tab>
</Tabs>

### Quarterly review checklist

<Check>
  * Review all enabled connectors and confirm business justification.
  * Audit group assignments and remove access for inactive groups.
  * Analyze connector usage patterns in User Analytics.
  * Review OAuth scopes and permissions for each connector.
  * Update connector documentation and training materials.
  * Verify compliance logs are being exported and monitored.
</Check>

***

## Appendix

<AccordionGroup>
  <Accordion title="Connector OAuth scopes" icon="key">
    Detailed OAuth scopes for each connector and what they enable.
  </Accordion>

  <Accordion title="Connector API limits" icon="gauge">
    Rate limits and quotas for connector API calls.
  </Accordion>

  <Accordion title="Data residency" icon="globe">
    How connector data is stored and processed based on workspace residency settings.
  </Accordion>

  <Accordion title="Connector deprecation policy" icon="clock">
    How OpenAI communicates connector changes, deprecations, and migrations.
  </Accordion>
</AccordionGroup>

## Self-check: Connector admin test

<Check>
  **Can an admin configure a connector in 10 minutes?**

  * I know which connectors are available and how to enable them.
  * I understand OAuth permissions and how to approve them.
  * I can scope connector access to specific groups.
  * I know how to monitor connector usage and review logs.
  * I have a plan for quarterly connector audits.
</Check>