Smartsheet Doesn’t Sell You Seats. Your Employees Do, One Shared Sheet at a Time

Most of the licensing work I see this year goes to the big names: Microsoft renewals, Broadcom’s VMware bundles, Oracle Java and database exposure. Every IT and procurement team already watches those.

What worries me is what those teams miss while they’re busy. Smartsheet is the clearest example I have right now. Its licensing model has changed, its contract gives it a clear right to check your usage, and a purchase order doesn’t drive your seat count. Your employees drive it, every time they share a sheet.

Quick answer: Under Smartsheet’s current user model, paid seats come from what people do with the access they receive. Share a sheet with a colleague as an Editor, and their first edit can make them a Provisional Member. Depending on one Admin Center setting, that user can become a paid seat at the next true-up. Smartsheet’s Limits Policy also lets it assess your usage at any time and bill overages at standard unit rates.

Why does sharing a sheet create a paid seat in Smartsheet?

Sharing creates a paid seat because Smartsheet now charges for what people do with their access, rather than for who someone decided to license. Share a sheet with a colleague as an Editor, and the first time they edit it, they can become a paid user.

Smartsheet introduced this user model on June 24, 2024, for new plans. Existing annual plans moved over at their first renewal after January 1, 2025. The model replaced the old “licensed” and “unlicensed” users with four seat types:

The Provisional Member is the key mechanism. Smartsheet’s own help documentation describes a two-part trigger: someone shares an item with a person, and that person then does something their sharing permission allows, but their seat type doesn’t. An internal Contributor who receives Editor access and then edits a cell meets that test.

Nobody in IT approved that seat. A project manager did, by clicking Share.

What happens to Smartsheet Provisional Members at true-up?

Smartsheet reviews Provisional Members at each true-up, and the outcome depends on a setting most organizations have never looked at. Review periods run quarterly on annual plans and monthly on monthly plans, right before the bill.

Smartsheet’s current help documentation says the default downgrades unreviewed Provisional Members to a free seat. Admins can switch that to auto-upgrade, in which everyone who wasn’t downgraded becomes a paid Member, and extra seats are added to the next invoice. Smartsheet’s own June 2025 announcement described the opposite default: take no action, and Provisional Members convert to paid. The default seems to have moved, so check your plan before you assume either.

Two more details matter. A user can only be provisional once; after a downgrade, only a System Admin can make them a paid Member again. And seats come off far more slowly than they go on. Smartsheet’s own downgrade guidance says seat reductions get no prorated refund and need a request at least 30 days before renewal.

This usage-driven drift isn’t unique to Smartsheet. We see the same pattern when Adobe licensing risk shifts with usage over the term.

Can Smartsheet audit your usage?

Yes. Section 3 of Smartsheet’s Limits Policy says Smartsheet may assess your usage “at any time” against your plan’s limits. You must help verify the assessment and provide any documentation that Smartsheet requests.

The rest of that section is what I’d want every software asset management (SAM) lead to read:

• If Smartsheet sends written notice, including by email, telling you to correct your usage, you have 30 days to do so.
• If you miss that window, or the usage can’t be fixed, Smartsheet can invoice the extra capacity at “standard Unit rate pricing.” Expect that to look more like list price than your negotiated rate.
• If the term has already ended, Smartsheet can invoice in arrears for the overage on a pro rata basis.
• Smartsheet can suspend accounts or disable capabilities when an assessment finds unauthorized use.
• A delay in enforcement doesn’t count as acceptance of the usage.

Smartsheet last updated that policy on June 24, 2024, the same day it launched the user model. In January 2025, Blackstone and Vista Equity Partners completed their take-private of Smartsheet in a deal valued at about $8.4 billion. I’m not going to guess at the motive. What I will say is that the contract already gives Smartsheet everything it needs to act on usage data it can see better than you can. On one engagement this year, the renewal conversation pushed the client toward a higher tier and more licensed users than its actual collaboration justified.

