Team Repository for Rise Project Files

Hi Patrick, 

We had this exact same issue at our org. We have about six IDs working on Rise content and it was a hassle trying to get edit access to edit docs, keep track of copies, and getting the owner to export the SCORM for LMS.

Our solution was to nominate one account to own all Rise content after development. I'm not an ID, I'm the Ed Tech that would constantly update/republish Rise content to Moodle. So my account was nominated the one account to rule them all. This Articulate account acts like a team repository. 

The general process is:

• The ID in charge of the Rise dev (initial Owner) adds everyone involved as a Collaborator.   
• The Owner ID works on Rise content as usual. Once finished, they transfer ownership to me.
• In my account, I would organise the Rise content into separate folders. Ownership is with me and I can publish to SCORM.
• If the ID needs to make changes afterward, they still can because their permission is set to Collaborator. They can notify me if they need Owner permissions back. But in the end, they transfer ownership back to me.

Housekeeping:

• We only use 'Send a copy' to share templates. If IDs were to use this function for transferring content, there would be uncontrolled versions of the same Rise course in multiple Articulate accounts. Haven't played with Block templates, but this new feature might be a substitute for us sharing templates.
• In case I get hit by a bus, my account details are available to my supervisor or another senior ID.
• As Alyssa mentioned, if a staff member leaves, make sure they transfer any Rise content they developed to the nominated account.

Hope that helps. Cheers, Alex