> ## Documentation Index > Fetch the complete documentation index at: https://stytch.com/docs/llms.txt > Use this file to discover all available pages before exploring further. # Reset by Email Start > Start password reset by email using the Stytch Next.js SDK `passwords.resetByEmailStart` wraps the [Reset By Email Start](/docs/api-reference/b2b/api/passwords/create-or-reset-options/password-reset-by-email-start) Password API endpoint. This endpoint initiates a password reset for the email address provided. This will trigger an email to be sent to the address, containing a magic link that will allow the member to set a new password and authenticate. ## Parameters The email address of the Member. Globally unique UUID that identifies a specific Organization. You may also use the `organization_slug` or `organization_external_id` here as a convenience. The URL that the Member clicks from the reset password link. This URL should be an endpoint in the backend server that verifies the request by querying Stytch's authenticate endpoint and finishes the reset password flow. If this value is not passed, the default `reset_password_redirect_url` that you set in your Dashboard is used. If you have not set a default `reset_password_redirect_url`, an error is returned. The URL that Members are redirected to upon clicking the "Log in without password" button in password reset emails. After Members are redirected to the login redirect URL, your application should retrieve the token value from the URL parameters and call the [Magic Link Authenticate endpoint](/docs/api-reference/b2b/api/email-magic-links/organization/authenticate-magic-link) to log the Member in without requiring a password reset. If this value is not provided, your project's default login redirect URL will be used. If you have not set a default login redirect URL, an error will be returned. Sets a time limit after which the email link to reset the member's password will no longer be valid. The minimum allowed expiration is 5 minutes and the maximum is 10080 minutes (7 days). By default, the expiration is 30 minutes. Use a custom template for reset password emails. By default, it will use your default email template. Templates can be added in the [Stytch dashboard](https://stytch.com/dashboard/templates) using our built-in customization options or custom HTML templates with type “Passwords - Reset Password”. Used to determine which language to use when sending the user this delivery method. Parameter is an [IETF BCP 47 language tag](https://www.w3.org/International/articles/language-tags/), e.g. "en". Supported languages are English ("en"), Spanish ("es"), French ("fr") and Brazilian Portuguese ("pt-br"); if no value is provided, the copy defaults to English. ## Response The ID of the Member. The ID of the Member Email. Globally unique UUID that identifies a specific Organization. Globally unique UUID that identifies a specific Member. The ID of the Member given by the identity provider. The email address of the Member. Whether or not the Member's email address is verified. The status of the Member. The possible values are: `pending`, `invited`, `active`, or `deleted`. The name of the Member. An array of registered SAML Connection or OIDC Connection objects the Member has authenticated with. Globally unique UUID that identifies a specific SSO `connection_id` for a Member. The unique ID of an SSO Registration. The ID of the Member given by the identity provider. An object for storing SSO attributes brought over from the identity provider. Sets whether the Member is enrolled in MFA. The id of the SCIM Connection. The unique ID of a SCIM Registration. The ID of the Member given by the identity provider. An object for storing SCIM attributes brought over from the identity provider. Identifies the Member as a break glass user - someone who has permissions to authenticate into an Organization by bypassing the Organization's settings. A break glass account is typically used for emergency purposes to gain access outside of normal authentication procedures. Refer to the [Organization object](/docs/api-reference/b2b/api/organizations/organization-object) and its `auth_methods` and `allowed_auth_methods` fields for more details. Globally unique UUID that identifies a Member's password. A list of OAuth registrations for this Member. Denotes the OAuth identity provider that the user has authenticated with, e.g. Google, Microsoft, GitHub etc. The unique identifier for the User within a given OAuth provider. Also commonly called the sub or "Subject field" in OAuth protocols. If available, the `profile_picture_url` is a URL of the User's profile picture set in the OAuth identity provider that the User has authenticated with, e.g. Google profile picture. If available, the locale is the Member's locale set in the OAuth identity provider that the user has authenticated with. The unique ID of an OAuth registration. Sets whether the Member is enrolled in MFA. If true, the Member must complete an MFA step whenever they wish to log in to their Organization. If false, the Member only needs to complete an MFA step if the Organization's MFA policy is set to `REQUIRED_FOR_ALL`. The Member's phone number. A Member may only have one phone number. The phone number should be in E.164 format (i.e. +1XXXXXXXXXX). Whether or not the Member's phone number is verified. A list of retired email addresses for this Member. A previously active email address can be marked as retired in one of two ways: * It's replaced with a new primary email address during an explicit Member update. * A new email address is surfaced by an OAuth, SAML or OIDC provider. In this case the new email address becomes the Member's primary email address and the old primary email address is retired. A retired email address cannot be used by other Members in the same Organization. However, unlinking retired email addresses allows them to be subsequently re-used by other Organization Members. Retired email addresses can be unlinked using the [Unlink Retired Email endpoint](/docs/api-reference/b2b/api/members/unlink-retired-email). The globally unique UUID of a Member's email. The email address of the Member. An arbitrary JSON object for storing application-specific data or identity-provider-specific data. An arbitrary JSON object of application-specific data. These fields can be edited directly by the frontend SDK, and should not be used to store critical information. See the [Metadata resource](/docs/api-reference/b2b/api/resources/object-update-behavior) for complete field behavior details. Explicit or implicit Roles assigned to this Member, along with details about the role assignment source. See the RBAC guide for more information about role assignment. The unique identifier of the RBAC Role, provided by the developer and intended to be human-readable. Reserved `role_ids` that are predefined by Stytch include: * `stytch_member` * `stytch_admin` Check out the [guide on Stytch default Roles](/docs/multi-tenant-auth/enterprise-ready/rbac/create-rbac-policy#default-roles-and-resources) for a more detailed explanation. A list of sources for this role assignment. A role assignment can come from multiple sources - for example, the Role could be both explicitly assigned and implicitly granted from the Member's email domain. The type of role assignment. The possible values are: * `direct_assignment` – an explicitly assigned Role. Directly assigned roles can be updated by passing in the roles argument to the Update Member endpoint. * `email_assignment` – an implicit Role granted by the Member's email domain, regardless of their login method. Email implicit role assignments can be updated by passing in the `rbac_email_implicit_role_assignments` argument to the Update Organization endpoint. * `sso_connection` – an implicit Role granted by the Member's SSO connection. This is currently only available for SAML connections and not for OIDC. If the Member has a SAML Member registration with the given connection, this role assignment will appear in the list. However, for authorization check purposes (in sessions authenticate or in any endpoint that enforces RBAC with session headers), the Member will only be granted the Role if their session contains an authentication factor with the specified SAML connection. SAML connection implicit role assignments can be updated by passing in the `saml_connection_implicit_role_assignments` argument to the Update SAML connection endpoint. * `sso_connection_group` – an implicit Role granted by the Member's SSO connection and group. This is currently only available for SAML connections and not for OIDC. If the Member has a SAML Member registration with the given connection, and belongs to a specific group within the IdP, this role assignment will appear in the list. However, for authorization check purposes (in sessions authenticate or in any endpoint that enforces RBAC with session headers), the Member will only be granted the role if their session contains an authentication factor with the specified SAML connection. * `scim_connection_group` – an implicit Role granted by the Member's SCIM connection and group. If the Member has a SCIM Member registration with the given connection, and belongs to a specific group within the IdP, this role assignment will appear in the list. SCIM group implicit role assignments can be updated by passing in the `scim_group_implicit_role_assignments` argument to the Update SCIM connection endpoint. An object containing additional metadata about the source assignment. The fields will vary depending on the role assignment type as follows: * `direct_assignment` – no additional details. * `email_assignment` – will contain the email domain that granted the assignment. * `sso_connection` – will contain the `connection_id` of the SAML connection that granted the assignment. * `sso_connection_group` – will contain the `connection_id` of the SAML connection and the name of the group that granted the assignment. * `scim_connection_group` – will contain the `connection_id` of the SAML connection and the `group_id` that granted the assignment. Whether or not the Member has the `stytch_admin` Role. This Role is automatically granted to Members who create an Organization through the discovery flow. See the [RBAC guide](/docs/multi-tenant-auth/enterprise-ready/rbac/create-rbac-policy) for more details on this Role. The date and time the Member was created. The date and time the Member was last updated. Globally unique UUID that is returned with every API call. This value is important to log for debugging purposes; we may ask for this value to help identify a specific API call when helping you debug an issue. The HTTP status code of the response. Stytch follows standard HTTP response status code patterns, e.g. 2XX values equate to success, 3XX values are redirects, 4XX are client errors, and 5XX are server errors. ```jsx theme={null} import { useState } from 'react'; import { useStytchB2BClient } from '@stytch/nextjs/b2b'; export const ResetPasswordStart = () => { const stytch = useStytchB2BClient(); const [email, setEmail] = useState(''); const startReset = async () => { const response = await stytch.passwords.resetByEmailStart({ organization_id: 'organization-test-07971b06-ac8b-4cdb-9c15-63b17e653931', email_address: email, reset_password_redirect_url: 'https://example.com/reset-password', }); console.log('Reset email sent:', response); }; return ( ); }; ```