# How to Build a WordPress Community Site Where Members Post

> A playbook for a member-run WordPress community blog: member roles, a front-end submission form, review with Pending status, and a members' dashboard.

By Aleksan Aharonyan, November 18, 2026. Original: https://wpuserpublish.com/blog/wordpress-community-site-members-post/

## Key takeaways

- Choose Subscriber for read-only members, Contributor for members who write, and Author only for people whose posts you trust to go live without review.
- Give members one page with a front-end submission form instead of wp-admin access; the form decides the fields, the post status and the emails.
- Set new posts to Pending and let email notifications tell you and the author what happened to a submission.
- Hand members the `[fe_fs_user_admin]` dashboard so they can see, edit and delete their own posts without opening the WordPress admin.

## What kind of community site are you building?

Start by deciding which of three shapes you are building, because each one changes the roles you hand out, the fields on your form, and how much review a post needs.

- **Community blog.** Many members, many posts, categories that matter, and one or two reviewers. This is what most people mean by a WordPress community site.
- **Club or association site.** A smaller group posting news and announcements. Fewer contributors, more trust, a shorter review step.
- **Member directory or listings site.** Each member owns one entry rather than a stream of posts, so the fields matter more than the publishing rhythm.

All three need the same four pieces: a way to sign members up, a form they submit from the front end, a rule for whether posts go live immediately, and a place where members can see and edit what they sent. WordPress roles cover the first and third. A post submission plugin covers the form and the dashboard. A membership suite is an option, not a requirement, and it brings settings a member blog never touches.

The rest of this playbook builds the community blog shape and marks where the other two differ.

## User roles for members: Subscriber, Contributor or Author

WordPress already ships the roles a community site needs, so pick the lowest one that lets a member do their job and promote people one at a time.

- **Subscriber** reads and comments, and cannot write posts in wp-admin. This is the right default role for new registrations: an unknown account gets a wp-admin dashboard with nothing in it, and a front-end form can still accept its posts under the form's own status rule.
- **Contributor** writes posts and saves drafts but cannot publish, and cannot edit anyone else's work. Use it for a new member who has been invited to write. WordPress does not let Contributors upload files by default, so test a featured image upload with a real Contributor account before you launch.
- **Author** publishes and manages their own posts. Give it to members with a track record.
- **Editor and Administrator** can publish and edit everyone's posts and change settings. Keep these for the people running the site.

Role and form setting do different jobs. The role decides what a member can do inside WordPress, including which posts they can delete from the dashboard. The form's Post Status decides whether a submission goes live. A Contributor submitting through a form set to Publish still ends up published, and an Author submitting through a form set to Pending still waits for review.

New accounts get the site's default role and an email with a link to set their password, like the WordPress registration page sends. Put a link to the WordPress "Lost your password?" page beside the form too, for members whose email lands in spam.

## Building the front-end submission form members use

The form is the whole member experience: it decides which fields appear, which editor they write in, and what happens when they hit submit. Keep it to the fields a post actually needs.

1. **Add the post fields.** Post Title, one content field, Taxonomies (categories, tags), and Featured Image if members supply their own. Custom fields for profiles or listings need Pro.
2. **Choose one content editor per form.** TinyMCE, the classic WordPress editor, suits members who write in a word processor. Markdown suits technical audiences. EditorJS gives a block-style editor with headings, lists, quotes and embeds. A plain Textarea is for posts with no formatting at all.
3. **Trim the category list.** Exclude terms members should not use and set defaults. A short, clear list makes review faster.
4. **Put the form on a page.** Use the shortcode `[fe_form id="123"]` or the Front Editor block, then add the page to your menu.
5. **Edit the logged-out message.** A visitor who is not signed in sees a message you can rewrite; point it at your login page.
6. **Test as a member.** Administrators have permissions members lack, so submit from a Subscriber account and a Contributor account before you announce anything.

