Please follow the step-by-step guide below to resolve common issues around<\/strong> user login<\/strong>.<\/p>\n Possible issue descriptions or questions could be:<\/p>\n In the MediaStore admin site, go to Users<\/em> and search for the user’s email address<\/strong> to find any matching account. Please also apply the Include Deleted<\/em> filter<\/strong> to search through deleted accounts as well. Also try searching for the user’s name in case the email address yields no matches.<\/p>\n a. If no account exists, ask the user to register or send them an invitation. In the list view, you will be able to review the account’s Status<\/strong>.<\/p>\n a. If the account is Deleted<\/em>, please use Actions<\/em> > Restore<\/em> restore it. After restoring, it will have one of the status listed directly below – please proceed accordingly. If the user cannot login after step 2<\/em>, ask them to use the password recovery<\/strong> function near the login prompt to retrieve a password reset link. (Note that we do not have access to clients’ passwords and cannot retrieve any passwords for you or the user.)<\/p>\n a. If the user receives the password recovery email, usage of the password recovery function should allow them to set a new password and login. Note that, if the user has requested a password recovery email but has not received it, it has most likely ended up in the user’s spam folder, so ask the user to check this. It also makes sense to double-check that the account’s email address is correct. Client users should typically log in via your client-facing site’s public login form<\/strong>. Internal users intending to use the admin site should use the separate admin site login page.<\/p>\n a. If the user is not using the correct login form (this could also be the case e.g. if the user attempts to reuse their user invite after already having activated the account), point them to the public login form, where they should be able to log in. Issues with login may arise due to the browser or internet connection<\/strong> used by the user.<\/p>\n a. Ask the user to try logging in using a different browser. Troubleshooting: User login: introduction Please follow the step-by-step guide below […]<\/p>\n","protected":false},"author":9,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[520],"tags":[],"class_list":["post-4229","post","type-post","status-publish","format-standard","hentry","category-troubleshooting-v2-user-guide"],"_links":{"self":[{"href":"https:\/\/mediastore.support\/index.php?rest_route=\/wp\/v2\/posts\/4229","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/mediastore.support\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/mediastore.support\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/mediastore.support\/index.php?rest_route=\/wp\/v2\/users\/9"}],"replies":[{"embeddable":true,"href":"https:\/\/mediastore.support\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=4229"}],"version-history":[{"count":14,"href":"https:\/\/mediastore.support\/index.php?rest_route=\/wp\/v2\/posts\/4229\/revisions"}],"predecessor-version":[{"id":4407,"href":"https:\/\/mediastore.support\/index.php?rest_route=\/wp\/v2\/posts\/4229\/revisions\/4407"}],"wp:attachment":[{"href":"https:\/\/mediastore.support\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=4229"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/mediastore.support\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=4229"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/mediastore.support\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=4229"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}\n
1. Does the user have an account?<\/h3>\n
\nb. If there is an account already, but under a different email address, ask the user to try logging in with this, or update the account’s email to the user’s up-to-date one.
\nc. If there is an account already and it matches the email address the user used during the login attempt, proceed to step 2<\/em>.<\/p>\n2. Check the user account’s Status<\/h3>\n
\nb. If the account is Inactive<\/em>, Pending<\/em> or Invited<\/em>, the user does not have access yet. This could be because they registered or were invited but didn’t finish signup, or because the user was set up as an inactive contact entry only. To give the user access, you may (re)send a user invite by using Actions<\/em> > (Re)Invite<\/em>.
\nc. If the account is Active<\/em>, they have an account including a password and should be able to log in. If this does not succeed, proceed to step 3<\/em>.
\nd. For other user Status details, please see here<\/a>.<\/p>\n3. Ask the user to set a new password<\/h3>\n
\nb. If the password recovery email has not arrived at all, retrieve it from the MediaStore maillog (if you have access) or ask us to provide it. (Also note that users should avoid common words or phrases and, based on your MediaStore implementation, other password requirements may be in place.)
\nc. If the user still cannot log in even though they have an Active<\/em> account and know their password by now, proceed to step 4<\/em>.<\/p>\n4. Verify how the user attempted to login<\/h3>\n
\nb. If the user is using the correct login form and still cannot log in, proceed to step 5<\/em>.<\/p>\n5. Rule out web browser and connection issues<\/h3>\n
\nb. Ask the user to attempt login via a different internet connection, e.g. a mobile or private network.
\nc. If the issue persists across multiple browsers and connections, ask the user for details (including versions) of browser and operating system, and get in touch with us.<\/p>\n","protected":false},"excerpt":{"rendered":"