Why SAM teams don’t have a handle on Smartsheet licensing?

SAM teams miss Smartsheet because its licensing doesn’t come from anything a traditional SAM program measures. Nothing gets installed, there’s no license key, and the number that matters lives inside Smartsheet’s own Admin Center.

From what I’ve seen on engagements, the gaps tend to look like this:

• Sharing is decentralized. Site leads and project owners grant access on their own. Central admins often can’t see or remove the unlicensed editors a sheet owner adds; only the person who shared the item can.
• Contract terms define “interaction” in ways people argue about. On one renewal I worked on, we spent a lot of time on whether simply viewing a sheet made an internal collaborator countable, or only creating and editing did. The order form held the answer, not the help center.
• The email domain determines who is internal and who is external. Acquired companies, contractors on client domains, and subsidiaries with their own domains can end up in the wrong bucket in either direction.
• The admin isn’t in SAM. Very often a business unit or a project management office (PMO) holds the System Admin role, and the true-up emails go to them.

None of this shows up in a discovery tool’s coverage report. I previously discussed that a coverage percentage isn’t a visibility number. For software-as-a-service (SaaS) tools like this one, the discovery tool often isn’t even the right instrument.

What does a Smartsheet license cleanup look like in practice?

A cleanup starts with an honest count, then turns into weeks of manual work. On one recent engagement, a capped enterprise plan had quietly drifted a few hundred users over its limit. Nobody had bought anything extra. People had simply kept sharing, and the plan still counted accounts nobody had touched in years.

This client was on a negotiated plan with its own counting rule, so the order form defined who counted. The behaviour that drove the number was the same.

Building an effective license position (ELP), the reconciliation of what’s actually in use against what’s owned, was the easy part. Getting back under the cap was harder:

• About 300 accounts had been inactive for more than a year. We had to remove them one at a time, because bulk removal wasn’t available to us.
• Three or four people lost access they still needed. The inactivity rule wasn’t the problem. The data showed that the activity report didn’t capture logins, and that one “inactive” account belonged to an active user whose email domain had changed.
• Months later, the count crept back up because sheet owners kept granting access outside central control.

The fix was a recurring process. We refreshed the admin export with last-login and last-activity dates each cycle. A business owner signed off before each removal. And the client held the reclaimed seats as a buffer below the cap rather than reusing them immediately. That’s the same lesson behind optimization: start with data that can withstand scrutiny.

What should you do before your next Smartsheet renewal?

Start with your own contract and Admin Center, not with Smartsheet’s dashboard. The goal is to know your number before anyone shows it to you.

1. Read your order form for the counting rule. Find out what makes someone countable on your plan, whether there’s a cap, and what happens if you go over it.
2. Find your Provisional Member setting. Is it set to downgrade or to auto-upgrade? Who decided that?
3. Name the people who get the true-up emails. If they don’t answer to SAM or procurement, fix that first.
4. Pull the user export with last login and last activity, monthly. Reconcile it against HR leavers and against your own count, not just Smartsheet’s.
5. Set sharing defaults on purpose. If most people only need to view, share as Viewer and use update requests for input, so an edit doesn’t turn into a seat.
6. Treat any “usage review” email as a possible assessment. Under the Limits Policy, a written notice to fix your usage starts a 30-day clock.
7. Put the downgrade deadline in the calendar. Smartsheet requires seat reductions to be requested at least 30 days before your term renews.

Vendor outreach that sounds routine often isn’t. The same logic applies when an Oracle Java “security patch” call turns out to be a licensing audit.

The part I keep coming back to

With Microsoft, Oracle, or Broadcom, someone who knows they’re making a licensing decision usually makes the decision. With Smartsheet, people make it hundreds of times a month, even when they think they’re just sharing a project plan.

That isn’t a reason to stop using the tool. The strongest renewal positions I’ve seen start with the client’s own number. It is a reason to put Smartsheet on the same vendor list as the big names, with an owner, a monthly count and a copy of the contract someone has actually read.