---
title: Feature availability
description: Understand why a Runner page may be hidden, gated, empty, or unavailable and choose the right next step.
---

Runner can show different features according to workspace, role, plan, store type, publication state, connected services, data, and staged release access.

**Entry path:** Runner documentation → **Advanced features** → **Feature availability**.

## Common availability gates

| What you see | Likely requirement | What to do |
| --- | --- | --- |
| Entry is missing | The feature is staged, disabled, or not available to this workspace. | Check the workspace and ask an owner or support. Do not use a guessed URL. |
| Upgrade message | The current plan does not include the action or its limit was reached. | Open **Plan & Billing** and review the current on-screen offer. |
| Publish requirement | The tool needs a live store or published site data. | Complete the publication checklist, then return after a successful publication. |
| Connect button | A provider or account must be connected first. | Open the named app and complete its official connection flow. |
| Empty dashboard | The feature is available but does not have data for the selected store, filter, or period. | Confirm store, date range, publication, and event collection. |
| Permission message | Your workspace role cannot perform the action. | Ask an owner to complete it or change access. |
| Page not found | The route is unavailable, retired, or not valid for this context. | Return through visible navigation and contact support if the entry itself is broken. |

## Check in order

1. Confirm the selected workspace and store.
2. Return to the visible project navigation instead of editing the URL.
3. Check whether the page names a prerequisite.
4. Check your role and the current plan from workspace settings.
5. Confirm required publication, data, or app connection.
6. Reload once after a recent access or connection change.
7. Contact support with the exact page, visible state, workspace, and store name.
### What not to assume

- A hidden entry does not prove the feature was removed from every account.
- An empty page does not prove collection is broken.
- A source route does not prove your workspace can use the feature.
- A successful connection does not prove downstream checkout, fulfillment, or reporting without an end-to-end result.

## Related guides

- [States and availability](../help-and-reference/states-and-availability)
- [Subscription plans](../plans-and-billing/subscription-plans)
- [Troubleshoot publishing, checkout, and apps](../help-and-reference/troubleshoot-publishing-checkout-apps)
- [Support and community](../help-and-reference/support-and-community)