Personal drive

As part of the move to the new VU.CITY platform, personal drives belonging to organisation members are migrated from Legacy to the new platform. Migration copies the contents of each personal drive so they remain accessible in the new platform.

Migrated personal drives are placed in the organisation’s root folder, inside a folder named Migrated Personal Drives <date>, <time>. The date and time indicate when the migration took place. Only the files present in each personal drive at that time are copied, so files added to a Legacy personal drive after the migration are not included.

Inside this folder, each migrated user has a separate folder named after them. Each folder contains the contents of that user’s personal drive, with the original folder structure preserved.

• Migrated folders diagram

  

If personal drives are migrated more than once, each migration creates its own Migrated Personal Drives folder.

Who can access migrated personal drives

Each user folder has a single explicit permission assigned to the user it belongs to. This means the personal drive content remains private to that user and organisation admins.

For more information about explicit and inherited permissions, see User permissions.

What happens to the original personal drive?

Migration creates a copy of the personal drive content in the new platform. The original personal drive remains available in Legacy and is not modified.

The migrated copy and the original personal drive are independent of each other. Changes made in the new platform do not affect the Legacy personal drive, and changes made in Legacy do not affect the migrated copy.