Flywheel considers data that has entered the system through a device to be of a higher importance than data created by Gears or uploaded by Users. device data is often data from a medical device and, in some cases, does not exist in long term storage anywhere but Flywheel.

Due to this lack of redundancy or ability to recreate this data via a Gear run, permissions around deleting device data are handled separately from permissions for deleting other files in Flywheel. For example, if a user wishes to delete a Subject that has an Acquisition containing device data, this user would need both the Delete Container AND Delete Device Data permission.

If a user would like to move a container, they would need the Create Container permission in the destination project and the Delete Container permission in the source project. Device data (described above) is not considered as the user will not be removing the data from the system.

To delete or remove a custom role, you must re-assign all users with that role.

You can assign multiple Project roles to the same user. If the two roles have conflicting permissions, Flywheel uses the enabled permission. For example, if one role restricts viewing files and the other role allows it, the user will be permitted to view files.

In this example, there is a user who is working on developing a new gear for your project. This user should be able to upload, test, and run gears in your Project. However, they do not need to create containers or run reports.