Retain Ownership of Rise Courses in Large Teams with Staff Turnover

Hi Forum,

I'm wondering how organisations with a large number of developers (and courses) manage & retain access to courses built in Rise, as employees leave the organisation or change roles.

Deploying a "Send-a-copy of Rise projects which need to be retained, to another person in the Team, before leaving the organisation" is one possible solution - however the overhead to manage this increases along with the number of staff & courses - and there is a risk of losing the courses if the policy is not properly enforced.

Adding other authors as collaborators does not allow the secondary authors rights to publish the course - so this is not a viable solution either.

Wanted some feedback from the community - how are other large organisations currently handling this?