No site selected

Settings

Packages

About this section: PackagesBundles customers can buy or unlock.

Purpose

A package is a named bundle of access (such as Public, VIP, or Live TV). Define them here once, then go to Site Assignments to choose which sites offer each package.

Key fields

  • Code: A short internal name like public, vip, or live_tv. Keep it stable.
  • Name and Kind: The customer-friendly name plus a tag you can use to group packages.
  • Parent Package: Used only to group related packages. It does NOT give people access to the parent.
  • Policy: The rules for what guests, members, and paying customers see.
  • Assignable: Turn this on if customers can buy this package directly.

Example

Create a Live TV package, attach a policy that gives guests a short preview, then enable it on the sites that should sell it.

Consequences

  • A package without a policy can group things but won't actually gate access.
  • Adding a parent package does not unlock the parent — use Grants for that.
  • A package only works on a site after you enable it in Site Assignments.

Add Access Package

PUBLIC is a real package row. Grants are explicit, not inferred from parent_package_id.

Stable lowercase/snake_case package identifier.
Operator-facing package label.
Open vocabulary; not yet a closed enum.
Closed package treatment. Leave empty for generic feed-driven packages.
Grouping parent only; grants are explicit.
Packages used as live truth should generally have a policy.
Positive decimal weight used for upsell ranking.
Archived packages remain for audit/history.