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
  • How entitlement checks work
  • Use cases
  • How can teams use Schematic feature management
Using Feature Flags

Feature Management Overview

Was this page helpful?
Previous

Flags

Next
Built with

Feature Management in Schematic enables you to control how product features are rolled out, accessed by end customers, and monetized. Unlike traditional feature management tools, Schematic is purpose-built with billing in mind, so feature access can be tied directly to a company’s plan and any other policy set up in Schematic (e.g. add ons, overrides, or individual targeting).

An entitlement is the right to use a feature—defined by the relationship between a plan (or add on) and that feature. When you check whether a company has access to a feature, you’re evaluating their entitlements (and any overrides or targeting rules). Entitlements can be boolean (on/off), limited by traits, or metered by usage.

Feature Management Overview

How entitlement checks work

When your app calls check(company, feature) (via the API or an SDK), Schematic combines the company’s plan entitlement with any company-specific overrides and takes the most generous of those values. If that doesn’t resolve to a result, it falls back to global rules (e.g. trait or segment-based). If nothing matches, the feature is disabled by default. The diagram below shows this flow.

How an entitlement check works

Use cases

  • Rollout new features: Rollout gradually to a small cohort to mitigate risk or to gather feedback.
  • Line up access with subscriptions: Ensure customers only see features tied to their subscription plans or usage limits.
  • Manage exceptions: Selectively enable or disable features for individual customers.
  • Drive upgrades and renewals: Enable feature trials or time-limited overrides.
  • Simplify billing implementation: Eliminate the need for custom code by linking feature flags directly to billing.

How can teams use Schematic feature management

  • Engineers: Replace homegrown feature flag or metering logic and get an out of the box admin panel to manage them.
  • Product Managers: Get fine-grained control over how much and which features are available to different customer segments.
  • GTM Teams: Grant plan and feature trials to close deals and drive upsell.