{"id":20,"date":"2026-09-09T04:25:34","date_gmt":"2026-09-09T04:25:34","guid":{"rendered":"https:\/\/nirohelp.com\/docs\/20\/client-login\/"},"modified":"2026-09-16T16:26:30","modified_gmt":"2026-09-16T10:26:30","slug":"client-login","status":"publish","type":"nirohelp_doc","link":"https:\/\/nirohelp.com\/docs\/ticket-management\/client-login\/","title":{"rendered":"Client login"},"content":{"rendered":"\n

Clients reach their tickets through one of three login methods. Pick yours under NiroHelp \u2192 Settings \u2192 Tickets \u2192 Submission \u2192 Login method<\/strong>. <\/p>\n\n\n\n

Two are passwordless; the third is a normal WordPress login.<\/p>\n\n\n\n

Method<\/th>What the client does<\/th><\/tr><\/thead>
Verification code<\/strong> (default)<\/td>Enters their email, receives a 6-digit code, types it in.<\/td><\/tr>
Magic link<\/strong><\/td>Enters their email, clicks a one-click link in their inbox.<\/td><\/tr>
Password<\/strong><\/td>Signs in, or signs up, with an email and password.<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

All three end in the same place: the client is signed in as a WordPress user holding the NiroHelp User role.<\/p>\n\n\n\n

Verification code<\/h2>\n\n\n\n
    \n
  1. The client opens Submit a Ticket<\/strong> or My Tickets<\/strong>.<\/li>\n\n\n\n
  2. Logged out, the page asks for their email.<\/li>\n\n\n\n
  3. They submit it and NiroHelp emails them a 6-digit code.<\/li>\n\n\n\n
  4. The code is valid for 5 minutes.<\/strong><\/li>\n\n\n\n
  5. They type it in and are signed in.<\/li>\n<\/ol>\n\n\n\n

    Wrong codes are counted. After 5 failed attempts the code is thrown away<\/strong> and the client has to request a new one.<\/p>\n\n\n\n

    Magic link<\/h2>\n\n\n\n
      \n
    1. Same first two steps.<\/li>\n\n\n\n
    2. Submitting the email sends them a one-click login link.<\/li>\n\n\n\n
    3. Clicking it signs them in and drops them back where they started. There is no code to type.<\/li>\n<\/ol>\n\n\n\n

      Password<\/h2>\n\n\n\n

      The form shows email and password fields, plus a sign-up panel. The sign-up panel only appears when account creation is allowed \u2014 see below.<\/p>\n\n\n\n

      This method runs through WordPress’s own login machinery, so anything you have protecting wp-login.php<\/code> \u2014 brute-force limiters, two-factor plugins, lockouts – applies here too.<\/p>\n\n\n\n

      \"submission\"<\/figure>\n\n\n\n

      Login links inside emails<\/h2>\n\n\n\n

      Whichever method you choose, every notification email that sends a client back
      \nto their ticket carries a one-click login link<\/strong>. Clicking it signs the client
      \nin and takes them straight to the conversation.<\/p>\n\n\n\n

      These links are single-use and short-lived, so a forwarded email stops working quickly.<\/p>\n\n\n\n

      Account creation<\/h2>\n\n\n\n

      A visitor whose email matches no existing account can only get in when account creation is allowed. That means one<\/strong> of these is on:<\/p>\n\n\n\n