Working · 2026-11PrimaryExpansionBilling

In-product seat requests with admin approval rules

Members ask for a paid seat from inside the product at the moment they need a paid feature, and the admin picks a rule: approve each request by hand, fill it from spare seats, or approve everything and buy seats as needed.

Also called: seat upgrade requests, auto-approve seats

Claim and evidence

The claimAuto-approve seats : All seat upgrade requests are automatically granted. If there are no seats available, a new seat will be purchased.

Figma · help.figma.com · undated

What the numbers show

No published number for this tactic has passed our word-for-word check yet, so there is no chart.

Why it works

Diagram, not data
Member hits apaid featureRequests aseat in theproductAuto-approve:seat bought ifneededManual reviewby the adminProrated onthe nextinvoice
Member hits a paid featureRequests a seat in the productAuto-approve:seat bought ifneededManual reviewby the adminProrated on the next invoice

Seat growth starts with the user who hits the paywall, so expansion does not wait for a sales cycle or a budget meeting. The admin rule sets how much friction sits between that demand and a new billed seat: auto-approval turns demand straight into revenue, manual approval trades some growth for budget control and fewer billing disputes.

How to run it

  1. Add a 'request upgrade' action wherever a free or lower seat hits a paid feature
  2. Route requests to the right admin (team, org or billing-group level)
  3. Offer per-seat-type approval rules: manual, use spare seats first, or auto-approve and purchase
  4. Pick a safe default and show it clearly in billing settings
  5. Notify requester and admin of the outcome and prorate new seats on the next invoice

Before / after

Before
This feature needs a paid seat
Ask your admin
Locked feature with no way forward
After
This feature needs a paid seat
Why do you need it?
Request upgrade
Your admin's approval setting applies
Request in place, admin rule decides

Generalised wireframe of the pattern, not a copy of any company's screen.

Ways to run it

Design options to test, not promised results.

  1. Option ASpare seats first

    Grant requests automatically only when a pre-purchased seat is free, Figma's default.

  2. Option BAuto-approve and purchase

    Grant every request and buy a new seat when none is free, as Figma offers to admins.

  3. Option CManual approval

    Route each request to the right admin for a decision, trading some growth for budget control.

Dated examples

  1. —

    Figma

    Admins on Professional, Organization and Enterprise plans choose per seat type between manual approval, auto-granting only when a pre-purchased seat is free (the default), or auto-approval that buys a new seat when none is free; enterprise license agreements default to auto-approve.

    “Auto-approve seats : All seat upgrade requests are automatically granted. If there are no seats available, a new seat will be purchased.”
    ✓ quote checked word-for-word on the page

    help.figma.com · undated

Does it still work?

Workingas of 2026-11

Described as current behaviour in Figma's live help center; no lift figures published. source

Risks

  • Auto-approval can produce surprise invoices and refund requests
  • Admins who never review the default may feel tricked
  • Manual approval queues can stall users and push them back to free tools

Sources

  1. help.figma.com · Figma Learn - Help Center · undated
    “Members or guests can make seat requests . As admin, you can use seat approval settings to automatically manage these new seat requests.”
    ✓ quote checked word-for-word on the page

Change log

  • 2026-11-20 — harvest v0.1 (pass2-expansion-ops)