Forum Discussion

JenniferBeasley's avatar
JenniferBeasley
Community Member
2 months ago

Review 360 Link

I have an SME we provided a review link to. It is not a private link. When she accesses the link, she is asked to sign-in to her Articulate account instead of it gong directly to Review 360. Trying to avoid having her have to create an Articulate account. 

Has anyone else come across this problem? It's happened to us previously with a different individual. 

5 Replies

    • LucianaPiazza's avatar
      LucianaPiazza
      Staff

      Hello FamiliezorgO-Vl​, 

      I understand that you're also running into an issue where your reviewer is being prompted to sign in to access the Review 360 item, and the suggestions shared earlier haven't resolved it.

      Just to clarify expectations, reviewers don't need an Articulate 360 creator license to view a private Review 360 item. However, if the item is set to Only invited users, they do need to sign in with an Articulate ID. If they don't already have one, they can create a free account.

      If you have any other questions or are looking for something different, please let us know in this thread or privately in a support case. 

  • tomm8033's avatar
    tomm8033
    Community Member

    Double-check the share settings in Review 360 and make sure Item Access is set to “Anyone with the link” (not “Only invited users”) and that the box for “Allow users without Articulate IDs to comment” is checked, then generate and send a fresh link. Ask her to open it in an incognito/private window or a different browser—cached sessions or an email already tied to an existing Articulate ID are the usual culprits that force a sign-in prompt even on a public link.

    • AnneMiesel's avatar
      AnneMiesel
      Community Member

      I have been having issues and have found for me, being sure to have the course set to "Anyone with a link" and "Allow users without Articulate IDs to comment" being checked and opening the link in a private/incognito window as well as filling in a fake email worked for me.  I'm waiting to hear back from a reviewer to see if that is workaround