Does Discera ever write to Gong?

No. Every scope Discera requests is read-only. We do not create, update, or delete calls, users, or any other Gong resource.

Can I limit Discera to a subset of these scopes?

Not today. Each scope maps to a feature the analysis pipeline depends on — dropping any of them would break a core path (no metadata, no transcripts, or no rep attribution).

Are scopes the same for OAuth and basic-auth?

Basic-auth credentials don't use scopes — they inherit whatever permissions the Gong user who created the key holds. We recommend a Gong user with read access to calls, transcripts, and users so the basic-auth path matches OAuth behavior.

Will Discera ask for more scopes later?

If new features require additional access (for example, listing folders or fetching specific deal-linked recordings), we'll request them on a fresh consent screen — your existing grant won't silently widen.

What Gong permissions does Discera request, and why?

Integrations / Gong·May 31, 2026·1 min·By Discera Team

Discera requests four read-only Gong scopes: basic call metadata, extensive metadata, transcripts, and user list. No write access.

TL;DR

Discera asks for four read-only Gong scopes: api:calls:read:basic, api:calls:read:extensive, api:calls:read:transcript, and api:users:read. Nothing in Gong is modified, created, or deleted.

The four scopes

`api:calls:read:basic`

Lets Discera list calls in a date range and read basic metadata — participants, duration, direction, start time. We use this to enumerate which calls fall inside the window you analyze and to power filter previews before a run starts.

`api:calls:read:extensive`

Lets Discera read the full call record from Gong's /v2/calls/extensive endpoint, including any HubSpot deal context Gong has linked to the call. The deal context is what powers Discera's HubSpot filters (stage, amount, owner, company size) without a separate HubSpot connection.

`api:calls:read:transcript`

Lets Discera fetch the transcript text for each analyzed call. Transcripts are the primary input the analysis prompt evaluates — without this scope, Discera can read metadata but cannot answer questions about call content.

`api:users:read`

Lets Discera resolve Gong user IDs to display names and email addresses, so reports show the actual rep on each call instead of an opaque ID. We use this only to enrich call records for the UI and downloadable reports.

What we don't request

Discera never asks for write scopes, scorecard scopes, or scopes covering calls outside your tenant. If a future feature needs broader access, Gong will surface a fresh consent screen — your existing grant stays narrow until you approve the new request.