FeatBit

Customer & Role Targeting

Give the right customers the first look.

A customer asks for a new reporting workspace. Their admins need to try it; members and other accounts need a familiar day. Combine account and role conditions to give the pilot a clear boundary.

Try FeatBit See the solution
CUSTOMER ACCOUNTADMINMEMBER

A practical walkthrough with reporting-workspace

The story · A reporting workspace, one customer at a time

Northstar asked for a new workspace. Only its admins need the first look.

Imagine a SaaS team building a reporting workspace for Northstar. The code is ready, but a fiscal-calendar edge case still needs real-world validation. A company-wide launch would turn one customer's pilot into everyone's problem.

Illustrative scenario · Real product configuration

Inside FeatBit · 3 steps

Open the workspace to the right admins in three steps.

Keep the existing experience as the baseline, configure the pilot and its serving variation, then review the result.

  1. 01Step 01 / 03

    Keep the existing workspace as the baseline.

    Start with a safe answer for everyone outside the pilot. In reporting-workspace, both the default ON rule and the OFF variation return Existing workspace.

    Default ON
    Existing workspace
    Flag OFF
    Existing workspace

    Members and other customers keep the experience they already use.

    Inside FeatBitLive app · Demo
    Swipe to inspect
    Targeting → Default rule

    Everyone, initially

    Existing workspace

    Start with a stable default

  2. 02Step 02 / 03

    Require the customer AND the role.

    Add the Northstar admins pilot rule with customerId = northstar AND role = admin. Set Serve to New workspace so users matching both conditions receive the candidate.

    customerId equals
    northstar
    AND role equals
    admin
    Serve
    New workspace

    A Northstar member or an admin at another account does not match the pilot.

    Inside FeatBitLive app · Demo
    Swipe to inspect
    Targeting → Northstar admins pilot → Conditions and Serve

    Northstar admins

    New workspace

    customerId = northstar AND role = admin → Serve New workspace

  3. 03Step 03 / 03

    Review and validate the pilot.

    Review that the pilot rule serves New workspace, then save. Check one matching admin and two non-matching users before inviting the pilot to validate the calendar workflow.

    Rule serves
    New workspace
    Check
    Admin · member · another account

    Expand after the pilot validates the workflow; use the existing workspace if it fails.

    Inside FeatBitLive app · Demo
    Swipe to inspect
    Targeting → Review the pilot change

    Matching admin

    New workspace

    The candidate reaches the selected audience

The next decision

Expand the audience after the pilot answers the question.

Check an admin and a member at Northstar, plus an admin at another account. Confirm the calendar workflow, then decide which customer or role should be next.

Build your own release in FeatBit

Targeting works alongside authorization

Keep permission checks in your application. A feature flag chooses an experience; your backend still decides whether the user can access data or perform an action.

From idea to implementation

Build your release path.

Configure targeting rulesBuild reusable customer segmentsExplore feature release management

Keep the release moving.

All solutions

Segment-Based Releases

Try a search rewrite with an opt-in beta or a regional pilot. Use the same limited audience across related feature flags.

Progressive Rollouts

Start an AI-assisted checkout with a small canary. Review errors and completion before more users receive the candidate.

Scheduled Releases

Deploy AI-assisted changes early, then schedule a reviewed pilot for a time when monitoring and recovery owners are ready.