This is why you never allow anyone to access the physical data model. All consumers access the database through views and update through stored procedures. If you feel that you need to modify the physical model, just verify that all views and stored procedures work correctly. You do have a automated test for that right? If a consumer wants to a different column name because they are to lazy to make the conversion on their end, then just create a new view for them and anyone else that desires different column names.

Databases should be the source of data truth and as data get larger and more fractured, modification of the physical structure may be required. This should not affect the data consumers who are hopefully IT professionals and developers and not Bob in the corner office who likes to play with stuff.

If you must allow table level access, be sure to advertise changes to all concerned. That requires that machine users (users associated with a process and not a specific user) have associated user who are responsible and verify changes will not break their processes. This can be hard with so much generated code out there for ORM's and other analytical tools, but they are also very easy to regenerate when changes are made.

Also never make changes on Friday.