Submission limits (quotas) per company or user

Right now any user with access can submit an unlimited number of feature requests. In practice this means one enthusiastic user can file 100 items while other customers file one, which skews the board and the upvote signal.

We would like to cap submissions, configurable per company (and optionally per user), for example:

• View only: 0 open submissions, can still read, comment and upvote

• Standard: 5 open submissions at any time

• Enterprise: 20 open submissions at any time

Key behaviour we are looking for:

• The limit counts open submissions only. When an item is set to Completed, Closed or Declined, the slot is released

• Limit set as a default per plan/segment, with an override on the individual company record, and optionally a per-user cap inside a company

• When the limit is reached, the submit button is disabled with a clear message ("Your organisation has 5 of 5 open requests. Close or wait for one to be completed, or upvote an existing request.")

• Admins can always exceed the limit when submitting on behalf of a customer

• Counter visible to the user and to us in the company profile ("Open requests 4 / 5")

Why this is useful

Submission volume may be part of SLA tiering. Customers on a discounted or basic subscription should get read plus upvote access, while enterprise contracts get a larger allowance.

Today we have no technical way to enforce that, so it becomes a manual conversation. It would also nudge users toward upvoting existing requests rather than filing near duplicates, which improves the quality of the roadmap signal.

Mockups below. We believe this feature would be a great addition to the professional plan.