Let members keep their own profile current.

One page called My profile. Whoever is signed in sees their own record, changes the parts that belong to them, and the office stops retyping change-of-address emails into the member list.

My profile Members only

Keep your own details current.

Name
Orin Oak
Role
Wand shop designer

Your profile, with only the fields you can edit.

Profile details Updated

Illustrative experience

  • One page serves every member
  • They only ever see their own record
  • Staff-only fields stay staff-only

The finished experience

The member list keeps itself current.

The people in the list are the ones maintaining it, so a new phone number is right the day it changes rather than the next time someone asks.

A good fit for
Associations, clubs and membership bodies whose roster is only as good as its last update.

  1. 1

    Make the profile one record

    The profile is a single entry, submitted while the member is signed in so Gravity Forms stamps it as theirs. One row to keep current, rather than a trail of submissions nobody can tell apart.

    Gravity Forms

  2. 2

    Put their own profile on one page

    An Edit Single Entry block, filtered to the entry whose Created By is the current user, shows each signed-in member their record and nobody else’s — one page for the whole membership.

    GP Entry Blocks

  3. 3

    Fence off what the office owns

    Status, tier and internal notes are yours to set. The free Remove Fields On Edit snippet keeps them off the edit form, and block-level user-role conditions decide who sees the rest.

    GP Entry Blocks

What you’ll need.

Start with Gravity Forms. Add the capabilities this solution needs, then make the experience your own.

Taking it further

Add these optional plugins when your project calls for more.

Before you start

  • Member accounts — the entry’s Created By is what ties a profile to the person signed in.
  • One profile form, submitted while the member is signed in, so each member has a single entry to come back to.
  • The free Remove Fields On Edit snippet is required for this recipe’s staff-only field exclusions. Optional account synchronization needs User Registration and Process Feeds on Edit, with unrelated feed IDs excluded; delayed feeds do not rerun.

Get this built.

A plan covers how many of our plugins you run at once, and on how many sites. Here is what this one needs.

Required

  • GP Entry BlocksPerks

Optional

Gravity Perks Basic $59 /year

Covers this on one site. More sites need Advanced or Pro.

Gravity Perks Advanced $169 /year Taking all 2 optional perks too makes it 3 in all, which needs Advanced.

See plans for this solution

Every plan renews at the same price, and you can upgrade any time for the difference.

Make it fit
your project.

How do we know when someone changes their details?

Saving from an Entry Block fires the “Entry Edited via Entry Block” notification event. Point a notification at the office and the change comes to you, so nobody has to watch the list for edits.

Does editing the profile update their WordPress account?

Not on its own. For optional account synchronization, configure the User Registration add-on’s update feed and the Process Feeds on Edit snippet. Exclude unrelated feed IDs so editing a profile does not repeat their actions; delayed feeds are not processed. Test the update with the feeds on your form.

  • Clay, CTO
  • Dan, Content Sorcerer
  • Dani, Product Manager
  • David, Founder & CEO
  • Matt, Senior Support Wizard
  • Roxy, Support Wizard

Not quite your build?

Tell us what you are making and we will work out which pieces it takes — or tell you straight if this is not something we can do.

Ask the wizards