1. Create a form
2. In the Form Settings->Form Permissions, set "Limit number of entries to one per...Logged-in User"
3. Check the Allow front-end editing of entries and set the "Role required..." fields to what you require
4. Assuming the user has created an entry, the next time they access the form, it will be populated with their info and will be in "edit mode".

https://formidableforms.com/knowledgebase/set-up-front-end-editing/

Thank you for the help Rob. While I am still sorting out and learning how the various aspects of the forms work, there are some things I don't understand.What is it about the Edit User Profile Form Template provided by Formidable forms which makes it load data from users fields?  Where as, taking an existing form I have and/or made, while following your instructions, DOES NOT load data from users fields?I followed your instructions on both an existing form and a new form, user information did not load.Which leads me to my next question...Referring to your point 4:4. Assuming the user has created an entry, the next time they access the form, it will be populated with their info and will be in "edit mode".Is that to say, if its a registration form, the first time a user fills it in then submits, with the right settings you mention above, the next time they load that same form, it will auto-fill with the information they previously entered and be editable?Here is the flow I am trying to do1. New user registers for site using a super simple form, fname, lname, email (and conf), password (and conf). SUBMIT2. User logs in, now has access to edit/update their profile with additional information only available to logged-in users. UPDATEI don't understand why this flow is proving to be so difficult for me to wrap my head around using FF.Thanks so much.  

OK, I think I see the flow now.Use a registration form for new users with the settings you mention.  Fields which I don't want the user to fill in, I set Availability to logged-in user only.Then, when logged in, use the same form and it will populate with the information the user entered upon registration, AND the logged-in user fields will now show up, AND the Register button will now show as an Update button. Is this correct?

One of the most important things to understand is the User ID field in a form. That will hold the ID of the user who created it and, more importantly, will allow you to link data from multiple forms because the user id in the entry of Form A and Form B will be the same. When you display an existing entry in a form by using either the editlink shortcode or coding the URL manually, if the entry id exists and the user id is that of the current user (or a user who has permission to edit the entry), the entry will be in edit mode and, yes, the Update button will display rather than the Submit button (the names of the buttons are configurable).

Thanks again Rob.  Tremendous help.  Between my last message and your reply, I figured out the flow and how things are tied together.Thank you!!