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

# Google Workspace

> Connect Google Workspace services to your Digital Twin for email, files, calendar, and more.

Pria integrates with Google Workspace to give your Digital Twin access to Gmail, Google Drive, Calendar, Sheets, Docs, Slides, Meet, Classroom, and Maps. Users can ask their Digital Twin to read emails, search files, create calendar events, and more — all within the conversation interface.

***

## Available Services

<Tabs>
  <Tab title="Communication">
    | Service         | Capabilities                              | Auth Type                 |
    | --------------- | ----------------------------------------- | ------------------------- |
    | **Gmail**       | Read, search, and send emails             | OAuth                     |
    | **Google Meet** | Access meeting recordings and transcripts | OAuth (requires Calendar) |

    **What you can say:**

    * "Show me my unread emails from this week"
    * "Search my inbox for messages from [jane@example.com](mailto:jane@example.com) about the budget"
    * "Send an email to the team with a summary of today's discussion"
    * "Find emails with attachments from the last 30 days"
    * "List my recent Google Meet recordings"
    * "Get the transcript from yesterday's team meeting"
  </Tab>

  <Tab title="Files & Documents">
    | Service           | Capabilities                                   | Auth Type              |
    | ----------------- | ---------------------------------------------- | ---------------------- |
    | **Google Drive**  | Browse, search, and download files to IP Vault | OAuth                  |
    | **Google Sheets** | Read spreadsheet data with structure           | OAuth (requires Drive) |
    | **Google Docs**   | Read document content with formatting          | OAuth (requires Drive) |
    | **Google Slides** | Read presentation content                      | OAuth (requires Drive) |

    **What you can say:**

    * "Search my Google Drive for the Q4 report"
    * "Download the project proposal PDF to my files"
    * "Summarize the content of my Google Doc about marketing strategy"
    * "Read the data from my Budget spreadsheet, Sheet1 cells A1 through D20"
    * "What's in my Google Slides presentation about onboarding?"
    * "Show me all spreadsheets modified in the last week"
  </Tab>

  <Tab title="Scheduling & Learning">
    | Service              | Capabilities                                                      | Auth Type |
    | -------------------- | ----------------------------------------------------------------- | --------- |
    | **Google Calendar**  | Read events, create new events with timezone awareness            | OAuth     |
    | **Google Classroom** | View courses, assignments, submissions, announcements (read-only) | OAuth     |

    **Google Calendar — What you can say:**

    * "What's on my calendar for tomorrow?"
    * "Schedule a team meeting next Tuesday at 2 PM for 1 hour"
    * "Create a recurring standup every weekday at 9 AM"
    * "Am I free this Friday afternoon?"

    **Google Classroom — What you can ask:**

    * "List my Google Classroom courses"
    * "What assignments are due this week in Biology 101?"
    * "Show me the latest announcements from my course"
    * "What student submissions have been turned in for the midterm essay?"
    * "Get the details of the Week 3 homework assignment"
    * "Show me all coursework for my Chemistry class"

    <Info>Google Classroom access is **read-only**. Pria can view courses, assignments, submissions, and announcements, but cannot create or modify them. This is ideal for students checking on coursework and instructors reviewing submissions during conversations.</Info>
  </Tab>

  <Tab title="Location">
    | Service         | Capabilities                                              | Auth Type                      |
    | --------------- | --------------------------------------------------------- | ------------------------------ |
    | **Google Maps** | Place search, geolocation, directions, reviews, geocoding | API Key (no user OAuth needed) |

    **What you can say:**

    * "Find Italian restaurants near downtown Seattle"
    * "Show me coffee shops within 2 km of my location"
    * "Get reviews for Central Park"
    * "Convert this address to GPS coordinates" (geocoding)
    * "What's the address at coordinates 40.7128, -74.0060?" (reverse geocoding)
    * "Find nearby pharmacies and show their ratings"
    * "Get the details and opening hours for this business"
  </Tab>
</Tabs>

***

## Authorization Models

Pria supports two authorization models that can be used independently or together.

### Personal Authorization

Each user connects their own Google account through their [Profile settings](/mdx/user-guide/profile-settings/google-services). They select which services to enable, authorize through Google's consent screen, and the tokens are stored securely per-user.

### Institution-Shared Authorization

Administrators can connect a shared Google account at the institution level. When configured, all users on the instance automatically gain access to the connected Google services — no individual OAuth authorization needed.

**Key use cases:**

* **Departmental access** — Share a department's Google Drive, Gmail, or Calendar with all students and staff
* **Simplified onboarding** — Users can access Google services immediately without going through OAuth consent
* **Centralized control** — Administrators manage exactly which services are available and whether access is read-only

**Service-level controls:**

* **Enabled for Users** — Each Google service can be individually toggled on or off for users. Even if the admin has connected Gmail and Drive, they can choose to expose only Drive to end users.
* **Read-Only Mode** — Services can be set to read-only at the institution level, preventing users from sending emails, creating calendar events, or modifying Drive files through the shared credentials.

### Authorization Priority

When both personal and institution-shared credentials exist, Pria resolves tokens with this priority:

1. **Institution-shared** credentials (if configured and the service is enabled for users)
2. **Personal** credentials (the user's own Google account)

<Info>This means institution-shared credentials take precedence. If an admin connects a shared Gmail, all users will use that shared Gmail rather than their personal one — even if they've also authorized their personal account.</Info>

***

## Google Maps

Google Maps does **not** require OAuth authorization. It uses a server-side API key configured in your instance settings. Users can ask their Digital Twin for place search and geolocation without any personal authorization.

***

## Service Dependencies

Some Google services require parent services to function:

| Service       | Requires        |
| ------------- | --------------- |
| Google Sheets | Google Drive    |
| Google Docs   | Google Drive    |
| Google Slides | Google Drive    |
| Google Meet   | Google Calendar |

When a user enables a dependent service, the parent service is automatically enabled as well.

***

## Troubleshooting

<AccordionGroup>
  <Accordion title="Google shows 'This app isn't verified'">
    During the OAuth consent screen, Google may display a warning that the application is not yet verified. This is expected — the Pria middleware is currently undergoing [CASA Tier 2 compliance verification](https://developers.google.com/terms/api-services-user-data-policy) with Google. To proceed, click **Advanced** and then **Go to \[app name] (unsafe)** to continue the authorization. This warning will be removed once verification is complete.
  </Accordion>

  <Accordion title="Refresh token not issued">
    Always use `prompt: 'consent'` when requesting new OAuth scopes. This forces Google to issue a new refresh token. Without it, token refresh may fail after the initial access token expires.
  </Accordion>

  <Accordion title="Users can't see Google services">
    * Check that the Google OAuth credentials are configured in the instance settings
    * Verify the APIs are enabled in Google Cloud Console
    * For institution-shared services, confirm the `enabledForUsers` flag is set for each service
  </Accordion>
</AccordionGroup>

***

## Related

* [Google Services User Guide](/mdx/user-guide/profile-settings/google-services) — End-user authorization and usage guide
* [Configuration](/mdx/admin-guide/configuration) — Instance settings including Google OAuth
* [Tools](/mdx/admin-guide/tools) — Tool definitions that power Google service interactions
* [IP Vault](/mdx/user-guide/files-documents/ipvault) — Files downloaded from Google Drive are stored here
