Originally published: August 21, 2021 · Last updated: August 17, 2026
Some WordPress sites need users to submit content without allowing unlimited publishing. Examples include directories, guest-post programs, member communities and internal editorial systems. The important distinction is between permission and quota.
WordPress core can control what a user is allowed to do through roles and capabilities. It does not provide a general setting such as “this author may create only five posts per month.” A numerical or time-based quota therefore needs an additional workflow, plugin or custom logic.
Start with the correct role
Do not give someone Administrator or Editor access simply because they need to submit content. WordPress roles are designed to restrict privileges. Contributors, for example, can create content without having the same publishing powers as Editors.
Choose the minimum capabilities necessary for the workflow. This reduces both accidental changes and the impact of a compromised account.
Decide what the limit actually means
A useful quota needs a precise rule. Is it five new posts per calendar month, ten drafts at any time, one submission per day or a total number of directory entries attached to a membership plan? Also decide whether deleted, rejected or expired content counts.
Ambiguous rules become difficult to enforce consistently.
Prefer pending review when editorial control matters
If the real problem is quality rather than volume, forcing new submissions into a review workflow may be more useful than a hard numerical limit. A contributor can submit content while an editor decides what is published.
This is especially effective for guest posts and collaborative sites where ten good drafts may be acceptable but one automatically published low-quality post is not.
Use quotas for business rules
Numerical limits make more sense when they are part of the product itself. A directory might allow a free account to create one listing and a paid account to create ten. A community could limit new submissions to reduce spam. In these cases, the quota should be enforced by the plugin or application responsible for the membership or submission feature.
Do not rely on hidden interface controls
Removing the “Add New” button after a threshold is reached can improve the interface, but it should not be the only enforcement mechanism. Permissions and server-side validation should still prevent disallowed actions.
Communicate the limit clearly
Show users how much of their allowance remains and what happens when it is reached. A silent error is frustrating. A message such as “You have used 5 of 5 submissions for this month” makes the rule understandable.
Bottom line
Use WordPress roles and capabilities to control what users can do, then add quota logic only when you genuinely need to control how often or how much they can submit. For editorial sites, pending review is often more useful than an arbitrary post limit.