> ## 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.
# Get Self
> Get the currently logged-in Member using the Stytch Next.js SDK
export const setting_0 = "View membership";
export const organization = "Represents an instance or tenant in your application, typically mapping to each of your top-level customers.";
export const member = "Represents an individual end user's account within a given Organization, uniquely identified within that Organization by their email address.";
export const isReact_0 = true
{isReact_0 &&
In React, use the useStytchMember hook to easily access the currently logged-in Member and react to changes.
}
`self.get` is an asynchronous method that wraps the [get member](/api-reference/b2b/api/members/get-member) endpoint. Use it to fetch the currently logged-in Member. If no Member is logged in, this method will return `null`.
Before using this method, enable **{setting_0}** in the [Frontend SDK page](https://stytch.com/dashboard/sdk-configuration).
The Stytch SDK caches this data in local storage. Calling this method will refresh the cached data.
The Stytch SDK will invoke this method automatically in the background, so you likely won't need to call this method directly. Instead, use the [`self.getSync`](./get-self-sync) method to fetch the cached data from local storage.
## Response
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](/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](/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](/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](/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](/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.
```jsx theme={null}
import { useEffect, useState } from 'react';
import { useStytchB2BClient } from '@stytch/nextjs/b2b';
export const WelcomeMessage = () => {
const stytch = useStytchB2BClient();
const [member, setMember] = useState(null);
useEffect(() => {
const fetchMember = async () => {
const member = await stytch.self.get();
setMember(member);
};
fetchMember();
}, [stytch]);
if (member === null) {
return No member logged in
;
}
if (!member) {
return Loading...
;
}
return (
);
};
```
```json theme={null}
{
"organization_id": "organization-test-07971b06-ac8b-4cdb-9c15-63b17e653931",
"member_id": "member-test-32fc5024-9c09-4da3-bd2e-c9ce4da9375f",
"email_address": "sandbox@stytch.com",
"email_address_verified": true,
"retired_email_addresses": ["old@stytch.com"],
"status": "active",
"name": "Test User",
"is_breakglass": false,
"member_password_id": "member-password-test-32fc5024-9c09-4da3-bd2e-c9ce4da9375f",
"mfa_enrolled": false,
"mfa_phone_number": null,
"mfa_phone_number_verified": false,
"default_mfa_method": "sms_otp",
"totp_registration_id": "totp-registration-test-32fc5024-9c09-4da3-bd2e-c9ce4da9375f",
"oauth_registrations": [],
"sso_registrations": [],
"roles": [],
"trusted_metadata": {},
"untrusted_metadata": {},
"created_at": "2023-01-01T00:00:00Z",
"updated_at": "2023-01-01T00:00:00Z"
}
```