QFieldCloud Feature Requests

It would be very useful to know which users have a project downloaded to a device, or if it has been removed from a device. When an update is required it would allow us to contact them and tell them to sync and remove before updating.

It'd be useful to allow input of an email to send monthly invoices to (i.e. to accounts dept)

With a "Offline" configuration of an attachment layers, the attachments folder (for instance DCIM) is synchronised with the cloud when update are done in the layer. Now, if the attachment layer is in "Direct access", the attachment folder (DCIM) is not synchronised with the cloud. It would great if we could either: * Force push the entire folder (now we can force push each file/image) * The folder can be synchronised with the "Push modifications" buttons

As a project admin I would like to add multiple members and their role via a list/csv file.

As a project admin, I want to receive email notifications in case of errors such as delta apply failures, job failures, or when the project status turns red, So that I can quickly respond to these issues, prevent data loss, and maintain the smooth operation of the project.

We have had a few occasions where data is lot because a QFieldCloud project has become corrupted on a device. Once this happens there is no way of accessing the files from a project (unlike QFieldSync in which the files can be accessed without opening a project). With a corrupt QFieldCloud project we are unable to access the project settings because it is only possible to do so once a project is open. Ideally we could access the edited gpkg files stored on a device without having to attempt to open a project.

As a QFieldCloud user, I want to exclude certain files from file versioning or protect them from getting updated, so that my storage is not quickly filled up by layers that are not editable and should not be updated every time the project is synchronized.

Would be great if we had the ability to download WFS or WMS maps for an area, knowing service won't be great.

We work with light data (as vector and geopackage files) and very heavy data (rasters, aerial orthophotos, etc...). Heavy data are used as basemap and they don't need to be updated. Light data are used from field workers, they are editable and they need to be updated on cloud. It could be great to have a QfieldCloud project on device with different "file destination" data where: some data are copied in device (heavy rasters, etc...) some data are synchronized on cloud (editable files, field data, vectors, etc...).

Would be awesome to have a WearOS app that mainly works with the Qfield App but also has the ability to work standalone on the WearOS device : )