Enable Sync on AGOL feature layers for Field Maps offline compatibility - any reason not to Enable Sync?

[Will]

Hi, our organization does a lot of work in remote disconnected areas so our staff need to take AGOL layers offline in Field Maps, which requires us to "Enable Sync" on those feature layers.  Is there any reason we shouldn't Enable Sync on all our feature layers to make them all offline compatible, or is there some performance reason to not Enable Sync on some layers?    Also, is there any way for end users (who aren't admins or owners of a layer) to easily see if a layer is offline compatible, i.e. it doesn't seem like they can tell.. so  we're thinking of adding metadata tags like "offline-enabled" to make such layers discoverable.. any other thoughts or ways to handle this?  Thanks.

[MarkBockenhauer · Accepted solution]

With regard to performance Sync can be an issue when you have thousands of users 'sync-ing' at the same time. Enabling sync for the layer is not an issue.  Using map author defined offline areas with scheduled updates provides the best performance if you have larger numbers of field workers.  Also, for the second part of your question, your field maps users will see the map areas that are available for offline use.   This does require the map owner to create the offline areas (offline maps) the field workers will need.  If you have lower numbers of field workers enabling sync and using on demand offline workflows should not be a problem.  You may want to create a group for your offline maps, and share the offline-able maps via the group with your field workers.  Field Maps user can access the maps through the group in the app.