Many organizations have multiple teams working on related products, and developers often need visibility into other teams’ repositories to learn from implementations, reuse patterns, and better understand integrations.
Currently, Mendix Team Server permissions are essentially all-or-nothing, meaning users either get full repository access or no access at all. This can discourage teams from granting access because users can also commit changes, creating a risk of unintended modifications.
Introducing a read-only repository access option would allow developers to view code, history, and project structure without being able to commit or alter the repository. This would promote knowledge sharing, collaboration, and transparency across teams while maintaining code ownership, security, and governance.
More over, it will more useful when it support for Merge Requests (Pull Requests) on Mendix Team Server (Git), then developers/user can read the code and create sub branch, and only create Merge Requests to get approval can merge code changes to certain branch, e.g. main branch, release/* branch.