Docs
Plans & Billing

Feature Access

Which features are unlocked by your plan, how feature locks behave, and what to do when something is unavailable.

Not every capability in Blox is available on every plan. This page lists the plan-gated features, explains what a "lock" looks like, and shows how to regain access. For the underlying model, see How Billing & Features Work.

Feature access is different from a quota — a feature is either on or off for your plan; a quota is a numeric cap (like how many sites or blog posts you can have). Blog posts, AI credits, and CMS collections are quotas, not features — see Usage Limits & Quotas for those.


Locked vs. Limited

Two different states make a feature unavailable. Recognizing which one you're hitting tells you how to fix it.

StateCauseWhat you seeFix
LockedThe feature isn't part of your plan.A "feature locked" overlay (where one exists) or a blocked action, with an upgrade prompt.Upgrade to a plan that includes the feature.
LimitedThe feature is included but you've reached its quota.The feature works, but the Create / Add action shows a "Limit reached" notice.Upgrade for a higher quota, or free up usage.

A locked feature requires a plan change. A limited feature can often be resolved without upgrading — by deleting or archiving something you no longer need. See Usage Limits & Quotas.


Plan-Gated Features

These are the six features the platform can turn on or off per plan. The exact plan each one belongs to is shown on the Compare Plans page.

FeatureWhat it unlocksWhere it appears
Custom DomainConnecting your own domain to a site.Site dashboard → Domains tab (Custom Domain Locked overlay).
AI AssistantThe AI copilot, AI-guided editing, and AI site generation.Dashboard AI copilot, the editor's AI panel, and the "Generate with AI" site flow. Hidden/disabled rather than shown behind a lock overlay.
Webhooks & APIProgrammatic REST API access and outbound webhooks.Dashboard → API & Webhooks (locked overlay titled "API & Webhooks").
Custom ScriptsInjecting custom header/footer <script> code, and installing third-party apps that inject custom code (e.g. Mailchimp, Google Reviews, Calendly).Site dashboard → Integrations, and blocked at install time for code-injecting apps.
App MarketplaceBrowsing and installing any app from the App Marketplace.Site dashboard → Apps tab (App Marketplace Locked overlay). This is the broader gate — installing a code-injecting app also requires Custom Scripts.
Site Export & DownloadExporting a site's pages/assets for download, and importing an exported site.Site dashboard, export/download actions. Hidden/disabled rather than shown behind a lock overlay.

When a feature is locked, previously saved configuration is preserved but inactive. For example, custom scripts you added on a higher plan are kept but stop running after a plan change, and start working again the moment you upgrade.


How Access Is Granted

A feature is usable only when two conditions are both met:

  1. Your plan includes it — this is the workspace-wide gate set by the Owner's plan.
  2. Your role permits it — once unlocked, your workspace or site role decides what you can do with it.

This means access is inherited from the plan, then scoped by role. A higher plan never overrides role restrictions: a Viewer on the top plan still can't publish, and an Editor on a basic plan still can't use a feature that plan doesn't include.


What to Do When a Feature Is Locked

  • If you're an Owner: open Compare Plans and upgrade to a plan that includes the feature. It unlocks immediately for every workspace you own.
  • If you're an Editor or Viewer: you can't change billing. Ask a workspace Owner to upgrade. Once they do, the feature unlocks for you automatically — no further action needed on your part.