Features Solutions Pricing FAQs Contact
Sign In

Other

Grid Tools Feature Request Portal

Grid Tools is built around real Smartsheet workflow friction — features are added because users hit specific, recurring pain points in their daily work. The feature request portal is how those needs get communicated. The most actionable requests describe a concrete workflow, identify what step is slow or impossible, and explain how often the situation arises.

Without Grid Tools

The daily workaround

No channel for structured feedback
Without a formal submission process, feature ideas get lost in support threads or never reach the development roadmap at all.
Vague requests stall development
Requests that describe an outcome without describing the underlying workflow are difficult to scope and prioritize against other work.
Duplicate requests fragment signal
When many users hit the same issue and submit separate requests with different descriptions, it's harder to measure how many people are affected.
No visibility into request status
Users who submit requests have no way to know whether the idea was received, considered, or added to the roadmap.
Screenshot: Grid Tools release notes page showing a new feature with a note indicating it originated from a user request
Release notes call out features that were directly requested — you can verify whether your submission shipped.
Screenshot: Known limitations page showing a documented browser extension constraint with a note that a workaround is planned
Some requests surface a browser extension limitation rather than a missing feature; the limitations page documents which constraints have planned workarounds.
Screenshot: Support center page linking to both the feature request portal and the roadmap
The support center links the request portal and roadmap so you can check existing plans before submitting a duplicate.

With Grid Tools

How Grid Tools handles it

Structured submission form
The portal collects the workflow context, frequency, and current workaround needed to make a request actionable — not just a feature name.
Roadmap transparency
Accepted requests that reach the development roadmap are visible on the roadmap page so users can track what is planned and what has shipped.
Direct path from pain to product
Grid Tools features are scoped around specific, demonstrated Smartsheet friction rather than generic requests, so strong submissions have a direct path to the roadmap.
Release notes track shipped requests
The release notes page documents what shipped in each version, making it possible to verify that a submitted request was addressed.
Screenshot: Feature request form showing the workflow description field with an example of a specific Smartsheet task being described
Describe the exact Smartsheet operation you're trying to do — not just the feature name you want.
Screenshot: Feature request form showing the frequency and current workaround fields filled in
Stating how often you hit the problem and what you currently do instead helps prioritize the request.
Screenshot: Grid Tools roadmap page showing a planned feature with a brief description of its scope
Accepted requests that are planned for development appear on the public roadmap page.

Frequently asked questions

What makes a feature request likely to be prioritized?

Requests that describe a specific Smartsheet workflow, identify the exact step that is slow or impossible, quantify how often the situation occurs, and explain the current workaround provide the most actionable signal for roadmap decisions.

Can I request a feature that requires Smartsheet API access?

Grid Tools is a browser extension that operates on the Smartsheet DOM and does not use the Smartsheet API, so features requiring API calls are outside the current technical scope — but documenting the need is still useful context.

How do I know if my request was already submitted by someone else?

Check the roadmap page and release notes before submitting — if the feature is already planned or shipped, it will appear there; if it isn't, your submission adds to the signal even if the concept has been raised before.

Is there a way to vote on or upvote existing feature requests?

The current portal collects submissions rather than public voting; the roadmap page reflects which requests have been accepted into the development queue.

Related solutions

Ready to try it?

Download for free. Upgrade when ready.

Download free See all features