For AI agents: a documentation index is available at the root level at /llms.txt and /llms-full.txt. Append /llms.txt to any URL for a page-level index, or .md for the markdown version of any page.
SupportDashboard
Getting StartedAPI ReferenceRoadmapBlog
Getting StartedAPI ReferenceRoadmapBlog
  • Getting Started
    • Overview
    • What is Schematic?
    • Concepts
  • Using Schematic
    • Who Uses Schematic
  • Quickstart
    • Quickstart
    • Account Setup
    • Entitling a Feature
    • Tracking Usage
    • Components
    • Identifying Users
    • Setup the SDK
  • Using Feature Flags
    • Overview
    • Flags
    • Features
    • Tracking Feature Usage
    • Company Overrides
    • Feature Types
  • Building Your Catalog
    • Overview
    • Plans
    • Managing Company Plans
    • Configuring the Catalog
    • Add Ons
    • Trials
  • AI Tooling
    • For Developers
  • Setting Up Billing
    • Overview
    • Usage Based Billing Models
    • Seat Based Billing Models
    • Credit burndown
  • Using UI Components
    • Overview
  • Developer Resources
    • Concepts
    • Key Management
    • Environments
    • Entity Relationship Diagram
  • Production Readiness
    • Availability
    • Observability & Support
    • Security
  • Integrations
    • Segment Integration
    • Clerk Integration
    • WorkOS Integration
    • Salesforce Integration
    • Hubspot Integration
  • Playbooks
    • Overview
    • Creating a metered feature
    • Backfills and usage corrections
    • Rolling out beta functionality with Flags
    • Handling customer exceptions and feature trials
    • Automatically provision customers using Stripe
    • Build a slack webhook
LogoLogo
SupportDashboard
On this page
  • Setting up Features
Using Feature Flags

Features

Was this page helpful?
Previous

Tracking Feature Usage

Next
Built with

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).

You can read more about setting up a metered feature here

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.

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 modal, add a name, description, and pick the event-based feature type. Click “Continue”.

Create feature

You can choose between Boolean, Event-based, or Trait-based feature types.
  1. Define a flag key.
    1. You’ll use this key in your application to reference this feature.

Create feature 2

  1. Attach an event to the feature. Add the query event to meter the feature and measure feature usage (if it doesn’t exist already, create it).

Create feature 3

  1. Once the feature is created, click ”Add plan entitlement” to add an entitlement and specify the limit for Search Query for a given plan.
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.

Entitlement a Feature

You’ll need to make sure to send usage events to Schematic to track feature utilization as it occurs. Read more here.