You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
/// - To confirm the user's email address or phone number, set ``AdminUserAttributes/emailConfirm`` or ``AdminUserAttributes/phoneConfirm`` to `true`. Both arguments default to `false`.
49
+
/// - ``createUser(attributes:)`` will not send a confirmation email to the user. You can use ``inviteUserByEmail(_:data:redirectTo:)`` if you want to send them an email invite instead.
50
+
/// - If you are sure that the created user's email or phone number is legitimate and verified, you can set the ``AdminUserAttributes/emailConfirm`` or ``AdminUserAttributes/phoneConfirm`` param to true.
51
+
/// - Warning: Never expose your `service_role` key on the client.
/// - Sends an invite link to the user's email address.
67
+
/// - The ``inviteUserByEmail(_:data:redirectTo:)`` method is typically used by administrators to invite users to join the application.
68
+
/// - Parameters:
69
+
/// - email: The email address of the user.
70
+
/// - data: A custom data object to store additional metadata about the user. This maps to the `auth.users.user_metadata` column.
71
+
/// - redirectTo: The URL which will be appended to the email link sent to the user's email address. Once clicked the user will end up on this URL.
72
+
/// - Note: that PKCE is not supported when using ``inviteUserByEmail(_:data:redirectTo:)``. This is because the browser initiating the invite is often different from the browser accepting the invite which makes it difficult to provide the security guarantees required of the PKCE flow.
0 commit comments