[Front User Submit](https://wordpress.org/plugins/front-editor/), a free plugin for frontend post submission and guest posting forms, handles this step with a drag-and-drop form builder: you drag fields into order, pick the editor, and place `[fe_form id="123"]` on a page.

## Publish now or review first: setting the status and the emails

Set new member posts to Pending unless every writer has earned your trust, because Pending keeps the post off the site until you publish it, while a form set to Publish puts every submission live on arrival.

The form's Post Status setting has two values, Publish and Pending, and members can also save a Draft with the Save Draft button while they are still writing. Then choose what happens after submit: stay on the page, open the new post, or go to a custom URL such as a thank-you page.

In Front User Submit you set the form's Post Status to Pending, so member posts wait in your queue. The [post submit settings](/docs/forms/post-submit-settings/) cover the status, the buttons and the redirect together.

Emails are per form. Notify the admin when a post is submitted, and the author when their post is submitted, published or trashed, using variables such as `[post_title]` and `[post_link]`. Turn on at least the admin email: without it, Pending posts sit unseen. The [notification settings](/docs/forms/notifications/) list each trigger, and mail goes out through WordPress's normal mail function, so send a test to a real inbox and add an SMTP plugin if your host drops it.

Two limits to plan for. Posts from people with no account at all are guest posting, a Pro feature, and a logged-out form needs captcha, also Pro, so most member sites run the free login-only form until they open up. The [plans](/pricing/) show what Pro adds.

## Where members see and edit their posts after submitting

Members manage their posts on a front-end dashboard page, not in wp-admin. The shortcode `[fe_fs_user_admin]` renders tabs for Publish, Pending and Draft, with edit and delete icons beside each post, so a member can fix a typo or check why a post is still waiting.

Front User Submit creates that page on activation, and the [user dashboard settings](/docs/user-dashboard/user-dashboard/) explain how the tabs behave.

Deleting follows the member's WordPress role: by default Subscribers cannot delete, Contributors can delete their own unpublished posts, and Authors can delete their own posts. You do not configure that, but say so in your welcome note so nobody hunts for a button that isn't there.

Editing reuses the submission form, with its own settings: the edit page, where to go after an update, the message shown after saving, and the button text. The time lock stops edits a number of hours after the post was created, which helps once posts are published and shared.

Add `[fus_form_login]` and `[fus_form_register]` so members sign up and log in on your site instead of the WordPress login screen. Both take a redirect, so a new member can land straight on the submission form.

## A launch checklist for a member-run community blog

Work through this list before you announce the site, then run it again after your first ten member posts.

- Default role is Subscriber, and you have promoted your first writers by hand.
- One named reviewer and one review cadence, so Pending posts do not wait a week.
- Test submission from a Contributor account on a phone, not only on the desktop where you built the form.
- Both emails arrive: the admin notification and the author notification.
- The form is set to Pending, and you have written down when a writer moves to Author or the form moves to Publish.
- Dashboard, login and submission pages are in the menu, and the registration page links to WordPress's "Lost your password?" page.
- Three short submission rules are visible to members: length, what counts as on-topic, and what happens to a post you send back.
- Category and tag fields show the terms you want and hide the ones you don't.
- A time lock is set if you don't want edits landing on published posts after the fact.
- Your spam plan is written: login required, Pending review, and captcha if you ever open the form to guests.

Then leave it alone for a month. Count how many posts you published as submitted, how many you edited, and how many you sent back. Those three numbers tell you whether the next change is a new field, a tighter review rule, or a different role for your writers.

## FAQ

### Do members need a WordPress account to submit a post?

Yes on the free version: a logged-out visitor sees a message instead of the form, and you can edit that message to point at your login page. Accepting posts without an account is guest posting, a Pro feature. An account also gives the member a dashboard for editing later, which is why most community sites keep the login requirement.

### Should members publish their own posts or wait for review?

Start with review, even for writers you trust, because a Pending queue is easier to loosen than a bad post is to unpublish. Once a member has a few posts you have approved, you can give trusted writers a second form set to Publish, or promote them to Author, and keep everyone else on the Pending form.

### How does a new member get a password?

The registration form creates the account with the site's default role and emails the member a link to set their password. If that email does not arrive, show them the WordPress "Lost your password?" page, where they enter their username or email and choose a new password, then log in and submit.
