Skip to main content
Connections add authorized provider context to a workspace. Connect only the account and resource that belong to the selected company, and review the requested permissions before approval.

​
Choose the connection surface

  • Use Analytics > Traffic to connect Google Analytics or Google Search Console in the context of the panels they populate.
  • Use Analytics > Social for social providers offered to the current workspace.
  • Use Settings > Integrations for the complete connection roster, including GitHub and other tools that do not belong to an Analytics tab.
All three entry points use the same underlying connection state.

​
Connect and verify

1

Confirm the workspace

Check the company name and domain before authorizing anything.
2

Select Connect

Open the provider row or card and choose the available OAuth or credential method.
3

Review access

Read the provider’s permission screen and choose the intended account. Cancel if the requested access or identity is unexpected.
4

Complete resource selection

If Alesta shows Action needed, choose the property, organization, site, or repository that should feed this workspace.
5

Verify Connected

Confirm the row shows Connected and inspect the account and selected-resource label.
6

Check the dependent panel

Return to the relevant Analytics or Signal surface and confirm it attributes data to the expected source.

​
Connection states

​
Change a selected resource

When the provider supports selection, choose Change from the connected row. Select the intended property and then re-check the dependent panel. Never assume the previous data belongs to the newly selected resource.

​
Disconnect

Select Disconnect and confirm the provider. Disconnecting removes Alesta’s active access for that workspace, but provider-side revocation and retention can also depend on the provider’s own controls and policies. After disconnecting, provider-backed panels can return to a disconnected or unavailable state. Public-domain baseline results remain separate.

​
GitHub-specific note

A GitHub connection can support a Signal’s confirmed issue-creation action. Alesta lists only accessible repositories eligible to receive an issue. The connection does not grant permission for Alesta to change code, create branches, or deploy.

​
References