When working in a development team that only uses migrations to update the data structures, it does make sense to make the primary environment data structures read only.
This way, there won’t be any possibility to update the primary environment by accident and potentially break production for that matter.
It could be necessary however to be able to edit the copy of the primary environment.
Here’s a visual overview of what I’m trying to achieve:
I would really like to have this feature for our projects too — to be able to forbid model editing in the primary environment for everyone on the project, including admins.
It’s easy to overlook the “current environment” banner, especially when iterating in small chunks to auto-generate focused migrations
I’d love this as a feature - I’d like to be able to have developers be able to add/edit models within sandbox environments, so they can then generate migrations for those, but not be able to do the same in the primary environment. They should still have view access, and normal content editing permissions to the primary environment. That doesn’t seem to be possible with the current rules, where access/editing and ‘perform operations’ seem to be tied together - is that correct?
Add/Edit/Delete models/blocks
Add/Edit/Delete content
