Workforce - allow access to users from non-organizational accounts

[UlfBecker]

Workforce currently requires that ArcGIS Online accounts be associated with ArcGIS Online For Organizations in order for them to be added as workers to a Workforce project.  However, we have many third party vendors who are no AGOL users.  I would like the latitude (no pun intended) for them to build their own personal accounts so that we an invite them into projects without the overhead of managing dozens of AGOL accounts for contract staff.

[ScottPrindle]

Hello Ulf,

Thank you for submitting this idea. Could you provide an example of a project where a non-organizational contractor would need to use a personal account? Would this scenario be a user that does not use ArcGIS Online, and will not after working on the project at hand?

This may diverge from Workforce specifically to a conversation about named users, so any additional information or detail on the workflows as they apply to the app will help us stay on topic.

Thanks,

Scott

[ScottPrindle]

To add to this, public accounts are not supported with Workforce based on this FAQ topic. This discussion can still be valid to identify common workflows and themes within customer projects. Please consider commenting to share your thoughts on this topic.

-Scott

[UlfBecker]

We work with many third party construction contractors at our manufacturing sites and many of them have their own, custom work request & dispatching tools.  These are designed to allow our staff access to submit requests for work (patch this road here, put up scaffolding there).  Unfortunately this forces our staff to have login credentials on several 3rd party tools and prompted us to take a look at Workforce.

Most (if not all) of these 3rd party construction contractors are not ArcGIS savvy and do not have access to organizational ArcGIS Online accounts.  Therefore we wondered if we could "encourage" them to create individual (public) accounts that we could invite into Workforce projects.  We would prefer this over managing IDs for them on our organizational ArcGIS Online implementation.  Does this address your question?

[ScottPrindle]

Hey Ulf,

Thank you for this additional context around the issue at hand. As I noted in another comment, the FAQ states that public accounts are not supported with Workforce. There may be different approaches for the temporary contractor scenario you've described, which is why the additional context is important.

Thanks,

Scott

[UlfBecker]

Scott - in the short term we will likely manage ID on behalf of 3rd party staff and see how it goes.