Read only access for Primary environments modal & blocks data structure

[thomas.verleye]

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:

Primary environment permissions
Add/Edit/Delete models/blocks
Add/Edit/Delete content

Sandbox environment permissions
Add/Edit/Delete models/blocks
Add/Edit/Delete content

[mat_jack1]

hey @thomas.verleye maybe you can remove this permission from your editors?

is this too much?

[mat_jack1]

oh right, you would like this only on the primary env, sorry. We don’t have this at the moment, let’s keep the feature request open

[illarion]

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