Allow Talk & Comment sign-in in Google Workspace

Use this guide when someone clicks Continue with Google and Google says their administrator blocked access. A Google Workspace administrator with the Service Settings privilege must review the school's app-access policy. Talk & Comment cannot change that Google policy for you.

Review what sign-in shares

Ordinary Talk & Comment sign-in requests the email and profile scopes. These provide the person's name, email address, and profile photo when Google supplies one.

It does not request access to Google Drive, Google Classroom, or Gmail. Separately, the school admin console's domain-verification flow requests openid email profile to verify the administrator's identity and domain.

Review or configure the app in Google Admin

These labels follow Google's app-access instructions.

1. Open app access controls. In the Google Admin console, go to Security → Access and data control → API controls, then click Manage App Access.
2. Find Talk & Comment. Review Configured apps, Accessed apps, or Apps pending review. Open the app's details to check its identity and requested scopes.
3. Add it if needed. Under Configured apps, click Configure new app. Search for Talk & Comment by name or OAuth client ID: 823194554797-rqlrc2ieua654odakrennnjagrad4qt6.apps.googleusercontent.com. Select the matching app and check its details before approving access.
4. Scope the approval. For a new app, use Select org units → Include organizations to choose the approved organizational units, then Select and Continue. Start with your teacher pilot; include students only for approved school workflows.
5. Choose the access level. Under Access to Google data, choose Trusted if your school's review approves that access level. Alternatively, Specific Google data can limit access to the scopes you select; include the required Google Sign-in scopes.
6. Finish the matching flow. For a new app, click Continue, review the settings, and click Finish. When changing access from an existing app's information page, select the organizational unit and access level, then click Save.

Trusted is Google's broader app-access setting. It does not mean Talk & Comment's current sign-in request includes Drive, Classroom, or Gmail scopes.

Google says app details typically appear 24–48 hours after authorization, and policy changes can take up to 24 hours. Do not expect an attempted sign-in to appear immediately.

Keep the three school controls separate

Control	What it governs
Google Workspace app access	Whether school accounts may authorize the Google sign-in request.
Chrome extension policy	Whether the extension can be installed or force-installed on managed Chrome devices. See school IT setup.
Talk & Comment team policies	Student recording, external sharing, and AI permissions. See the school admin console.

Public voice-note links can be heard without an account or extension. When the recording owner's team turns off External sharing, listeners need a signed-in account belonging to that Talk & Comment team. Sign-in approval alone does not grant team membership, and student listening does not require turning on student recording.

Retry or ask for help

1. Retry with the intended school account. Return to Talk & Comment and click Continue with Google, or Try again with Google if shown.
2. Capture the exact failure if it continues. Give your school IT staff the school's domain and Google's full error message. Not every sign-in failure is an app-access policy block.
3. Ask an adult to contact support if needed. A teacher, parent, or school admin can email Talk & Comment support with the domain and error. Students should use that adult support route.

For the school's agreement review, read privacy and DPAs for schools.