Smartsheet contributor vs viewer: what actually changed?

Why you still see the word viewer in Smartsheet

Because viewer means two different things, and only one of them went away. Smartsheet has seat types, which describe who someone is on your plan, and sharing permission levels, which describe what they can do on one particular sheet. Viewer used to be both. Now it is only the second one.

Smartsheet was explicit about this when the contributor seat shipped: there is no change to the viewer permission on sheets, reports, or dashboards. So if you share a sheet with someone as a viewer, that still works exactly as it did. What changed is the seat sitting underneath them. They are now a contributor at the account level, and a viewer on that specific sheet.

This is worth getting straight before you audit anything, because the two layers interact. Your seat type sets the ceiling on what you are allowed to do anywhere. Your sharing permission on a given item sets what you actually do there. A contributor shared as a commenter can comment. A contributor shared as an editor still cannot edit, because their seat does not permit it. The lower of the two always wins.

What can a contributor do without paying?

More than a viewer could, and the additions are the ones people complained about. Contributors are free users who can view anything shared with them, and when they are shared with commenter permissions they can also comment and add or delete attachments. They can download attachments on items they can see, and follow sheet activity to get notifications.

What they cannot do is create anything, edit content, or share items with other people. That boundary is the whole design. Free seats consume work, paid seats produce it.

That table is the clearest summary of the change anyone has published, including Smartsheet. Nine actions are identical between the old seat and the new one, and exactly two things are new: free commenting and free attachments. Nothing was taken away, which is why the transition needed no admin action and broke nothing.

Contributors are free on Pro, Business, and Enterprise plans. That last detail matters more than it looks, and it comes back in a moment when we get to external people.

Which Smartsheet seat covers which activity?

Four seat types exist now. Here is what each one allows, and what it costs you.

Guests are the one that needs a footnote. A guest is a free external user, meaning someone whose email domain does not match your organisation's. Guests are free on Business and Enterprise, and what they can actually do depends entirely on how each item is shared with them. Shared as an editor, a guest can edit unlocked rows and columns and submit update requests, all without costing you a seat. They still cannot create items or own anything on your plan. If all a client really needs is to follow along, it is worth checking whether sharing progress with clients can be done without giving them a seat in the tool at all.

The catch is that the guest seat type does not exist on Pro plans at all. On Pro, external people are treated exactly like internal ones, so they fall under member or contributor rules. If you are on Pro and a client needs to edit a sheet, that is a paid member seat. On Business it is free. Same person, same task, different plan, very different bill.

Where the paid seat count creeps up on you

The main way teams end up over-licensed is not a decision anyone made. It is provisional membership, and it works quietly. It is a good example of the hidden costs of project software, where the price is set by a default rather than a choice.

When someone without a paid member seat takes their first qualifying action on your plan, Smartsheet automatically assigns them a provisional member seat. They get the same full access as a member, free, until the end of the current billing cycle. Nobody approved this and nothing was blocked. Someone just tried to edit something and Smartsheet let them.

What happens next depends on a setting your system admin controls. The default is a downgrade: any provisional member who has not been manually upgraded drops back to a free seat at the end of the cycle and loses the access they had. The optional behaviour is auto-upgrade, where every provisional member becomes a paid member at the end of the cycle, and if you do not have spare seats, the cost of the extra ones is added to your next invoice.

Both settings have a failure mode. With auto-upgrade on, your bill grows every time somebody wanders into editing a sheet. With the default on, people quietly lose access at the end of the month and file a ticket asking why the thing they were using last week has stopped working. Neither is wrong, but you should know which one you have turned on, and admins can review and downgrade provisional members from the seat types and true-up page before the cycle ends.

This is the seat-model version of a problem that shows up all over the category. It is the same shape as running out of AI credits mid-cycle: a meter nobody deliberately set, doing arithmetic in the background.

Who on your team actually needs a paid member seat?

The rule that keeps workspaces honest is to default everyone to the free seat and promote only on evidence. Here is how that splits in practice.

People who build things

Anyone who creates sheets, reports, dashboards or workspaces, owns them, shares them, or builds automations needs a member seat. There is no way around this and no reason to try. In most workspaces this is a much smaller group than the org chart suggests, often a handful of people who set things up and maintain them.

People who only review and respond

Reviewers, approvers, stakeholders who read a dashboard once a week, and anyone whose entire involvement is commenting or attaching a file should be a contributor. Since April 2026 that costs nothing, which was not true before, and it is the single biggest saving available in most accounts. If you last audited your seats before the contributor change, you are probably paying for people who no longer need paying for.

People who need to edit but do not build

This is the awkward middle, and it is where the cost actually lands. Editing requires a member seat for anyone internal, full stop. Externally it depends on your plan: a guest on Business or Enterprise can be given editor permissions for free, while the same person on Pro cannot. If your workspace has a lot of people in this category, the seat maths gets expensive quickly, and it is worth checking whether they truly need to edit or whether an update request would do the job.

What this looks like in a real workspace

Take a marketing team on Business running campaign tracking. Twenty two people touch the workspace: four build and maintain the sheets, nine are internal reviewers who comment on progress, six are internal staff who occasionally update their own rows, and three are external agency contacts.

Left alone, this workspace tends to drift toward twenty two paid seats, because everyone got added as a member at some point and nobody revisited it. Applied properly, it is ten. The four builders are members. The nine reviewers are contributors, free, and they keep commenting and attaching files exactly as before. The three agency contacts are guests, free on Business, shared as commenters or editors depending on what they need. The six occasional editors are the only genuine judgement call, and they cost six member seats unless their updates can be handled through update requests instead.

The saving is not clever. It is just the difference between assigning seats deliberately and letting provisional membership assign them for you.

What to do about it

Smartsheet's free collaboration tier is genuinely better than it was, and if your last look at seat costs predates April 2026 your assumptions are out of date in your favour. Go to the seat types and true-up page, see how many members you are paying for who have not created anything, and downgrade them. Then check which way your provisional member setting is pointing, because that one decides whether your bill or your helpdesk absorbs the surprise.

Where this stays expensive is the middle group: internal people who need to edit but never build, and external collaborators on a Pro plan where guests do not exist. If that describes most of your workspace, seat maths will keep being a recurring admin job no matter how carefully you audit, because the cost is structural rather than accidental.

That is the tradeoff worth weighing against a flat model. Breeze charges $9 per user per month for one plan with every feature, and client users are free and unlimited regardless of what they need to do, so there is no seat type to assign and no plan tier that changes the answer. Clients get their own scoped permissions instead of a licence. For teams whose work is mostly a small core plus a long tail of clients and collaborators, that removes the question rather than optimising it. For teams who need Smartsheet's grid, formulas, and portfolio reporting, it does not replace them, and you should stay where you are and audit properly instead.

Seat types and plan availability change, as this one just did. Check Smartsheet's current documentation before making a licensing decision.