I do get that modifying an app architected for use by a single user into a multi-user model, perhaps even with “roles”, is a huge engineering task, and one that doesn’t forward the core mission of AI Inventor 2.
I don’t see how it would create “security issues”, per se (other than the fact that the more people who have access, the great the risk that an account with access will be compromised), but it would definitely involve a lot of additional effort required to track who did what, on top of the obvious issues with maintaining synchronization and resolving conflicting modifications / avoiding inadvertently erasing one person’s modifications when another user makes a change simultaneously. I also suspect that the app doesn’t maintain a “history” of changes that allows you to revert to a previous state (directions to manually save versions to your local computer imply as much) ala Google Docs.
But, ultimately, some kind of mechanism of this sort is necessary for more than trivial levels of development.
Maybe, as an interim measure, the ability to save a project to another account (with permission)? In my case, the “designer” is going to be working on art assets (button graphics and background images), rather than modifying the look and feel by moving buttons around or changing other properties, so no risk of code inconsistency.