Members-Only Submission Form in WordPress: A Playbook
By Aleksan Aharonyan ·
A members-only submission form in WordPress is a post form that only signed-in members can use: logged-out visitors get a short explanation and a way in, not a set of fields they cannot submit. Three pieces make it work: a role that decides what a member may do, a form that collects the post, and a front-end dashboard where members manage what they sent. This playbook sets them up in that order and ends with a test run from registration to first edit.
Key takeaways
- Set the default role for new members before you build the form, because that role decides what they can do with a post after they submit it.
- Leave the guest posting option (Pro) off: that single setting is what makes the form members-only rather than open to the whole internet.
- Give logged-out visitors a route forward, either an editable restricted message with login and registration links, or, on Pro, a login form in place of the submission form.
- Run the final test in a private browser window with a brand-new account, because your administrator account hides every restriction you have just set.
What “members only” should mean for a submission form
Members only means two gates, not one: the visitor must be signed in, and the account they signed in with must be allowed to submit. WordPress covers the first gate through its own login system. You cover the second through the role new accounts receive and through one setting on the form itself.
A members-only form is not a private site. The published posts stay public, which is usually the point; only the act of submitting is restricted. That distinction matters when you choose where to put the restriction. Hiding the submit page behind a password, a maintenance mode or an unguessable URL is weaker than it looks, because links get shared and cached. The check inside the form is the part that holds, because it runs on every request.
There is a second model worth naming. If the site needs reach, you accept posts from strangers and review them before they appear. A members-only form fits a club, association or paid community where the contributor list is known in advance. If the site’s value comes from outside voices, an open form with a review step will serve you better than a login wall, and a members-only form only adds friction.
Pick the role that members get when they register
Every new WordPress account gets the site’s default role, a single setting in the WordPress settings, and that role decides what the member can do after the post is submitted. Set it before you invite anyone. Changing the default later affects new accounts only, so existing members keep whatever role they were given.
For a members’ submission site, Contributor is the usual choice: it can create and edit its own posts but cannot publish them, so a member who wanders into wp-admin still cannot push anything live. Subscriber is the more minimal option and is fine when the form does all the work.
The role also decides what a member can remove. Deleting follows the WordPress role: by default a Subscriber cannot delete, a Contributor can delete their own unpublished posts, and an Author can delete their own posts. If you want members to clean up after themselves from a front-end dashboard, Subscriber is the wrong default and Contributor is the right one.
Images add one catch. A member needs the WordPress upload_files capability to add a featured image, and a Contributor does not have it by default (the form plugin used later in this playbook gives it to Subscribers when it is activated). If you choose Contributor and want images, add that capability to the role with a role editor plugin.
Never make Author, Editor or Administrator the default role on a site that accepts registrations. Those roles can publish, edit other people’s work or change the site.
Plan for the first password. A front-end registration form creates the account with the site’s default role, and since version 5.2.5 it sends the same emails as the WordPress registration page: the new member gets a link to set their password, and the admin gets a new user notice. If your site’s mail does not reach inboxes reliably, that link never arrives, so check that your site sends email properly and point members at the WordPress “Lost your password?” page as a backup on your registration page.
Build the post form and restrict it to logged-in users
Work through these steps in order; the last two are the ones that make the form members-only.
- Create the form and choose the post type it writes to. Posts suit most clubs. Custom post types need Pro.
- Add the fields members actually need. Post Title, a content editor, categories or tags, and a featured image cover most cases. Fewer fields means more finished submissions.
- Decide what happens after submit. Set the post status, the redirect and the success message. In Front User Submit, a free plugin for frontend post submission and guest posting forms, the form has one Post Status setting, so every member post can go to Pending from the same screen where you built the fields.
- Leave guest posting off. Guest posting lets visitors submit without an account, it is a Pro feature, and on a members-only site it stays disabled. With it off, a visitor who is not signed in cannot submit, whatever they do to the page.
- Place the form. Put it on a page with
[fe_form id="123"]or the Front Editor block, then look at that page while logged out to confirm the restriction is doing its job.
The redirect choice is worth a minute. Staying on the page suits a site where one member files several posts in a row. Opening the new post suits a news site where the member wants to see the result. A custom URL suits sending people back to the dashboard.
What visitors who are not logged in should see instead
A logged-out visitor on the submit page should see a short explanation of who can post and two links, one to log in and one to create an account. A blank form, a redirect into wp-admin or a bare “you must be logged in” line all end the visit instead of starting it.
Front User Submit shows an editable restricted message in place of the form by default, and the Pro version can put a login form on that page instead, so the visitor signs in without leaving it. Either way, write the message for a person who has never heard of your site: one sentence on what members get, then the two links. The guest posting and login restriction settings cover both behaviors, and the login and registration form settings explain the shortcodes and their redirects.
Order the links by who is most likely to be reading. A brand-new audience needs the registration link first. A renewal or returning-member page needs the login link first. If your site already has a public login page, link that; if not, the plugin’s own login shortcode keeps people on a page that looks like the rest of your site rather than the default WordPress login screen.
Keep members posting from the front end, out of wp-admin
Members who submit through the front end should stay there, including when they edit. Front User Submit creates a user dashboard page with [fe_fs_user_admin] when you activate it, and that shortcode shows Publish, Pending and Draft tabs with edit and delete icons, so a member can fix a typo or check whether their post went live without ever seeing the WordPress admin.
That dashboard is also the natural landing page after login. A Subscriber who signs in through the standard WordPress login screen lands on a profile page inside wp-admin, which reads as a dead end to someone who just wanted to post a notice. Set the login form’s redirect to the dashboard or back to the submit form. The user dashboard settings explain the tabs and every dashboard option.
Two more details belong here. The edit view uses the same form, so members see familiar fields rather than a stripped-down editor. And the edit settings include a time lock, which stops changes a number of hours after the post was created, useful for notices that should not be rewritten after the fact.
Decide whether member posts publish or wait for review
Choose per form, not per site: a club newsletter can publish immediately while the public news page waits for a read-through. The difference is who carries the risk of a bad post going live.
| Post status | Best for | What it costs |
|---|---|---|
| Publish | a closed club where members are known | you read posts after they are public |
| Pending | a site with a public front page | someone must review, and members wait |
With Pending, the review step only works if it is staffed. Turn on the per-form email notifications so the admin hears about each submission and the author hears when a post is submitted, published or trashed. A member who submits and hears nothing assumes the form is broken.
Keep the member’s own draft separate from your review queue. A draft is unfinished work that stays with the member; Pending is a finished post waiting on you. Tell members in the form’s intro text which one they are creating, and roughly how long review takes.
Test the flow: register, log in, submit, edit
Test with a browser window that has no session, not with your admin account. Each step below fails differently, and the order matters because a fault early on hides the ones after it.
- Open the submit page logged out. You should see the message and the two links, not the fields.
- Follow the registration link and create a test account with a real address you can read.
- Check the account in the WordPress users list and confirm it has the role you intended.
- Open the set-password email the registration sent (if it does not arrive, fix the site’s mail delivery and use the WordPress “Lost your password?” page meanwhile), set a password, then log in through the front-end login form and confirm the redirect lands where you planned.
- Submit a post with a title, some content, a category and a featured image. Note the status it lands in.
- Open the dashboard: the post should appear under the matching tab. Edit it, save, and confirm the change shows on the front end.
- Delete the test post and see whether the role allows it. If it does not and members should be able to delete, change the default role.
You know the setup works when the submit page never shows fields to a signed-out browser, every new account lands with the role you chose, the post shows up in the dashboard tab that matches its status, and the notification emails arrive at both addresses.
FAQ
Can I make a WordPress form that only logged-in users can submit?
Yes. Keep guest posting switched off and the form renders the restricted message instead of the fields for anyone who is not signed in. The page URL can stay public and indexable, because the restriction lives in what the page outputs, not in who can reach the URL.
Do members need their own WordPress account to submit a post?
For a members-only form, yes, and that account is what ties the post to a person who can edit it later. Submitting without an account is possible on some setups, but then the sender has no dashboard, no edit rights and no way to prove the post is theirs.
How do I stop members from ending up in wp-admin?
Give them a front-end dashboard and set the login form to redirect there after sign-in. A Subscriber who logs in through the standard WordPress screen still reaches a minimal profile page, so the redirect is what keeps the experience on your site. Do not solve this by giving members higher roles.