What the Form Builder builds
Five pages a signed-in member sees — not the login or registration forms. Start here before you go looking in the wrong screen.
- Beginner
- 5 min read
- Applies to 2.0
The one thing to know first
The Form Builder does not build your login, registration or password reset forms. Those are set up in Pages & Forms and styled on the Design tab. If you came here to change a field on your sign-up form, you are in the wrong screen.
What it builds is the member area: the pages someone sees after they have signed in.
The five flows
| Flow | What it is for | Shortcode |
|---|---|---|
| Account | the member's account details | [attributes_account] |
| Profile | the public-facing profile | [attributes_profile] |
| Dashboard | the landing page after sign-in | [attributes_dashboard] |
| Settings | preferences and account actions | [attributes_settings] |
| Onboarding | what a new member completes on first sign-in | [attributes_onboarding] |
Five, and only five. You cannot add a sixth.
Getting there
User Access → Form Builder. Pick a flow from the selector at the top; each one has its own fields, its own layout and its own status.
The Form Builder with the five flows in the selector and the field list below.
Who can see them
All five are for signed-in members, and they enforce it themselves. A visitor who
is not signed in never reaches one: they are redirected to your login page
before anything renders, and sent back to where they were going once they sign
in. A bookmarked /profile still works — sign in, land on the profile.
There is no setting for this, and that is the point. All five pages describe the person reading them; an account screen with no account is not a page, it is a mistake waiting to be found. Onboarding was the one candidate for a public page and it is not one either — it shows a member their own setup progress.
The redirect covers the pages you assigned to a flow in the Login Page Manager,
because only those can be recognised before the page is built. If you paste
[attributes_profile] into some other page, that page cannot be predicted — the
shortcode falls back to a short notice with the same sign-in link.
Nothing on these pages could be saved by a signed-out visitor in any case: the four handlers behind them accept no anonymous request. What changed is that the visitor now finds out before filling anything in.
If your site genuinely needs one of the five open, the filter
attrua_pro_member_page_requires_login receives the flow name and decides — per
template, per role, or per anything else code can see.
Draft and ready
Every flow carries a status.
- Draft — nothing renders on the site for ordinary members.
- Ready — the flow is live.
A draft is not invisible to you: an administrator sees it on the site so it can be tested in place, with a badge saying so. That badge is how you tell a draft you are previewing from one that is actually live — if you see it while signed in as an administrator, your members are seeing nothing at all.
New flows start as drafts. If you have built a page, put the shortcode on it, and your members report a blank space, check the status before anything else.
Where a flow's page comes from
Each flow is attached to a WordPress page. The fields you build are stored against that page, so a flow travels with its page — export it, move it, and its form goes with it.
Until a page has been assigned, the builder still works and saves your fields; they move to the page the moment one exists.
A newly created page is seeded from a starting template, so a flow is never empty when you first open it. Clear it out and start over if the starting point is not what you want.
What comes next
Something missing or out of date? Tell support.