# Parameter user registration

**URL:** <https://community.gravityforms.com/t/parameter-user-registration/16306>\
**Category:** Get Help\
**Tags:** user-registration, gravity-flow\
**Created:** [November 20, 2023, 10:00am UTC](https://community.gravityforms.com/t/parameter-user-registration/16306 "2023-11-20T10:00:44Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![d.fiorentino](https://avatars.discourse-cdn.com/v4/letter/d/838e76/32.png) [@d.fiorentino](https://community.gravityforms.com/u/d.fiorentino)\
**Post date:** [November 20, 2023, 10:00am UTC](https://community.gravityforms.com/t/parameter-user-registration/16306/1 "2023-11-20T10:00:44Z")

</div>

Good morning, I am new and I haven’t yet understood how the user registration plugin of Gravity Forms works. I have created an update form identical to the registration form. Which parameters should I use in the meta fields to enable the display of fields that have already been filled in during the registration phase?

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/flex020/uploads/gravityforms1/original/2X/f/fef63f0599c45e0218c30d9f5d7ca8bff9b00189.png) [@system](https://community.gravityforms.com/u/system)\
**Post date:** [December 20, 2023, 10:01am UTC](https://community.gravityforms.com/t/parameter-user-registration/16306/2 "2023-12-20T10:01:23Z")

</div>

Closed on December 20, 2023, 10:01am UTC

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.

---

<div class="post-metadata">

**Author:** ![JamieO](https://sea2.discourse-cdn.com/flex020/user_avatar/community.gravityforms.com/jamieo/32/2521_2.png) [@JamieO](https://community.gravityforms.com/u/JamieO)\
**Post date:** [February 14, 2024, 4:38pm UTC](https://community.gravityforms.com/t/parameter-user-registration/16306/3 "2024-02-14T16:38:22Z")

</div>

Hi Donato,

The following list shows how you can use [Gravity Flow](https://gravityflow.io) to have one form handle both user registration + updates thanks to the Update User step type. If you don’t need approval between each registration and update, the workflow you setup would be even easier to create.

1. A potential user submits the registration form.
2. The entry goes to an Administrator for an [approval step](https://docs.gravityflow.io/article/22-approval-process).
3. On approval, the user is created via the [User Registration feed](https://docs.gravityforms.com/user-registration-add-on/#h-create-your-feed).
4. Via the [gravityflow\_step\_complete action](https://docs.gravityflow.io/article/98-gravityflowstepcomplete) the newly created user ID is stored in the User workflow field of the entry.
5. A [notification step](https://docs.gravityflow.io/article/72-email-notifications) sends an email with a link to [update their profile](https://flow-demo.gravitydemo.com/user-registration/update-profile/)
6. The user updates their profile data through a [user input step](https://docs.gravityflow.io/article/23-configuring-user-input-step).
7. The updated entry is approved via an approval step.
8. The [Update User workflow step](https://docs.gravityflow.io/article/260-update-user-step) updates the user’s profile and the entry goes back to ‘Change Profile Data’ for more changes.

The code snippet for gravityflow\_step\_complete in that case is:

```auto
add_action( 'gravityflow_step_complete', 'get_registered_user', 10, 4 );
function get_registered_user( $step_id, $entry_id, $form_id, $status ) {
	//Field 3 = Email
	//Field 11 = User Field
	// ensure correct step id
	if ( $step_id == '205' ) {
        	// get the entry details
        	$entry = GFAPI::get_entry( $entry_id );
        	// get user by email input
        	$user = get_user_by( 'email', $entry[3] );
        	// update the user ID in the hidden user field if it matches
		if ( $user ) {
	        	GFAPI::update_entry_field( $entry_id, '11', $user->ID );
		}
	}
}

```

Cheers,  
Jamie