Hot answers tagged wording
Start with the purpose of the notification.... Usually, notifications are created to inform the user that something has happened. Therefore, the primary UX goal is to convey that information. Usually, getting the user to take action (e.g. reply, dismiss, approve) is a secondary UX goal, because it's hard for the user to take action without first reading ...
Token is a good term for it. This is what OWASP (the open web application security project) refers to it as. You may want to look at the owasp guidelines for forgotten password - https://www.owasp.org/index.php/Forgot_Password_Cheat_Sheet It is very deliberately not called password as you should never send a password via email. Tokens are usually used to ...
There are several terms used for this: Token (or verification token) One-time password (or OTP) Temporary password Verification code Validation code They are loosely interchangeable. In your case, if the system sets the password and it's persistent (Ie the user doesn't change it except to request another system-assigned password) then it's probably ...
I think the term you are looking for is "Verification code" Here are some examples
Users have gotten used to the fact that a notification is clickable, so based on that I don't think you need to add text like "click here to answer Tom". Users expect a notification to be clickable by default, so "Tom posted a new comment" should be enough.
Only top voted, non community-wiki answers of a minimum length are eligible