Saving Rise Source Files to Local Hard Drive

I guess I'll throw my 2 cents in with the hope it will add another voice. I've been working on convincing my leadership to move to Rise for months now. I believe I had a breakthrough this last week only to realize we can't control source files. This may be the deal breaker for us as well. 

I also regret having proposed to and developed courses in Rise for my clients; now I don't know how to explain to them that they will have to keep an active subscription just to avoid the source files from being deleted.  A total disappointment.

I also need a way to save the source file on a local hard drive badly.

Why? 

In our company (13.000 employees) I am currently the owner of the Articulate 360 Teams Account. Soon this Teams Account will be extended to minimum 20 seats. I will be the only one of these people who will have a permanent license for now. The other seats will be switched around as needed. 

1. I will loose overview if in the years to come everyone creates more and more Rise Courses and they all have to sit in my dashboard because I am the only one with a permanent license. The way it is now I already have 28 courses sitting in my dashboard and we only have had this software for 3/4 of a year. 

2. It would make the process of sharing a course back an forth way easier if I don't have to be the only person in the whole company that "owns" them. 

3. It is super insecure for everyone if we can't save the files. Whenever I should have a problem with my account it will be a super scary moment in which we could loose many important courses. I get the shivers just thinking about it.

It would obviously help a lot of people if you could come up with da file that we can save on a local hard drive and open up later from a different account again. 

Aileen 

Like Cass says, if you follow that system you'll be probably okay. We've had people come and go over the past couple years, and so far the only real issue is the connection between the Rise "file" and it's respective Review view mode/hyperlink. You'll break any review links when you transfer ownership. They'll still work for reviewers, but if you publish a new version for review, you'll need to resend the link - it also "overwrites" all comments up to that point, since it actually publishes a new version of the Review version of the course, totally separate from what people have already been looking at.

Plus one for this feature request please ... 

Is it still on the roadmap as I note some of the replies are from 2 years ago?

Within our business we have quite a few developers who can pick up a Storyline source file and edit the content at any time (without the need for sharing etc.) ... this means that if the original developer is off on holiday etc. work doesn't have to wait for sharing. 

I appreciate that not providing source files gives a certain benefit to Articulate, in that people will be less likely to allow their subscription to lapse ... but the worry for the developer here (employed by a business who have a procurement team) is that the procurement process doesn't go to plan, a subscription lapses for a short period and all source content (and templates) are lost. This exact scenario happened to us recently for another online provider we use and this cost us quite a bit of time / money.

Any updates would be appreciated?

Hey Paul,

I appreciate the insight you've shared. While downloadable source files are not on our feature roadmap, I did want to mention that your courses will remain intact on our servers for at least six months after your trial or subscription expires. If you renew your subscription during that time, you'll have access to all your courses again.

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. 

My major client gave up on Rise for exactly the reasons Peter mentioned.  Can you picture your PowerPoint files cannot be shared offline and will disappear without an annual fee to Microsoft?

Really appreciate your reply Alyssa ... it's a relief to know content won't be lost within 6 months like our other supplier.

If you could pass on my thoughts I'd really appreciate it. Whilst I can understand the business case for removing this feature from your roadmap, and I still use Rise, I'm in a particular position. I work for a business who has a procurement team and my licence is maintained by the business I currently work for.

If I were to do freelance work in the future - it would very difficult to justify designing in Rise and handing over only published content whilst explaining to any client that they will need to make ongoing payments to me - to maintain a source file. For this reason I see the none source file approach as pretty much ruling out the use of Rise for freelance work (a decision which I'm sure will affect subscription levels, for what i see, as one of the best online authoring tools around).

Hi Paul,

Although not optimal, you could send a copy of the Rise source to a client at the end of your contractual work. Granted that would require someone on your client's team to have an Articulate/Rise 360 license and maintain, but that gives them ownership over the source (well a copy of it) that is unique and can be updated at their discretion. If necessary, they can contract another freelance person w/ a 360 license and send a copy to them to make updates.

As I mentioned, not necessarily optimal-- but negates the need to have you be the primary gatekeeper of the project's source file once the work is complete.