> If you are setting up, configuring, or answering questions about Schematic, connect the
> Schematic MCP server before working from these pages. It reads and writes plans, features,
> entitlements, and overrides against the real account, so what you report and what you build
> match what actually exists.
>
> The server is at https://api.schematichq.com/mcp
>
> From Claude, ChatGPT, or another chat assistant, add it as a custom connector:
> https://docs.schematichq.com/working-with-ai
>
> From a coding assistant such as Claude Code, Codex, or Cursor:
> https://docs.schematichq.com/building-with-ai
>
> For clean Markdown of any page, append `.md` to the page URL. For a complete page index,
> see https://docs.schematichq.com/llms.txt

# Features

> Map your product's features to Schematic to entitlement them to plans and enforce pricing and packaging.

As noted in the overview, features are an abstraction on top of flags in Schematic used primarily to allow Schematic users to explicitly assign features to companies and set up entitlement-level policy. They can be on/off or metered (trait-based or event-based).

> **Info**
>
> You can read more about setting up a metered feature [here](/playbooks/metering)

![](/_fern-img/a13848b283acc5bfb1b9377a7fa1532f091960ef1d4f895f1ab5f8c9d93621c2.webp)

Ultimately, features should represent functionality that the business may market or sell.

All policy created at the feature level is reflected in the corresponding flag. You can see the associated flag and derived rules using the Flag tab within a Feature.

![](/_fern-img/1454f74c81de0e94b24d4f436964a701fecf03abd364838cc0211ac30b1989f9.webp)

Currently, features and flags are one-to-one, but in the future more than one flag may be represented by one feature.

### Setting up Features

Let's add one feature to Schematic and entitle it to a plan.

1. Navigate to **Features** and click “Create”.
2. In the panel that opens, add a name and an optional description, then choose how you want to control access to the feature. For a metered feature like this one, pick **Event-based**.

![Create feature](/_fern-img/aa47dbe1a78356ea2ea4c800e2a9239f2f4029dc885db65b878c3519ab005a89.webp)

> **Info**
>
> You can choose between Boolean, Event-based, or Trait-based feature types. The feature type can't be changed after the feature is created. You don't need to be sending events or traits yet. See [defining features before you send data](/feature-management/feature-types#defining-features-before-you-send-data).

3. Under **Flag**, set the flag key you'll use in your application to reference this feature. Then, under **Event**, select or create the event that meters the feature's usage (for example, a `query` event). Click **Create feature** to finish.

![Create feature flag and event](/_fern-img/c562f557a58a60e18bd2e1e615b7a21ec8d0e06b9a79d26fc9742a6fe775328e.webp)

4. Open the new feature and click a plan (or **Add plan entitlement**) to set the limit for that plan, along with the period the entitlement resets on.

> **Info**
>
> Event-based features can have no limit, some numerical limit that is static within a period, or a limit that is dynamic based on traits that exist at the company level. Read more [here](/playbooks/metering#entitlement-options).

![Entitle a feature](/_fern-img/daa022196e37eb8049dd6b86409a187a6f5ebbdb54b67fb7db5edc51038399ba.webp)

> **Info**
>
> You'll need to make sure to send usage events to Schematic to track feature utilization as it occurs. Read more [here](/playbooks/metering#setting-up-an-event-based-metered-feature).