I’d be really careful with that. Menus and securities have less backend data integrity control than most things. Footgun prevention is mostly handled at the client. Copy-to-company, then being very careful to only work on company copies, preserves the system copies if you need an easy way to unwind your work if/when you discover that things work in unexpected ways. Configuring the whole security ecosystem effectively requires using DMT or whatever, which do make it very easy to accidentally do undocumented things.
I don’t know what you guys are saying, lol. The “Form to Use” field is editable for me and always has been. And no, I don’t have any cusomization in place. This is straight from demo.
Maybe the difference is prior setup? In new cloud environments, I see that the copy to current company feature is required to edit menus, but not on an upgraded database.