Skip to main content
Back to Integrations
Gong logo

Gong

Inventory Gong users and whether each one is recorded, the permission profiles that decide who can download, export, share or delete call recordings, and the audit trail of sign-ins, admin activity, impersonation and calls shared outside the company.

Questions you can answer 15

Each one is a saved query that ships with ConfigView, reading your Gong data on your own server. Ask it in plain English, SQL, Slack or the API.

  • Which Gong call recordings were opened by people outside the company?
  • Who shared Gong calls externally in the last 30 days?
  • Were any Gong recordings played by someone outside the company this month?
  • Has Gong support impersonated any of our users?
  • Who acted as another user in Gong recently?
  • Show Gong impersonation activity in the last 90 days
  • Which Gong seats have not been used in 30 days?
  • Who has an active Gong license but never logs in?
  • Are we paying for Gong seats nobody uses?
  • Who can download Gong call recordings?

What ConfigView collects from Gong 5

  • Audit Logs

    Gong's five audit logs, kept as a growing history: sign-ins (Gong keeps these 14 days only, so this must run daily), user and admin activity, who played which call, and every time a call shared outside the company was opened or played. Includes Gong staff acting inside the account.

  • Permission Profile Users

    Which permission profile each Gong user has, in each workspace.

  • Permission Profiles

    Each workspace's permission profiles: how much of the company's calls, deals, emails and coaching each one can see, and whether it can download call recordings, share calls with customers, export data or delete calls.

  • Users

    Every Gong user: name, email and aliases, title, manager, whether the seat is active, and whether their web meetings, phone calls and emails are recorded or imported.

  • Workspaces

    The company's Gong workspaces (usually one per team or region).