> ## Documentation Index
> Fetch the complete documentation index at: https://docs.hypergsc.com/llms.txt
> Use this file to discover all available pages before exploring further.

# HyperGSC authentication and permissions

> Understand browser OAuth, enabled-property access, optional research-write consent, client authorization, and Google connection revocation.

There are two separate authorizations: Google lets HyperGSC read Search Console, and HyperGSC lets an AI client use your account's enabled properties.

## OAuth for AI clients

Connect your AI assistant through browser OAuth. The client discovers HyperGSC's authorization server, opens a sign-in and consent flow, and receives credentials for the MCP resource.

The default scope is `gsc:read`. This lets the connection read authorized data within current property and plan restrictions.

For custom clients, HyperGSC supports authorization code with PKCE S256 and dynamic client registration. Follow [the authentication walkthrough](https://hypergsc.com/auth.md) and discovered metadata rather than hardcoding an OAuth exchange.

## Optional research writes

Saving or deleting keywords and SEO change records requires `projects:write` in addition to `gsc:read`, and an eligible plan.

These writes store research in HyperGSC. They do not edit Google Search Console or your website. A read-only grant cannot perform them; reconnect with the required consent when needed.

## Manage client access

Review the permissions requested during browser sign-in. If your authorization expires, reconnect the assistant and complete consent again.

Client authorization is separate from the Google connection. Disconnect a client when you no longer want it to access HyperGSC.

## Manage the Google connection

Disconnecting Google in HyperGSC removes that connection's credentials and properties. To revoke the underlying Google grant too, remove HyperGSC from your Google account's third-party access settings.

Google may expire or revoke refresh credentials. Reconnect from **Connections** when HyperGSC reports that Google authorization must be renewed.

## Property selection is shared

Property choices apply across connected clients. Authorizing a new client does not expose every property the Google account can access; a property must be enabled in HyperGSC.

See [connection management](https://docs.hypergsc.com/guides/connect-search-console.md) and [troubleshooting](https://docs.hypergsc.com/troubleshooting.md).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.