B: is already partially integrated (guest role) into the right management of FE2. It would be cool to connect those settings automatically to the Azure security groups via app roles of the SSO.
Example:
- Security Group: Admin = admin access
- Security Group: Member =regulars
- Security Group: Externals = guest access
It is more of an icing on the cake situation, but this helps IT/admins to have control over the access.
With this reply I want to add another point to the list:
Besides making sure, that projects are not deleted by removing users (see link below) … it would be in general important that people with admin access should be able to enter any private and public project without the need to be invited. Maybe a colleague creates a project, leaves the firm, or is sick … the accessibility is a big issue that might affect project success.
Of course, one could step into the DB and change settings, but this is not a clean method for a bigger group of admins.
Domain Owned Streams & Admin Control - Features & Ideas - Speckle Community