Meeting Companion: Admin Setup Guide (Google Workspace)

Authorise ELSA once for your Google Workspace domain, and every eligible learner gets automatic post-meeting feedback for Google Meet.
If the Google row in your Web Conferencing settings still shows Coming Soon, the Workspace connection hasn’t been switched on for your organisation yet, your ELSA CSM can enable it and walk you through the steps below.

1. Who this guide is for

Follow these steps if all of the following are true:

• You’re a Google Workspace admin who can authorise apps and manage Domain-Wide Delegation in the Google Admin console.

• Your organisation is on an ELSA for Business plan (the Workspace-level setup isn’t available on individual accounts).

• You have an admin seat at app.elsaspeak.com/business.

2. What the Workspace install unlocks

One domain-level authorisation covers every learner on your plan, no per-user OAuth prompt and no individual setup.

Post-meeting analysis works with the Workspace install alone. If a team also needs real-time in-call coaching, those learners complete a one-time individual authorisation in addition to your Workspace setup.

3. Enable ELSA on your Google Workspace

The whole flow takes about ten minutes, including the Google Admin console step.

1. Sign in to the ELSA admin console. Open app.elsaspeak.com/business and log in with your ELSA admin account.

2. Go to Settings → Integrations → Web Conferencing. In the left sidebar, choose Settings, then the Integrations tab, then the Web Conferencing section.

3. Click “Connect Google Workspace”. ELSA shows your domain’s connection details — the ELSA service-account client ID and the exact scope list to authorise. Keep this tab open; you’ll paste these into Google next.

4. Authorise ELSA in the Google Admin console. In admin.google.com, go to Security → Access and data control → API controls → Domain-wide delegation, click Add new, and paste the ELSA client ID plus the scope list from step 3. Every scope is read-only:

   • Basic profile & email — identify each learner’s account

   • Calendar (read-only) — detect upcoming Meet calls

   • Meet space info (read-only) — find the right meeting

   • Meet audio (read-only) — generate speaking feedback

   • Directory (read-only) — map meeting participants to your Workspace users

5. Verify the connection. Back in ELSA, click Verify. The Google row will show Connected · your domain and the Learners Synced panel starts filling in.

6. Assign learners. Under People → Groups, choose who is eligible. Any learner in an enabled group whose ELSA email matches a Workspace directory entry starts getting reports automatically after their next Google Meet call.

Learners never see a Google OAuth prompt. As long as the meeting is on your connected Workspace domain and the participant is on the ELSA plan, ELSA can process it.

4. Managing learners & seats

• Provisioning: add learners via SAML SSO, SCIM, CSV upload, or email-domain auto-provisioning from the People tab.

• Group-level reporting: create groups (team, department, cohort) and see aggregated speaking time, pronunciation, and improvement trends.

• Learner opt-out: individual learners can pause Meeting Companion any time. You see a coverage indicator, never the raw audio.

• Digests: automatic weekly PDF digests to your inbox, plus a CSV export endpoint on the API.

5. Data, privacy & compliance

• Encryption: audio and transcripts are AES-256 encrypted at rest and served over TLS 1.2+.

• Only the speaker’s segments: ELSA analyses each learner’s own speech; other participants’ audio is used solely to separate speakers.

• Retention: default 90-day retention on raw audio; feedback reports persist per your plan; custom windows on Enterprise.

• Compliance: SOC 2 Type II, GDPR, and signed DPAs (with the sub-processor list) are available on request from your ELSA CSM.

• Google data use: follows the Google API Services User Data Policy, including Limited Use: no ads, no selling data, no training of generalized AI models. The full Domain-Wide Delegation scope list is disclosed in ELSA’s Privacy Policy.

• Learner data deletion: a learner can request deletion of their feedback history via privacy@elsanow.io.

6. For developers (API)

Every action in the admin console is backed by a REST API, so you can sync ELSA state into your HRIS, LMS, or BI stack. The production base URL is https://api.elsaspeak.com, and requests authenticate with an admin bearer token from Settings → API keys → Generate (treat it like any admin credential).

Common endpoints include listing meetings (/meetings), fetching a learner’s cached report (/meetings/{id}/participants/{pid}/analyze), and subscribing to the meeting.analyzed webhook to push scores into an LMS. The full OpenAPI spec, rate limits, and samples are in the developer portal at app.elsaspeak.com/business/developers; sandbox tokens are free on any B2B plan.

This is a condensed pointer. If you’d like a full API reference as its own help article, that can be built from the developer portal.

7. Troubleshooting