Forum Discussion

RenaeFlegg-7602's avatar
RenaeFlegg-7602
Community Member
3 months ago

Sharing between Rise360 and Rise

Hi all. I have a client with a Rise (LMS) licence who would like me to send a copy of the course I built in my Rise360 account.

I've shared courses between Rise360 accounts many times, but when I entered the email address attached to their Rise (LMS) account, it says: Failed to send copies to the following emails, please ensure that they have valid accounts in your regional data center:

So I guess my question is can you transfer between Rise360 and Rise?

  • Hi RenaeFlegg-7602!

    Happy to help with this!

    It appears you and your colleague’s accounts are hosted on different data centers. Transferring course content between the U.S. and EU data centers is not currently available. However, the ability to migrate is planned as a part of our official production launch.

    Please let me know if you have any more questions! 

    • PaulBrennan-a29's avatar
      PaulBrennan-a29
      Community Member

      Hi there.  I have a similar problem.  I want to share a Rise360 source file with a client but their data center is in a different region to mine.  Is there a way to change the data center region setting so that I can share the file with them?  

      • RenaeFlegg-7602's avatar
        RenaeFlegg-7602
        Community Member

        In the end I exported the SCORM file and sent it to them to import into their Rise LMS which worked. 

  • I am having the same issue. Both my client and I are in the US so not understanding why I can't send a copy. I didn't have any issues until I upgraded to a Teams account. 

    • KellyAuner's avatar
      KellyAuner
      Staff

      Hi, JenniferThomas!

      Thanks for reaching out and I'm sorry to hear you've hit this snag. I see you've connected with my teammate, Dexter, in a support case. We'll continue troubleshooting there!

      • JenniferThomas's avatar
        JenniferThomas
        Community Member

        Thanks Kelly - thanks to Dexter, we were able to solve the issue! We needed to verify which emails were used for the Articulate IDs.