A "Mobile Worker" user type is already able to log in to the AGO web app, and their permissions are sufficient to open maps they own in the Field Maps web app to create and manage offline areas. It seems a choice has been made that allowing a non-owner to interact with the entire Field Maps web interface would be problematic as there are many settings that need to be properly managed only by the map owner.
Offline Areas created in the web app need to be freed from this paradigm, they would be highly useful within an organization (or even share group) if they were able to be created by anyone with share access to the map and the right user type level (let's say Mobile Worker or above in this case.) This would enable non-map-owning project managers and field staff to organize their work areas on the fly and without the need to coordinate with a map's owner (who does not necessarily need to know how a field staff's work will be appropriately subdivided and assigned for offline data collection.)
This may be best accomplished by adding a blue button in the right-hand launcher just below "Open in Field Maps" that would go directly to the offline map creation interface panel. This could be configured so the button only appears if the map owner has configured the map for offline use, it could also be made to rely on a toggle option in the map settings where a map owner could allow/deny this type of activity. An organization could choose whether they want this enabled by default.
End result would be a whole lot more access to creating offline areas in the web app that can then be consistent across your field team, without putting all the project management pressure on one AGO map owner (whom is not generally tasked with personnel/scheduling/project subdivision on a day-to-day basis.)
Current project has a map shared to us in our client's AGO group. We can view the map in the web app, and we can access the map in Field Maps mobile, create our own device level offline areas (which are not sharable between users), add data to feature classes, etc. All of this has been configured by the map owner. Do we need to ask the client to create offline areas using the web interface for us, so that all our field users will have access to the same project subdivisions that our team is developing on a day to day and staffing needs basis? If the field app can do it, so can the web app! Looking forward to the solution on this one!
P.S. no, I don't want to sideload map packages either 😄
