Feature Planning

Use this page before enabling features or changing a workspace plan. The best first launch is usually the smallest useful feature set.

Feature Tokens And Effective Availability

A tenant-admin or super-admin reviews feature selection in the active workspace. Feature tokens are stable machine identifiers, not translated menu names. The minimum plan and automatic dependencies are:

Selected features are intersected with plan availability, then required dependencies are added. For example, selecting community or membership adds customers; neither automatically adds ecommerce. Check the effective set, automatically added dependencies, and plan-blocked selections before launch. Enabling a feature does not grant a role, publish content, or register customer OAuth clients. App implementation belongs in the domain task guides; use this page for operating scope and availability.

Plan Availability

Commerce and event ordinary email share a KST monthly pool: Free100, Starter1,000, Basic1,000, Pro3,000; Enterprise remains unlimited. Customer OTP, password reset and event cancellation are observed but excluded from ordinary limits and customer billing. Sandbox has one common 100-attempt monthly ceiling per generation, including essential email, with no external send or billing. Video is available on Starter, Basic, and Pro; live streaming is Enterprise-only.

Gallery items use images by default. For feed-style content or portfolios, each item can instead reference one video, in the same gallery order. Video items require the videos feature to be enabled and available on the workspace's current plan; they reuse the existing video upload, processing, and playback flow. Image galleries remain available on Free.

Paid Plan Allowances

Basic and Pro are the paid plans available for new subscriptions; beyond Pro, contact sales for Enterprise. Prices include VAT, and yearly billing equals ten months.

• API calls and ordinary email are monthly allowances on yearly billing too. Both reset on the first day of each KST calendar month, independent of the card billing date (subscription period).

Workspace-only and Live APIs remain available when API metering storage is uncertain. Without completeness evidence, first Enterprise monthly usage invoices are held, including apparently normal months. Existing invoices and flat subscription billing continue; missing quantities are never estimated for billing.

• Storage, documents, and webhooks are held amounts and do not reset monthly. 100GiB is 107,374,182,400 bytes.
• API calls count /api requests that send X-Publishable-Key. Requests without a key and CORS preflight (OPTIONS) are not counted; requests that fail while processing are. The request after the limit returns 429 usage_limit_exceeded. If the usage store is temporarily unreachable, Live allows the request and Sandbox rejects it, so the API limit is not a guaranteed cost cap.
• Storage warns at 100% of the limit and blocks uploads that add usage at the default 2x safety ceiling. Reading and deleting existing files keeps working.
• Exceeding a lower plan's limits never triggers automatic deletion, extra charges, or upgrades. While over a limit, new creates, sends, or uploads for that item can be restricted.
• Ten webhook registrations do not mean unlimited delivery or retries.

Feature Decisions

Dependencies

• Community depends on customer accounts.
• Membership requires customer accounts. Ecommerce is selected independently when you also need products and orders.
• Membership cannot be disabled while live or incomplete memberships or pending charges remain. If the feature becomes unavailable through another change, renewals stop, existing memberships end at the paid period boundary, and customers can still view or cancel their memberships. Turning the feature back on does not restart those renewals.
• An existing paying member keeps group benefits while renewal is unresolved for up to two hours after the paid period ends. A declined renewal, cancellation, revoked payment method, or refund ends this hold immediately. A past-due member does not receive this extra time; benefits already valid within the paid period keep their existing rule. Existing Checkout and Order prices stay fixed.
• Plan-blocked feature intent may be saved, but it is not effective until the plan allows it.
• Disabling unused features keeps navigation and readiness checks focused.

Console Menu Names

In Console, a tenant-admin or super-admin can use Settings → Menu display names to rename the active workspace's menus. The names also appear in collection headings, breadcrumbs, and Cmd+K. Menu names do not change field names, content document titles, URLs, menu order, or permissions. The Commerce Config and Branding · SEO · Business settings screens use their menu names as document headings and provide a link back to Settings.

For each menu, use one single-line name of up to 40 characters for every Console UI language. Leave a name blank or reset it to restore the default name in the selected UI language. Other workspace operators see the saved names.

Shared payment settings

Payment provider connections are available under Settings → Payments without turning on Ecommerce. tenant-admin operators can register provider configuration and manage credentials in the active workspace. Secrets are never shown after saving. Commerce market assignments are optional; an account with no markets is not selected for Commerce checkout. Toss configuration attestation and activation are available without Ecommerce. PortOne activation still requires an existing verified webhook route. Route reads and tenant-admin issue, attest, and revoke are available without Ecommerce; existing tenant and active-tenant permissions still apply. Whole-connection Commerce switching still requires Ecommerce. This does not enable a public Events payment API.

Next Actions

• Prepare non-commerce areas in Content Operations.
• Prepare sales workflows in Commerce Operations.
• Check blockers in Launch Readiness.

Customer accounts can be created through signup or authorized server integrations. Operators cannot create customers from the Admin Panel, including relationship fields; use the customer list to review existing accounts.

Customers with a local password can reauthenticate and withdraw their account. See Customer self-withdrawal for membership restrictions and retained history.

Membership administrators can review paid results that did not change a subscription in Console under Membership → Unapplied membership payments, or from the related membership and charge detail. Each retained row shows the charge, source (dispatch, webhook, or queryCharge), and reason. These rows are review evidence; refunds remain workspace-operated.

Workspace administrators can configure one embedded app with exact execution-role opt-in. Editors/viewers see only the authorized execution screen; the receiver must also opt in and enforce feature permissions. See Embedded Admin.

Ecommerce also includes workspace-defined, single-use customer benefit vouchers. Workspace servers issue, redeem, and void them; Customers view their own vouchers. In Console Customer detail, tenant-admins and tenant-editors can redeem available vouchers; tenant-admins can also void them.