Support registration & login via email

[paulo-rossy]

Hello team!

At the moment the project supports user sign-up and authentication only by phone number.
In my country most suppliers (employees) rely exclusively on email for communication and account access, so they cannot use the current flow.

Could you please add full email support, including:

1. Account creation with an email address.
2. Email-based login (password or magic-link flow).
3. Ability to invite / add users by email.

This would make onboarding our local suppliers much smoother.
Thanks for considering the enhancement!

[pahaz]

Hi there,

Thank you for raising this! We completely understand that email-only workflows are the norm for many suppliers, and we want to make their onboarding as smooth as possible. To deliver full email support we’ll tackle the feature in three parallel steps:

1. Invite employees by e-mail
   Action: Extend the inviteNewOrganizationEmployee endpoint so it accepts email (in addition to—or instead of—phone).
   Proposal: We can introduce an environment variable, e.g. INVITE_REQUIRED_FIELDS, that lets you declare which identifiers (email, phone) are mandatory in your deployment. That way the same codebase adapts to different markets.

2. E-mail-based login (in progress)
   Our auth module is being updated to support password-based login (with “Forgot password” reset action).

3. E-mail confirmation (in progress)
   New users who sign up or are invited by e-mail will receive a verification link to activate their account and unlock full access.

---

How you can help right now

If you’d like, we can try to fix the inviteNewOrganizationEmployee mutation. Once the endpoint accepts e-mails, your team can start inviting employees, while the login & confirmation features roll out behind the scenes.

Let us know if this plan works for you or if you’d prefer a different approach. We’re happy to align on timelines and the exact shape of the INVITE_REQUIRED_FIELDS switch.

Here are three illustrative values for the INVITE_REQUIRED_FIELDS environment variable, assuming we store the required identifiers as a comma-separated list (use JSON or another format if your config system prefers):

Scenario	Meaning	Example value
1️⃣ Phone only	The invite must include a phone number; e-mail is optional.	INVITE_REQUIRED_FIELDS=phone
2️⃣ E-mail only	The invite must include an e-mail address; phone is optional.	INVITE_REQUIRED_FIELDS=email
3️⃣ Phone and e-mail	Both identifiers are mandatory in the invite payload.	INVITE_REQUIRED_FIELDS=phone,email