Forum Discussion
NEW IN ARTICULATE 360 TEAMS: Transfer Content
Today we released a new feature that’s just for Articulate 360 Teams: transfer content. Now it’s easy to maintain control of your content when team members change.
The new transfer content feature...
Hi everyone!
We are excited to share that we have released Rise 360 Team Folders! You can now create shared team folders in Rise 360 to organize your content and share content with collaborators even faster. We know this has been a popular feature request and we can't wait for you to finally check it out!
Your Rise 360 dashboard will look a little different, but don't worry. You can find all of your content, personal and shared, in the My View section. If you run into any snags or have additional questions about Rise 360 Team Folders, our team is available in this discussion or in a support case.
While I appreciate that this feature is useful when permanently removing a user from a team, in the case of the team I work in it is proving to be problematic. We swap seats quite regularly, as different members of our team require Articulate 360 access at different times. I believe this is a common situation for many Articulate 360 customers.
Since the introduction of this feature we have encountered issues with content being assigned elsewhere or - worse - deleted accidentally when team members are swapping seats. The fact that it is possible to permanently delete Rise/Review content from the pop-up, with no possibility of recovery, is extremely risky. The current system puts users in a position where they could easily delete sensitive and important work with no warning that this is irreversible, or transfer content without a paper trail to follow. Again, this poses a real problem when swapping seats on a regular basis.
I've already submitted a feature request to change the default of the pop-up to 'Nothing - just remove user from team', as we believe that would significantly reduce the amount of mistakes made. But I wanted to reiterate here the gravity of making an error when swapping seats, and draw this to the attention of the community and development team.
