Help & Reference

Your profile

Your profile holds the name and email address attached to your account. Both live in the Your Profile section of the Settings page.

Open your profile

  1. Tap mirepoix in the navigation bar and choose Kitchen settings.
  2. Scroll to Your Profile near the bottom of the page.

If you’re signed in but not a member of any kitchen, the landing page links to a standalone Edit your name form at /profile/edit. That form covers name only — to change email from there, accept a kitchen invitation first.

Change your name

  1. Edit the Name field.
  2. Tap Save changes in the page footer.

The new name shows up beside your row in the Members list and as the inviter line in any invitation emails you send.

Change your email

Email lives behind a verification step so a stolen session can’t redirect your sign-in codes.

  1. Tap Change email next to your current address.
  2. Type the new address in the New email field.
  3. Tap Send verification.

mirepoix sends an 8-character code to the new address. The code is good for 10 minutes and can be used once.

To finish the change:

  1. Open the inbox at the new address and copy the code.
  2. On any device, open /session/new and enter your sign-in email.
  3. On the code-entry page, paste the verification code and tap Sign in.

The change applies the moment you confirm. mirepoix then sends a notification to the old address so you’d notice if someone changed your email without your knowledge.

If the new address is already in use

The verification page returns: That email address is already in use. Request a new code with a different address. Pick a different address and start over.

If you hit a rate limit

mirepoix caps email-change requests at 3 per hour per account. After the third, Send verification returns a Could not send verification error. Wait an hour and try again.

Why the two-step flow

If someone got hold of your sign-in session, they could otherwise change your email and lock you out. The verification step blocks that. Even with your session, an attacker would also need to read the code at the new address and ignore the notification sent to the old one.

See also