Skip to content
Front User Submit
Menu

WordPress Contributor Role: A Checklist for Member Posts

By Aleksan Aharonyan ·

The WordPress Contributor role lets a user write and save their own posts but not publish them, so anything a Contributor submits waits as Pending until someone with publishing rights approves it. That makes Contributor the right default for members who send you posts, Subscriber the right role for people who only read, and Author a role you hand out deliberately to people whose work you would publish unread.

Key takeaways

  • Contributor can create, edit and delete their own unpublished posts but can never publish one, so every submission from a Contributor lands in review.
  • Contributors do not have the file upload capability by default, so a featured image or file field needs a test with a real Contributor account before you announce the form.
  • Authors publish without review and Editors can edit other people’s posts, so neither role belongs to a member who submits work for approval.
  • The role decides what a member sees in a frontend dashboard and which edit and delete buttons they get, so set up the dashboard and the login flow at the same time as the role.

What the WordPress contributor role can and cannot do

The Contributor role is WordPress’s write-but-do-not-publish role: a Contributor can create posts, edit and delete their own posts, and save drafts, but cannot publish anything or touch anyone else’s work.

Under the hood this is a fixed list of capabilities. A Contributor has edit_posts, delete_posts and read. A Contributor does not have publish_posts, so no publish button appears in wp-admin, and does not have upload_files, edit_others_posts or edit_published_posts. The WordPress roles and capabilities reference lists the full set for every role.

The practical consequence for a site that accepts member posts is that review comes built into the role. A Contributor who submits a post produces a Pending post, not a live one, and that is WordPress doing part of the moderation work for you. On the front end the same guarantee has to come from your form settings instead: keep the form’s Post Status on Pending so a Contributor submission still waits for review, and remember that a front-end form set to Publish can put a Contributor’s post live, because the form setting, not the role, decides the status of a new post.

Two caveats. Role-editing plugins can rewrite these capability lists, so if you run one, check what Contributor actually means on your site rather than assuming. And a custom role that copies Contributor but adds media uploads is possible, but every step of your submission flow then needs retesting.

Subscriber, Contributor, Author, Editor: a capability checklist for submitted posts

Only two of the four common roles should ever create posts on a member site, Contributor and Author, and the difference between them is whether a human reads the post before it goes live.

Role Creates posts Publishes without review Uploads media
Subscriber No No No
Contributor Own only No No, by default
Author Own only Yes Yes
Editor Anyone’s Yes Yes

Subscriber

A Subscriber can read the site and nothing else, which makes this the role for readers and for anyone whose posting rights you have not confirmed yet. Start new accounts here and promote after the first accepted post; that is the least-privilege path and it costs you one extra click per member.

Contributor

A Contributor can write, save drafts, edit their own drafts and submit work for review, which is what most member-post sites actually need. The limit people notice first is publishing, since that is the point of the role. The limit people forget is media: without the upload capability, a featured image field can fail for a Contributor while working perfectly for you as an administrator.

Author

An Author can publish their own posts immediately, upload media, and edit and delete their own published posts. Give this role to columnists, staff writers and long-standing contributors whose work you would publish without reading first, because once someone is an Author your review step no longer applies to them.

Editor

An Editor can publish and edit anyone’s posts and moderate comments. It is a staff role, not a member role, and no submission workflow needs it.

Which role should people who post on your site get?

Give Contributor to anyone whose posts you want to read before they go live, Author only to people whose work you would publish unread, and Subscriber to everyone else until they have submitted something you accepted.

A few common cases:

  • An open call for posts from strangers. Contributor, with the form’s Post Status set to Pending. You get a review queue and the writer gets a post they can still fix.
  • A regular columnist or a colleague. Author. Reviewing their work every time slows both of you down.
  • Directory listings, classifieds and profile-style posts. Contributor, because the person who owns the listing is usually the one who needs to correct it later.
  • Paid submissions. Payment does not change the role. The post still needs review after the money clears.

There is a third option that removes the role question entirely: guest posting, where a visitor submits without an account at all. There is no role, no dashboard and no author to notify, and the trade-off is that the visitor cannot come back to edit their post, so every correction runs through you. It suits one-off contributions and contests more than it suits an ongoing community.

