> ## 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.

# Availability, plans, and access

> Separate plan entitlement, workspace role, provider readiness, data coverage, and credits.

A visible capability is not necessarily runnable, and a plan entitlement does not guarantee that a provider will return data. Alesta evaluates several boundaries before it can show a result or start an action.

## The availability stack

<Steps>
  <Step title="Plan entitlement">
    The workspace plan must include the panel or action. A lock and upgrade prompt indicate a plan boundary.
  </Step>

  <Step title="Member role">
    Some administration actions require the workspace Owner. Other workspace work may be available to both Owner and Admin roles.
  </Step>

  <Step title="Connection and selection">
    Provider-backed measurements may require authorization and a selected account, property, organization, or repository.
  </Step>

  <Step title="Service readiness">
    The Alesta service and third-party provider must support the requested operation in the current environment.
  </Step>

  <Step title="Source coverage">
    The source must have usable data for the domain and requested window.
  </Step>

  <Step title="Credits and target lock">
    Eligible paid actions require remaining capacity, and only one action can run on the same protected target at a time.
  </Step>
</Steps>

## Plan boundaries

<Tabs>
  <Tab title="Free">
    Includes one zero-rated domain-first profiling run for an eligible workspace. It provides the bounded public baseline and free documents available to that run. New chat turns, Signals, deeper Web areas, Social measurement, and model-backed corrections can be plan-locked.
  </Tab>

  <Tab title="Pro">
    Adds monthly capacity and access to eligible workspace actions and readings. The exact catalog, price, and allowance shown in Billing are the source of truth for the current environment.
  </Tab>

  <Tab title="Enterprise">
    Uses commercial scope and availability confirmed with the Alesta team. Do not assume that every catalog capability is included until it appears in the agreement and product.
  </Tab>
</Tabs>

See [Pricing](https://alesta.ai/pricing) and [Billing](/billing) for the current plan catalog.

## Common states and responses

| What you see     | What it means                                                     | Next step                                                           |
| ---------------- | ----------------------------------------------------------------- | ------------------------------------------------------------------- |
| Upgrade          | The current plan does not include the capability                  | Review the plan in Billing; only the Owner can change billing       |
| Connect          | A provider is required and not linked                             | Review permissions and start the connection flow                    |
| Choose or Change | Authorization exists, but a property or resource must be selected | Select the source that belongs to this workspace                    |
| Reconnect        | The credential or authorization needs attention                   | Reauthorize and confirm the selected resource                       |
| Unavailable      | The service or source could not produce the result                | Read the reason and retry only when it suggests a transient failure |
| Coming soon      | The surface is not currently runnable                             | Do not purchase or connect anything expecting it to activate        |
| Limit reached    | Paid capacity is exhausted                                        | Wait for renewal or review plan options in Billing                  |
| Already running  | The same target has an active action                              | Let the existing action finish and follow its status                |

<Info>
  Plan access, provider support, and data coverage answer different questions. A successful upgrade can unlock a run while the final panel still reports unavailable source data.
</Info>

## References

* [Billing](/billing)
* [Credits](/credits)
* [Integrations and permissions](/account/integrations-and-permissions)
* [Locked and unavailable actions](/troubleshooting/locked-and-unavailable-actions)
