Hosted RPA includes a single machine and a Process license. Access to the machine is limited and not necessarily granted to each developer.
Also, a recommended way of working with unattended flows is doing development and testing on a separate machine from the one where the flows will actually run. This is especially important when you want to make changes to a flow that is already deployed, or if you want to add additional flows. In order to not interfere with flows in production, you should separate development and testing from production. The absolutely ideal way would be having at least three environments (machines) - one for development, one for testing and one for production. But the bare minimum is to have at least one for dev+test and one for prod.
These can also be on the developer workstations, if you don't want extra VMs, assuming they can mimic the same software setup as what you'd be getting on the prod VM. The version of Windows is something that is not absolutely important, but your developers should at least have access to all of the software clients that you'll be automating, as well as any network locations, databases, etc.
-------------------------------------------------------------------------
If I have answered your question, please mark it as the preferred solution. If you like my response, please give it a Thumbs Up.
I also provide paid consultancy and development services using Power Automate. If you're interested, DM me and we can discuss it.
As such, I would suggest having Premium licenses for your developers, or else they will not really be able to run tests on your flows in attended mode (the Process license does not include that).