How the role changes what users see in a frontend post dashboard

A frontend dashboard shows each member only the posts their role allows and hides the actions their role cannot perform, so the role you assign decides whether a member can fix a typo, withdraw a draft or delete their own post.

In Front User Submit, a free plugin for frontend post submission and guest posting forms, the [fe_fs_user_admin] dashboard splits a member’s posts into Publish, Pending and Draft tabs, and the edit and delete icons follow the user’s WordPress role rather than a separate plugin setting. By default a Subscriber cannot delete posts, a Contributor can delete their own unpublished posts, and an Author can delete their own posts. The user dashboard documentation walks through each option.

That means a Contributor typically sees their submission sitting in Pending, can open it in the same form and correct it, and has no way to push it live. An Author sees the same post under Publish and can take it down themselves. If those two experiences do not match what you expect, the role is the first thing to check, not the form.

One more setting worth pairing with the role: an edit time lock closes editing a set number of hours after the post was created. Without it, members can keep reopening and changing their posts long after you reviewed them.

Keeping contributors out of wp-admin and off the admin bar

A Contributor who lands in wp-admin finds a stripped-down dashboard with almost nothing useful on it, so redirect members to the front end after login and keep the admin bar out of their way.

WordPress does part of this on its own: a Contributor genuinely cannot publish from wp-admin, so the risk is confusion rather than damage. The rest is configuration. Set the login form to send members to their frontend dashboard instead of wp-admin, and hide the admin bar for members. Front User Submit’s global settings include an admin bar option, for example showing it only to administrators.

If you block wp-admin outright for low roles, test a submission afterwards. Some blocking rules also catch the background requests a front-end form depends on, and the form fails in a way that looks like a permissions problem but is not. And do not solve a permissions problem by promoting someone to Administrator or by switching off a security plugin; fix the role instead.

A checklist to run through before you open submissions

Run these checks on a staging copy with one test account per role, because most role problems only appear when an account without publishing rights actually uses the form.

  1. Create one test user per role. A Contributor and an Author are the minimum. Testing only as an administrator hides every permission bug.
  2. Set the form’s Post Status to Pending. Then submit as the test Contributor and confirm the post is Pending, not Published. If it publishes, the form is overriding the role.
  3. Test the media path as a Contributor. Upload a featured image in the form. If it fails, decide deliberately whether to grant the upload capability or to drop the field for that role.
  4. Open the frontend dashboard as a Contributor. Confirm the Pending tab shows the post, the edit link works, and the delete icon is there for an unpublished post.
  5. Set an edit time lock. Decide how many hours a member has to correct their post after submitting, and set the same limit for every role you hand out.
  6. Send a test submission and check both emails. The admin notification confirms the form works; the author notification confirms the member knows their post arrived. Posts submitted without an account have no author to email.
  7. Point new registrations at the dashboard. Front User Submit’s [fus_form_login] and [fus_form_register] shortcodes let you set a redirect after login and after registration, and new users get the site’s default role. The login and registration settings explain both.
  8. Check the default role in WordPress itself. New accounts should land on Subscriber unless you have a reason. A site that defaults to Author lets every new account publish from wp-admin without review.
  9. Explain the password step. Since version 5.2.5 the registration form emails new members a link to set their password, like the WordPress registration page. Tell them to watch for it, and to use the WordPress “Lost your password?” page if it does not arrive.
  10. Write down the review routine. Who checks Pending, how often, and what happens to a rejected post. A role only protects you if someone actually works the queue.

FAQ

Can a WordPress Contributor publish a post?

No. The Contributor role does not include the publish capability, so a Contributor can save drafts and submit posts for review but cannot make them live, either in wp-admin or through a front-end form that respects the role. To publish, they need the Author role or someone with publishing rights has to approve the post.

What happens to a Contributor’s posts if I promote them to Author?

Existing posts keep their current status, but everything they submit from wp-admin from then on publishes immediately, because the Author role includes publishing their own posts. If you still want review for that person, leave them on Contributor and let the Pending queue do the work.

The Contributor role does not include the media upload capability, so uploads can fail even though the rest of the form works. Test the exact field with a real Contributor account, then either grant the upload capability knowingly or choose a submission setup that does not depend on it.