What the labels mean
Not every part of Spek is open to every workspace. Rather than leaving you to discover that by clicking, here is the current state.
| Label | What it means for you |
|---|---|
| Available | In the dashboard for any workspace that meets the prerequisites, such as having a store credential. |
| Limited availability | Enabled per workspace. You may not see it, and that is expected rather than a fault. |
By surface
| Surface | Status | Platforms |
|---|---|---|
| Onboarding and adding an app | Available | App Store and Google Play |
| Agent proposals | Available | App Store and Google Play |
| Agent chat | Available after Agent setup | App Store and Google Play |
| Editor and publishing | Available | App Store and Google Play |
| Competitors | Available | App Store and Google Play |
| Custom product pages and page tests | Available when Apple has made your app eligible | iOS |
| In-app events | Available | iOS |
| Changelog | Available | App Store and Google Play |
| Workspace, profile and members | Available | Workspace-wide |
| Plans, credits, and billing | Limited availability | Workspace-wide |
Not available
Two things people ask about that are not open today.
| Surface | Current state |
|---|---|
| The keyword workbench | Not a customer surface today. The metrics it produces still drive the agent, and are explained in how the agent picks keywords. |
| Reviews and replies | Not a dashboard surface today. The inbox and its workspace draft settings are not currently available. |
Common questions
Something in this page does not match what I see.
Then one of the two is wrong and we would like to know which. Tell us which surface and which workspace.
Include your workspace, selected app, store, role and the exact control or behavior involved. A screenshot can help when it contains no secrets. That context lets the team distinguish a documentation mismatch from a setup, permission or provider-eligibility requirement.
How do I get access to something marked limited?
Ask. Limited availability means it is enabled per workspace rather than gated behind a plan.
What should I check when a feature is missing from my workspace?
Check the selected workspace and app, your membership role, completion of any required setup and the provider prerequisites listed for that surface. Some App Store features depend on Apple's eligibility state, while other capabilities depend on workspace availability. A missing control therefore does not always indicate a broken page. Compare your situation with the specific feature's guide and contact Spek with the relevant context if it still disagrees. Avoid inferring availability from a marketing illustration or another teammate's different app.
Does a higher plan automatically unlock every store capability?
A commercial plan and provider eligibility are different requirements. An app can need a particular App Store state or permission even when its workspace has an appropriate subscription. Limited availability can also be managed at the workspace level. Review the prerequisites attached to the feature you intend to use rather than assuming a plan change will resolve every missing action. If you are evaluating Spek for a specific workflow, confirm that workflow's current scope before making it a dependency in your team's process.
How should I interpret screenshots and product previews?
Use them to understand the workflow and interface being illustrated, then consult the relevant guide for platform scope, setup and permission requirements. A preview is not evidence that every connected app is eligible for the pictured action. App Store-specific features retain their Apple scope even though Spek's public ASO positioning covers both stores. When a detail matters to your rollout, check the actual surface for your selected app and ask support to resolve any disagreement between the documentation and what you see.
What makes an availability report actionable?
Name the workspace, app, store, feature and the role you are using, then describe what the documentation led you to expect and what appears instead. Include the relevant setup or provider-state message if one is visible. This separates a permissions question from an eligibility or product-availability question. Keep credentials and private customer information out of the report. The team can then check the concrete workflow rather than interpreting a broad statement that an entire dashboard or plan is missing something.