# Limit number of jobs users can submit by partition

**URL:** <https://discourse.openondemand.org/t/limit-number-of-jobs-users-can-submit-by-partition/2835>\
**Category:** Feature Requests and Roadmap Discussion\
**Created:** [July 27, 2023, 12:02am UTC](https://discourse.openondemand.org/t/limit-number-of-jobs-users-can-submit-by-partition/2835 "2023-07-27T00:02:24Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![aneil2](https://avatars.discourse-cdn.com/v4/letter/a/dbc845/32.png) [@aneil2](https://discourse.openondemand.org/u/aneil2)\
**Post date:** [July 27, 2023, 12:02am UTC](https://discourse.openondemand.org/t/limit-number-of-jobs-users-can-submit-by-partition/2835/1 "2023-07-27T00:02:24Z")

</div>

Further to a discussion at the booth at PEARC23  
You can limit the number of jobs that a user can submit by creating a qos that has limts set to whatever value. However the feed back to the user is not friendly (see below). A better solution would perhaps to have a data parameter, perhaps definable per partition, that would allow the OOD interface to give meaningful feedback before a user launches a job. Possibly just disabling the launch button with a tooltip feedback explaining why?

 ![image](https://us1.discourse-cdn.com/flex015/uploads/osc/original/2X/3/36d6d2143591ba9ee61adfa25d0ef5c17f365299.png)