> ## Documentation Index
> Fetch the complete documentation index at: https://partner-docs.nuwebgroup.com/llms.txt
> Use this file to discover all available pages before exploring further.
# Feature Flags & Limitations
> Enable, disable, and configure platform features and restrictions for companies.
## Overview
Feature flags control which platform capabilities are available to a company. They are managed from the company edit page in the hub, where features are organised into groups (Events, Shop, Websites, EPOS, Fees, System, Integrations, and more).
There are two types of flags:
* **Capabilities** — enable features or workflows (e.g. seating plans, access control, donations).
* **Limitations** — restrict or disable specific functionality (e.g. disallow box office mode, block editing historic events).
Some features can be toggled by company administrators themselves (**self-service**), while others can only be configured by platform administrators in the hub (**hub-operated**).
## Reseller Funnelling
Before a feature can be enabled on a company, it must first be enabled on the reseller that owns the company. The reseller acts as a funnel — only features that are active on the reseller will appear as available options when configuring a company or creating a plan under that reseller.
This funnelling pattern applies beyond feature flags. Currencies, countries, languages, and [payment gateways](/topics/gateway-settings) all work the same way: they must be enabled on the reseller before they can be assigned to any of its companies.
Enabling a feature on the reseller does not enable it on any company — it simply makes the feature available for assignment.
## How Features Are Assigned to Companies
Once a feature is available via the reseller, it can be assigned to a company in two ways:
**Directly** — toggle individual features on the company edit page. This gives full control over exactly which features a company has access to.
**Via a plan** — assign the company to a [plan](/topics/plans-and-packages) that has a predefined set of features. When a plan is assigned, its features are synced to the company automatically. A plan's available features are also funnelled through its reseller — only features the reseller has enabled can be added to the plan. Features assigned via a plan appear as read-only on the company edit page — removing them triggers a confirmation warning since it means deviating from the plan.
## Feature Modes
Some features support multiple modes, configured via a context selector that appears when the feature is enabled.
| Feature | Modes |
| --------------------------- | --------------------------------------- |
| **Seating plans** | Small plans only, Small and large plans |
| **Donations** | Donations only, Donations with Gift Aid |
| **Seating plan holds** | Seats only, Seats + general admissions |
| **Account balance refunds** | Admin only, Admin and self-serve |
| **Resale** | API only, Web only, Web and API |
| **Refund Protect Group** | Standard, Anonymous |
## Conflicts and Requirements
Some features depend on other features being enabled first, and some features are mutually exclusive.
The feature flag configuration interface now highlights conflicts, prerequisites, and incompatibilities in real time as you toggle features. When you enable a feature that requires another feature, the prerequisite is visually indicated. When you attempt to enable a feature that conflicts with an already-active feature, the collision is surfaced immediately — preventing invalid configurations before they are saved.
**Requirements** — the feature cannot be enabled until its prerequisites are active. For example:
* **Seating plan holds** requires **Seating plans**
* **Lead capture** requires **Access control**
* **Custom currencies** requires **EPOS** and **Online account balances**
* **Gift vouchers** requires **Split payments** and **Online account balances**
* **Rolled up fees**, **Dynamic fees**, **Tiered fees**, and **Fee hierarchy control** all require **Custom fees**
**Conflicts** — only one of the conflicting features can be active at a time. For example:
* **GEA integration** conflicts with **Tawakkalna integration**
* **Szamlazz integration** conflicts with **Conditional tax bands**
* **Refund Protect Group** conflicts with **Manual Refund Protection**
* **All-in pricing** conflicts with **Conditional tax bands**
## Pre-Release Features
Features marked as pre-release (beta) are only visible to super users in the hub. These features are in active development and may change or be removed. They are indicated with a beta badge in both the hub and in the reference tables below.
***
## Capabilities
### Self-Service
These features can be enabled or disabled by company administrators from their own settings.
| Feature | Description |
| --------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Allow item approval before payment** | Companies can mark non-guest list items as requiring approval. Customers cannot pay for their order until it has been approved. |
| **Extended customer country selection** | Customers can select any country for their address, rather than just the countries enabled for the company. |
| **Stay22** | Companies can display the [Stay22 hotel concierge widget](https://docs.nuwebgroup.com/core-platform/integrations/stay22) alongside events to offer nearby accommodation to customers. |
### Hub-Operated
These features require a platform administrator to configure.
| Feature | Description |
| ------------------------------------------------------------------------------------------------------------------------------------------ | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Event time slots** | Allows events to add tickets to specific time slots. |
| **Online billing** | Allows companies to view invoices. |
| **GEA integration** | Event information, cancellations and ticket sales are pushed to the GEA database via API. **Conflicts with:** Tawakkalna integration |
| **Seating plans** | Allows users to create seating plans for events. **Modes:** Small plans only · Small and large plans |
| **Product sales** | Companies can create physical products and attach them to events. |
| **Guest list sales** | Companies can create guest list items and attach them to events. |
| **Event streams** | Events can be set as streaming and host online streams. |
| **Event teams/groups** | Events can allow team/group entries. |
| **Access control** | Enables access control features including zone scanning and zones. |
| **Website integration** | Enables the website integration tools. |
| **Data imports** | Enables the data import tools. |
| **Internal questions** | Companies can assign internal questions to events. |
| **Donations** | Companies can present site-wide or event-specific donation options during checkout. **Modes:** Donations only · Donations with Gift Aid |
| **Fundraising** | Companies can enable fundraising mode for specific events. |
| **Season tickets** | Companies can create season tickets and attach them to multiple events for entry. |
| **Tawakkalna integration** | Event information, tickets and venue data are pushed to Tawakkalna via API. **Conflicts with:** GEA integration |
| **Event media** | Companies can create custom event media (printable tickets and wallet passes) and assign them to item types. |
| **Self manage features** | Gives companies control over self-service feature flags from their admin settings. |
| **EPOS** | Allows companies to set up an EPOS solution with multiple vendors and product sales through the EPOS mobile app. |
| **Articles** | Companies can create and publish articles and configure article types and blocks. **Conflicts with:** Disallow the ability to view shop from admin |
| **Template blocks** | Companies can add pre-designed templated blocks to event pages, article pages, and custom pages. **Conflicts with:** Disallow the ability to view shop from admin |
| **API token management** | Unlocks the API settings section for generating API tokens and managing access. Disabling this does not disable existing API access. |
| **Form builder** | Companies can create and attach data capture questions to forms. **Conflicts with:** Disallow the ability to view shop from admin |
| **Sale item groups** | Allows event organisers to create sale item groups for organising tickets. |
| **Refund cancellation fees** | Companies can set a fixed cancellation fee per item when refunding orders. |
| **Assign events to users** | Allows assigning additional events to admin users outside of their visibility groups. |
| **Invoice payments in shop** | Enables invoice payments as a checkout method in the shop. |
| **Seating plan holds** | Companies can manage seating holds for restricting sales on specific groups of seats. **Modes:** Seats only · Seats + general admissions. **Requires:** Seating plans |
| **Szamlazz integration** | Tax receipts and invoices are created via Szamlazz, complying with Hungarian law. **Conflicts with:** Conditional tax bands |
| **Access codes** | Companies can create access codes that restrict item sales to customers who enter the correct code. |
| **Can edit billing details** | Company billing details are editable from admin. |
| **Attach PDF to tax receipt email** | A PDF is attached to the tax receipt email with the same contents as the email. |
| **Misr SMS** | Companies can use their Misr SMS account for order approval/rejection notifications. |
| **Include other items** | Companies can include other sale items when editing tickets, season tickets, and products. |
| **DTCM** | Company event data is automatically synced with DTCM performance data. |
| **Event level default currency** | Companies can override the company default currency per event. |
| **XE integration** | Sale item pricing for each currency is automatically set by converting the default currency price using today's exchange rate. |
| **Custom currencies** Beta | Companies can create their own custom token currencies. **Requires:** EPOS, Online account balances |
| **Advanced tax controls** | Companies can configure advanced tax settings including pricing display and tax calculations for invoices. |
| **System defaults** | Companies can customise default fields/settings and create alternate templates for admin forms. |
| **Conditional tax bands** | Companies can create dynamic tax bands applied at checkout based on the purchaser's country. **Conflicts with:** Szamlazz integration |
| **Custom fees** | Companies can create custom fees (order level, event level, sale item level) that are automatically applied to baskets. |
| **Instant access orders** | When invoice payment is selected, customers can access tickets and downloadable items immediately after completing their reservation, before paying. |
| **Fees can attract discounts** | Discount codes can discount the reseller and processing fees of a sale item. |
| **Webhooks** | Companies can configure automated HTTP callbacks triggered by events such as completed orders. |
| **Seating plan best available seats** | Enables focal point positioning within seating plans for best available seat suggestions. |
| **Lead capture** | Companies can create exhibitors for use alongside access control. **Requires:** Access control |
| **Order distribution** | Customers can distribute selected order items via a unique code, QR code, or URL. |
| **Split payments** | Box office users can process orders with multiple payment methods by splitting across transactions. |
| **Fulfilment fees** | Order fulfilment methods and fees can be set up and applied to orders. |
| **Online account balances** | Customers can use an account balance to purchase tickets online or products via EPOS. |
| **High frequency scheduled reports** | Reports can be generated and sent at shorter intervals, such as hourly. |
| **Deposit payments** | Customers can place deposits on reservations and pay the balance later, according to configured rules. |
| **Rolled up fees** Beta | Fee items can be grouped and displayed as a single line in the basket summary while remaining individual items on the order. **Requires:** Custom fees |
| **Account balance refunds** | Enables refunds to account balance. **Modes:** Admin only · Admin and self-serve. **Requires:** Online account balances |
| **Net price discounts** | Fixed discount codes can be applied before tax using the net item price. |
| **Named ticket holders** | A name can be set on tickets without transferring the ticket. |
| **Gift vouchers** | Gift vouchers can be managed, purchased, and redeemed. **Requires:** Split payments, Online account balances |
| **Event sales dashboards** | Real-time sales dashboards are available per event. |
| **Customer groups** | Customer groups can be created to restrict purchases and discounts to certain customers. |
| **Box Office Kiosk Mode** | Kiosk is available as a sales channel for use in kiosk mode. |
| **Dynamic fees** Beta | Custom fees can include a dynamic, percentage-based element calculated from basket or item totals. **Requires:** Custom fees |
| **Fee hierarchy control** Beta | Fees assigned to multiple inventory sources can apply only the most specific fee in the hierarchy. **Requires:** Custom fees |
| **Tiered fees** Beta | Companies can specify pricing tiers for fees based on item or order value. **Requires:** Custom fees |
| **Tracking pixels** | Companies can enable tracking pixels for individual events. Enabling this forces global basket to be disabled. |
| **Refund Protect Group Integration** | Enables the Protect Group integration for refund protection during checkout. **Modes:** Standard · Anonymous. **Conflicts with:** Manual Refund Protection |
| **Automatic event reminder emails** Beta | Companies can send reminder emails a set time before an event. |
| **White label app: Access Control** Beta | Enables white label access control app for the reseller/company. |
| **White label app: Box Office** Beta | Enables white label box office app for the reseller/company. |
| **White label app: EPOS** Beta | Enables white label EPOS app for the reseller/company. |
| **All-in pricing** Beta | Customers see the all-inclusive price including fees and taxes throughout the shop. **Conflicts with:** Conditional tax bands |
| **Event sale periods** Beta | Pre-sale and general sale periods can be defined for events, with dynamic event page content. |
| **Deferred ticket download** Beta | Ticket downloads can be deferred until a set time before the event starts. |
| **Basket links** Beta | Customers can enter checkout using a link generated for a basket created through the API. |
| **Report publishing** | Scheduled reports can be published to user-defined data endpoints such as S3 buckets. |
| **Resale** Beta | Enables ticket resale. **Modes:** API only · Web only · Web and API. **Requires:** Online account balances, Split payments |
| **Order modification** Beta | Orders can be modified after checkout. Increases require additional payment; reductions are refunded to account balance. **Requires:** Online account balances, Split payments |
| **3D Digital Venue** Beta | Venues can provide 3D Digital Venue details for view-from-seat in the item selector and checkout. |
| **Manual Refund Protection** Beta | Enables custom opt-in refund protection fees for ticket buyers. **Conflicts with:** Refund Protect Group Integration |
| **Merge customers** Beta | Admin users can merge duplicate customers, consolidating purchases, data capture, authentication methods, and profile information into a single record. |
| **GTM Advanced Consent Mode** Beta | Google Tag Manager is included regardless of cookie consent status. |
| **Secure QR codes** Beta | Events can use secure (rotating/dynamic) barcodes for access control. Also enables the new wallet UI for customer tickets. |
| **Dynamic pricing** | Companies can enable [dynamic pricing](https://docs.nuwebgroup.com/core-platform/integrations/dynamic-pricing) at the event level so tickets are automatically adjusted in real time based on demand. Per-ticket configuration (opt-in tickets, pricing models, min/max bounds) is managed through an embedded third-party portal accessed from the event dashboard. Standard unseated events only. |
***
## Limitations
Limitations are restrictions. When a limitation is **enabled**, the specific functionality is **blocked** or **hidden** for the company.
### Self-Service
These restrictions can be toggled by company administrators.
| Limitation | Effect |
| ------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------- |
| **Force profile questions on checkout** | Profile questions are asked every checkout, even if the data has already been provided. |
| **Disallow profile changes** | Customers can only edit profile fields during checkout. |
| **Disallow data capture editing** | Customers cannot edit their data capture answers outside of checkout. |
| **Disable instant checkout** | Hides the instant checkout button from box office. |
| **Force customers to login/register before adding items to basket** | The "buy now" button is replaced with a login button for guest customers. |
| **Force customers to login/register before browsing the shop** | Unauthenticated customers are redirected to the login page. If SSO is enabled, they are redirected to the SSO provider. |
| **Disable sitemap generation** | The company's sitemap is not generated or served publicly. |
| **Disable schema JSON** | Schema JSON (json+ld) is suppressed within the shop. |
| **Disable customer feedback collection** | Disables all feedback widgets in customer experiences such as the checkout flow. |
### Hub-Enforced
These restrictions are applied by platform administrators and cannot be removed by the company.
| Limitation | Effect |
| ------------------------------------------------ | ------------------------------------------------------------------------------------------------------------ |
| **Block company access when invoice(s) overdue** | Companies are blocked from the system until overdue invoices are cleared. |
| **Disallow editing historic events** | Events past their end time are no longer editable. |
| **Disallow refunding historic events** | Events past their end time are no longer refundable. |
| **Disallow free items** | Free items cannot be created on events. |
| **Mandate organiser details** | Organiser details are mandatory for all events. |
| **Disallow box office mode** | Company users cannot access box office mode. |
| **Disable global event stock** | Hides global stock settings for event items. Stock can only be configured at the event level. |
| **Disable global epos stock** | Hides global stock settings for EPOS products. Stock can only be configured at the shop level. |
| **Disallow processing fees** | The company cannot set processing fees. |
| **Disallow reseller fees** | The company cannot set reseller fees. |
| **Disallow resell/assign existing items** | Companies cannot create sale items from existing items (except for season tickets and via event scheduling). |
| **Cannot amend Szamlazz credentials** | Company users cannot change their Szamlazz credentials once set. |
| **Disallow absorbing item fees** | The company cannot absorb processing or reseller fees into their prices. |
| **Disable usage metrics** | Platform usage data (feature frequency, user journeys) is not recorded. |
| **Disallow the ability to view shop from admin** | Removes options to view the shop from admin. |
| **Hide global system roles** | Company users cannot see global system roles (e.g. Box Office User, Scanning User). |
| **Disallow refunding reseller fees** | The company cannot refund the reseller fee portion of an item. |
| **Disable ticket shop** | The company's ticket shop is disabled. Child companies with global login disabled cannot be disabled. |
| **Disable Google Places** | Customer address lookups are disabled; customers must type their address manually. |