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

# Integrations and permissions

> Review Alesta's complete connection roster, identity selection, permissions, and revocation boundaries.

Integrations add authorized provider evidence or enable a narrowly confirmed action. A listed provider is not automatically connected, supported by every workflow, or guaranteed to return data.

## Open the connection roster

Open **Settings > Integrations**. Alesta groups current connections by their product pillar and places tools without an Analytics area under **Other tools**.

A provider removed from the product appears under **Removed from Alesta** only so you can disconnect and revoke the access the workspace still holds. It cannot be connected or reselected.

## Read the row

Each row can show:

* provider name and purpose;
* connected account identity;
* selected property, site, organization, or resource;
* current state;
* a reason sentence;
* Connect, Choose, Change, Reconnect, or Disconnect controls.

| Badge           | Meaning                                                                           |
| --------------- | --------------------------------------------------------------------------------- |
| Connected       | Authorization is ready; dependent panels can still have no data                   |
| Connecting      | Alesta is validating or preparing the connection                                  |
| Action needed   | You must select a resource before the connection can answer its intended question |
| Needs attention | Authorization or provider state requires repair                                   |
| Removed         | The product no longer uses the provider; disconnect to revoke access              |

## Permission checklist

Before connecting, confirm:

* the active Alesta workspace;
* the external account identity;
* the person is authorized to grant access;
* the requested scopes;
* whether access is read-only or supports a confirmed external write;
* the exact property, organization, repository, or site;
* the business question the connection should answer;
* the provider-side revocation path.

Use the smallest appropriate scope.

## Connection does not equal capability

A connected credential can still lead to an unavailable panel because:

* the workspace plan does not include the reading;
* a required service is not deployed;
* provider verification or commercial access is incomplete;
* the selected identity lacks data or permission;
* the provider returned no usable evidence.

Similarly, a visible panel does not prove its required provider is currently connectable.

## Keep source identity with the result

For connected measurements, retain:

* provider and selected account;
* selected property or resource;
* reporting population;
* time window and time zone;
* metric definition;
* retrieval date;
* partial or unavailable caveat.

Do not copy a number into another document without this context.

## Disconnect safely

<Steps>
  <Step title="Confirm the workspace and provider">
    Check both identities before revoking access.
  </Step>

  <Step title="Record the last valid evidence date">
    Note which reports or decisions depend on the connection.
  </Step>

  <Step title="Select Disconnect">
    Confirm the provider control. For a retired row, disconnect is the only available action.
  </Step>

  <Step title="Verify provider-side access if needed">
    Use the provider's own security settings when organization policy requires complete revocation.
  </Step>
</Steps>

Previously generated documents can retain information already incorporated into their content. Review and correct or delete that material separately when required.

## References

* [Connect an integration](/guides/connect-an-integration)
* [Traffic analytics](/workspace/traffic-analytics)
* [Social analytics](/workspace/social-analytics)
* [Trust and data scope](/security/trust)