lifecycle
Smartsheet license optimization: choosing the right seat type for every user
Under the User Subscription Model, Smartsheet stopped selling licenses in bundles and started asking a harder question every quarter: which of these people should actually be a paid Member?
That question has a deadline. Reconciliation periods run quarterly for annual plans and monthly for monthly plans, and each one hands you a list of Provisional Members to approve or downgrade. Approve everyone and you’re buying seats nobody needed. Downgrade the wrong person and you break a business process — because a downgraded user keeps their sharing permissions on paper while losing the ability to use them.
So license optimization here isn’t “find the unused seats.” It’s a per-person routing decision across four seat types.
The four seat types, and what each one costs you
| Seat type | Who it’s for | Can create? | Can edit content? | Cost |
|---|---|---|---|---|
| Member | Internal people who build or maintain work | Yes | Yes | Paid |
| Provisional Member | Anyone who took a qualifying action without a paid seat | Yes | Yes | Free for at least 30 days, then reconciled |
| Contributor | Internal people who consume others’ work | No | No | Free |
| Guest | External collaborators | No | Yes, per item permission | Free (Business plans and up) |
Two rows in that table do most of the damage in practice.
The Contributor row. This is the one admins get wrong: a Contributor cannot change the information in a sheet. Smartsheet’s own guidance spells out the trap — a user can hold Editor permissions on an item and still only have Contributor capabilities, so they see the sheet but can’t change anything in it. Seat type wins over item permission. If someone updates rows weekly, Contributor isn’t a cost saving; it’s an outage with a delay on it.
The Guest row. An external editor is free. If you’re paying for Members whose email domains don’t match your plan’s domains, that’s usually the fastest real saving on the list, and it costs nobody any capability.
The routing questions, in order
For each person on the reconciliation list, work down this list and stop at the first yes.
1. Do they own anything? A Contributor cannot own items on the plan, so anyone owning a sheet that’s still doing work needs a Member seat — full stop. This one also has the nastiest failure mode, which is the next section.
2. Do they edit content — rows, cells, values? Then Member (internal) or Guest (external). Not Contributor. Check update requests and form submissions rather than assuming, because those are the workflows where a well-meaning downgrade quietly stops a process a week later.
3. Are they external? Then Guest, at Editor or Commenter, and stop paying for them.
4. Do they only look at things? Contributor — free, and genuinely correct for the many people who just open dashboards and read reports. This is where most of the money is: across environments scanned, only about one in ten licensed users actually creates sheets.
5. No evidence of anything at all? Now you have a candidate for retiring the seat entirely rather than downgrading it — but read the next section first.
The trap: retiring a seat that owns things
Removing a user isn’t a clean accounting operation — their owned items don’t go away, and this is where license cleanup turns into a governance incident.
Transfer ownership before you remove the seat. Remove the user first and their items become abandoned; recovering them means working through the abandoned-items report in Admin Center — a worse job than the one you avoided. Transferred sheets land in a “Transferred from (username)” folder in the new owner’s directory, keep their sharing permissions and data, and anything already in a workspace stays put.
So the real prerequisite for any seat decision is knowing what each person owns. Smartsheet’s seat type report gives you seat type, admin access, permissions and activity per user — that’s the license side. It doesn’t tell you which of that person’s sheets are load-bearing, how recently each was used, or who else would know how they work. That’s the layer Smart Admin Studio’s owner mapping and institutional-knowledge risk discovery covers, so a downgrade decision is made against real dependency rather than a guess.
This mostly protects the quiet builders. The creators an admin already knows about are the loud ones, who ask for expansions and knock on IT’s door. Most of the real building is done by people who never trip an alert and never surface on a standard report — and on an activity-only view they can look like a downgrade candidate.
Don’t convert dormant sheets into a seat number
A lifecycle review will tell you that a lot of the environment is idle. In environments we’ve looked at, the large majority of sheets haven’t been touched in months, and roughly a fifth look like genuine lifecycle-review candidates. (Generalized from a real large-environment analysis; illustrative, not a guaranteed result for every environment.)
That’s a data-retention and archival finding, not a seat count. Sheets and seats don’t map one-to-one — one person can own hundreds of dormant sheets and still be your most essential Member — and an argument that slides from “most sheets are stale” to “we can cut seats” falls apart under the first serious question. Keep the two reviews adjacent and separate.
The optimization that isn’t cutting
Moving view-only people to Contributor and external editors to Guest frees real budget without removing anyone’s access — and that budget is usually best spent on the Members who are underusing what they already have.
In a large-environment scan, only a small fraction of sheets used the platform’s advanced capabilities at all. That’s not indifference; nobody showed those people what the platform does. Enablement and a few visible internal examples raise per-seat value faster than any deprovisioning exercise — and this is the version of the review that gets a licensing increase approved, because you can show what depends on the platform and what would break without it.
Before your next reconciliation period
Have three lists ready:
- Owners of load-bearing work — Members, non-negotiable, with a named successor for each.
- Consumers and externals — the Contributor and Guest conversions, which is where the savings actually are.
- True retirement candidates — no ownership, no editing, no access pattern — each with its ownership transfers already done.
None of that requires reading the contents of a sheet — ownership, structure and activity metadata answer all of it.
Reconciliation dates don’t wait. Get visibility today — no credit card, no sales call.
Smart Admin Studio is an independent product and is not affiliated with, endorsed by, or sponsored by Smartsheet Inc.
Stefan Quartemont
Co-Founder, Smart Admin Studio · President, QREW Tech
Stefan is Co-Founder of Smart Admin Studio and President of QREW Tech, which he founded in 2018 to advance the citizen-developer movement through no-code and low-code training, tooling, and consulting. He has spent years helping non-technical builders ship real business systems on platforms like Google AppSheet — and helping the organizations around them govern what gets built. He writes here about bringing visibility, ownership, and lifecycle discipline to sprawling low-code and Smartsheet environments without smothering the people doing the building.