Thanks @jonathon: Something like the second approach. This would especially aid medium to large organizations.
Hierarchy:
- Speckle Admin = Admin on company-level → has the rights for invites (external guests) + project creation
- Speckle Project Owner = Admin on project level → has the rights for inviting team members (existing on the server) into the project → manages the project
- Speckle Project Member = just works on it = writing rights
- Speckle Project Guest = can only watch and comment = reading rights
Autodesk Construction Cloud has a similar approach … a bit too complicated though
It is not just about keeping control over who has access, but also about maintaining order.
With MS Teams we had total madness until we limited the creation and invested in an admin tool for the approval process … to prevent project duplicates and to maintain a project naming convention.
Some aspects I have also mentioned here Administration of Projects and Invites