> For the complete documentation index, see [llms.txt](https://support.doowii.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.doowii.io/external-data-connections/granting-doowii-access-to-google-classroom.md).

# Granting Doowii Access to Google Classroom

This guide explains how your Google Workspace Administrator can securely grant Doowii access following Google’s recommended practices for delegated access to Classroom APIs.

Doowii integrates with Google Workspace for Education to ingest Google Classroom data (including coursework, course rosters, assignments, submissions, and materials) so your organization can analyze teaching and learning workflows in one place.

{% hint style="success" %}
**Prerequisites**

1. Google Workspace for Education Fundamentals or higher
2. Admin privileges to the Google Admin console
3. The Doowii-provided service account email (shared privately during setup)
4. Confirmation that your organization permits third-party API access to Classroom
   {% endhint %}

***

## 1. Overview of Doowii’s Google Classroom Integration

Doowii uses Google Classroom APIs to read and (optionally) write teaching and learning data.

This enables:

* Class roster and content access for alignment with SIS data and reporting
* Performance analytics for teachers and academic leaders
* Optional Data-Driven Content Generation:
  * Lesson plan generation workflows
  * Quiz and assignment generation
  * Assignment and material publishing

The integration uses a Doowii-owned Google Cloud service account, authorized via domain-wide delegation within your Google Workspace tenant.

***

## 2. Required OAuth Scopes

Depending on your institution’s selected workflows, you may choose Read Only access or Read + Write access.&#x20;

{% hint style="warning" %}
**Confirm with your Doowii representative on the the OAuth Scopes needed for your project.**&#x20;
{% endhint %}

#### 2.1 Read-Only Scopes (Standard Analytics Use Cases)

<table data-header-hidden><thead><tr><th width="208.43359375"></th><th></th></tr></thead><tbody><tr><td>Purpose</td><td>Scope</td></tr><tr><td>List/view courses</td><td>https://www.googleapis.com/auth/classroom.courses.readonly</td></tr><tr><td>List/view coursework (assignments, materials)</td><td><p>https://www.googleapis.com/auth/classroom.coursework.me.readonly</p><p>https://www.googleapis.com/auth/classroom.coursework.students.readonly</p></td></tr><tr><td>View student rosters</td><td>https://www.googleapis.com/auth/classroom.rosters.readonly</td></tr><tr><td>View course topics</td><td>https://www.googleapis.com/auth/classroom.topics.readonly</td></tr></tbody></table>

These scopes allow Doowii to read course structures, teaching materials, rosters, and assignments.

***

#### 2.2 Write Scopes (Optional – For Content Generation)

Only enable these if your organization has partnered with Doowii to push generated content *into* Google Classroom.

<table data-header-hidden><thead><tr><th width="208.33203125"></th><th></th></tr></thead><tbody><tr><td>Purpose</td><td>Scope</td></tr><tr><td>Create/update coursework</td><td><p>https://www.googleapis.com/auth/classroom.coursework.me</p><p>https://www.googleapis.com/auth/classroom.coursework.students</p></td></tr><tr><td>Create/update course materials</td><td>https://www.googleapis.com/auth/classroom.courses</td></tr><tr><td>Manage topics</td><td>https://www.googleapis.com/auth/classroom.topics</td></tr></tbody></table>

Generally, we propose all content that Doowii writes to your Classroom be labeled clearly as “Doowii Generated”.

***

## 3. Step-by-Step Setup Instructions

### Step 1 — Customer Org: Verify API Access Is Enabled in Google Admin Console

1. Go to Admin Console → Security → API Controls
2. Ensure “Enable API access” is checked
3. Confirm that the Organization allows third-party app integrations
   * (This is default for most EDU tenants.)

### Step 2 — Doowii: Provide Service Account Client ID

Doowii provides your organization with:

* The GCP service account email
* The unique OAuth 2.0 Client ID associated with the service account

You will use these in Step 3.

### Step 3 — Customer Org: Grant Domain-Wide [Delegation](https://developers.google.com/admin-sdk/directory/v1/guides/delegation) to the Doowii Service Account

1. In the Google Admin Console:

   Security → API Controls → Domain-wide delegation
2. Click Add new.
3. Enter the Client ID provided by Doowii.
4. Add the required OAuth scopes (comma-separated).

Example (read-only):

```
https://www.googleapis.com/auth/classroom.courses.readonly,
https://www.googleapis.com/auth/classroom.rosters.readonly,
https://www.googleapis.com/auth/classroom.coursework.me.readonly,
https://www.googleapis.com/auth/classroom.coursework.students.readonly,
https://www.googleapis.com/auth/classroom.topics.readonly
```

Example (read/write):

```
https://www.googleapis.com/auth/classroom.coursework.me,
https://www.googleapis.com/auth/classroom.coursework.students,
https://www.googleapis.com/auth/classroom.courses,
https://www.googleapis.com/auth/classroom.topics
```

5. Click Authorize.

### Step 4 — Customer Org: Confirm [Classroom API](https://developers.google.com/workspace/classroom) Is Enabled

1. Go to Google Cloud Console for your Workspace organization.
2. Navigate to: APIs & Services → Enabled APIs & Services
3. Verify Classroom API is enabled.
4. If not, click Enable APIs and Services → Classroom API → Enable.

### Step 5 — Doowii: Validate Access and Begin Initial Sync

Doowii completes:

* Token validation
* Scope confirmation
* Classroom → SIS roster alignment
* Initial metadata sync
* Optional write-access smoke test (if granted)<br>

This step should not require customer participation unless issues arise.

***

## 4. Summary (For Administrators)

To grant Doowii access:

1. Enable API access
2. Authorize Doowii’s service account via domain-wide delegation
3. Add the required Classroom API scopes
4. Confirm Classroom API is active
5. Notify Doowii to begin verification and ingestion<br>

This process uses Google-recommended methods and is fully auditable.

{% hint style="info" %}
**References (Google Documentation)**

* Google Classroom API Overview: <https://developers.google.com/classroom>
* Delegated Domain-Wide Authority: <https://developers.google.com/admin-sdk/directory/v1/guides/delegation>
* OAuth Scopes for Classroom: <https://developers.google.com/classroom/guides/auth>
  {% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://support.doowii.io/external-data-connections/granting-doowii-access-to-google-classroom.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
