Saving Rise Source Files to Local Hard Drive

I don't think anyone here is requesting offline editing.  What we're asking for is CONTROL of our own intellectual property, so that it can be passed along to clients or to our successors if we move on.  I have a repository (on our own servers, with our own security) of all of my authored content.  When I move on, someone else will gain access to that repository.

No one here is asking for the keys to the kingdom.  We're asking for a source file that WE can store locally, so that WE are responsible for its security, so that WE always know where to find it and can send it on to a client at the end of a contract or can pass it to our successor in a way that WE think makes sense.  If that file then has to be edited in the cloud with a valid Rise 360 subscription, that's fine - it's no different than my successor having to buy the software used to create any other initial file.  But not to allow us to control our own intellectual property is clearly a problem for a lot of us, and will result in us not utilizing Rise 360 (however useful a product it may be).  

I want to store all of my content in ONE place, so no one has to wonder where it is.  ALL OF IT.  And I want my security people to control who sees it, and who can edit it.  How it gets edited depends on the type of file - and a Rise 360 file which is only editable with a valid subscription is absolutely fine with me.  

I'll add another voice into the mix.  We switched to Articulate 360 last year, and have been using Rise 360 a lot in the past few months.  A few weeks ago, one of our Rise courses mysteriously disappeared - the published content was gone, resulting in a 'Hmmm, we can't find what you're looking for' message to the user, who reported it to us.  When we viewed the link, it was gone - and when we went to re-publish, we found the source file was also missing.  

Articulate Support was unable to locate the source file and insisted that we must have deleted it - which we didn't.  The course had been stable and working from December, had not been modified or updated, none of my team had touched it.  Yet it was gone.  Because nothing was stored locally or backed up, we didn't even have the published version to refer to - we had to re-create the entire module from scratch.

Obviously this had made me extremely motivated to not only backup all of my content, but to deliver it from our own servers and not through Articulate servers.  If I can't depend on the content being stable, and if files are just going to disappear and I can't back them up, it's not a reliable solution for us.

So... what exactly is Articulate suggesting that I do?  Send a copy of every file to myself, and manage the duplicates?  I hope you realize this isn't a viable solution.  We need a way to store and/or backup our content.  Make it editable only through a valid Rise 360 subscription, for sure - but if you can't guarantee that my content is stable, especially if you can't recover something that has disappeared (for whatever reason), you need to provide me with a way to back it up and store it on my own server.

I agree--I would love to be able to give the source files to clients! A client hired me to create a few RISE courses, and the application is so new I don't think either one of us thought about the issue of source files.

After I delivered the published files, I realized that the client will not have access to be able to make even minor changes on this course, unless they go through me. That's not acceptable to me!

Also, I can't guarantee I will subscribe to 360 next year. As a freelancer, it will depend on whether there is client demand. 

This is not really a viable solution. We're working with a Fortune 50 company, and they are strongly advising away from Articulate Rise and fully supporting competing platforms -- for this very reason.  For these larger corporations, investing in courseware development -- only to then have it not archivable, not retrievable, not transferrable outside this platform -- is a deal killer; we're seeing it first-hand.  You have a decent product.  I hate to see it bested by the likes of Elucidat et al.  My strong recommendation:  Get it on the feature roadmap, ASAP. 

5 years ago, this was 'on the roadmap' but for some reason it is no longer. Articulate seems to be missing the point of the request - and on purpose. I see continued comments from staff about not really understanding the purpose of the request and offering non-work-arounds - this is disingenuous. It's strong-arm strategy for sales.

My clients need the source files - not the web or the pdf version, or the media files but the actual source copy that they could upload to Rise for editing after a buying a subscription. They need the security of knowing that if they become unhappy with my services, I can't hold their courses hostage because I'm the only one with access to the material through my Articulate account. They need ownership and control of their intellectual property.

I need the source files - for archiving offline in case you somehow lose the data on your servers. As a professional it's irresponsible for me to not have some sort of redundancy built in for my data and content, but your platform prevents me from fulfilling this basic responsibility. 

I'm concerned with the ease with which one can absentmindedly delete an Articulate Rise project from the dashboard. Is there a way to archive a project away from the main page? I'd love to have an alternate back up location.

I work for a Healthcare company that is really tight with IT security and we would need to be able to definitely need to load or store the files on our company's servers.  If it would be possible to at least create a package to be saved locally and then upload if needed to use RISE for changes.  My team has multiple accounts with 360 so that is not the issue,  It is being able to secure the files locally that would be our IT security's preferences. 

As a company that likes to ensure the safety and security of the training it creates, it feels like a misstep to rely on a full web integration product.  I believe it would be helpful to create a package file of the rise course so that it could be removed from the web version and stored on locally behind our company's firewall.  Any time changes should be made we could re-upload the file to rise and make are changes.

It would be great to set this functionality added.

Steve

Please count one more voice clamoring for the ability to save a local source file! I work on a team of administrators supporting a team of instructional designers in a heavily regulated industry, and we're just looking into Rise as it really makes for elegant learning materials. We're looking at developing more using Rise as opposed to Storyline, however the cloud-based structure of Rise does give us pause.

The big questions for us are: What do we do when a regulator requests all of our training materials post-incident? How do we track and control versions? The PDF feature seems like a good fit for tracking versions (make a course, PDF it, file it; revise a course, PDF the new version, archive that, etc.), and the ability to create preview links just like we do in Storyline 360 should enable us to let a regulator view the course nearly in situ. I guess we could 'Create a Copy' every time we want to revise the course so that each version would be distinct and accessible at a later date to fit this function. I'm not sure managing some 1500+ courses in the Rise home page is going to be as effective (or fun!) as our in-house filing system, however it seems there's enough noise being generated in favor of a downloadable source file feature that we will likely be able to get the best of both worlds soon enough.

Wondering if it is possible to download the source file package yet, and re-upload for future edits? We have confidential content that our IT is not comfortable with hosting on your server. I see you had submitted a request 9 months ago - has anything been done in this regard? Without it, we won't be able to use Rise for most of our eLearning, as our security protocols require sensitive data to be hosted in-house. Thank you!